ITU-T Liaison Statements

ITU-T LIAISON STATEMENT SG16-LS210

Outgoing from:

SG16

Sent for action to:

TSAG registered as T22-TSAG-240729-TD-GEN-0616 for meeting [Geneva, 29 July - 2 August 2024]

Sent for information to:

SG2 registered as T25-SG02-250205-TD-GEN-0005 for meeting [Geneva, 5-14 February 2025]

SG3 registered as T25-SG03-250408-TD-GEN-0032 for meeting [Geneva, 8-17 April 2025]

SG5

SG9 registered as T22-SG09-240902-TD-GEN-0804 for meeting [Tokyo, 2-10 September 2024]

SG11 registered as T25-SG11-250219-TD-GEN-0124 for meeting [Geneva, 19-28 February 2025]

SG12

SG13 registered as T22-SG13-240715-TD-GEN-0396 for meeting [Geneva, 15-26 July 2024]

SG15 registered as T25-SG15-250317-TD-GEN-0002 for meeting [Geneva, 17-28 March 2025]

SG17 registered as T22-SG17-240902-TD-PLEN-2254 for meeting [Geneva, 2-6 September 2024]

SG20 registered as T25-SG20-250115-TD-GEN-0015 for meeting [Geneva, 15-24 January 2025]

In response to:

Source:

ITU-T SG16

Title:

LS/r on using the term "In force" instead of indicating the actual date of Approval of the Recommendations in clause 2 references (SG2-LS103)

Reference:

Approval date:

2024-07-05

Deadline date:

Full path:

See full conversation:

LS	Title	From	To	Approval date
SG16-LS210	LS/r on using the term "In force" instead of indicating the actual date of Approval of the Recommendations in clause 2 references (SG2-LS103)	SG16	TSAG; SG2; SG3; SG5; SG9; SG11; SG12; SG13; SG15; SG17; SG20;	2024-07-05
SG2-LS103	LS on using the term "In force" instead of indicating the actual date of Approval of the Recommendations in clause 2 references	SG2	SG3; SG5; SG9; SG11; SG12; SG13; SG15; SG16; SG17; TSAG; SG20;	2024-04-22