Committed to connecting the world

  •  
wtisd

ITU-T work programme

[2022-2024] : [SG16] : [Q11/16]

[Declared patent(s)]  - [Associated work]  - [Publication]

Work item: H.323 (V8)
Subject/title: Packet-based multimedia communications systems
Status: Approved on 2022-03-16 [Issued from previous study period]
Approval process: AAP
Type of work item: Recommendation
Version: Rev.
Equivalent number: -
Timing: -
Liaison: IETF
Supporting members: -
Summary: Recommendation ITU-T H.323 describes terminals and other entities that provide multimedia communications services over Packet-Based Networks (PBN) which may not provide a guaranteed Quality of Service. H.323 entities may provide real-time audio, video and/or data communications. Support for audio is mandatory, while data and video are optional, but if supported, the ability to use a specified common mode of operation is required, so that all terminals supporting that media type can interwork. The packet-based network over which H.323 entities communicate may be a point-to-point connection, a single network segment, or an internetwork having multiple segments with complex topologies. H.323 entities may be used in point-to-point, multipoint, or broadcast (as described in Rec. ITU-T H.332) configurations. They may interwork with H.310 terminals on B-ISDN, H.320 terminals on N-ISDN, H.321 terminals on B-ISDN, H.322 terminals on Guaranteed Quality of Service LANs, H.324 terminals on GSTN and wireless networks, V.70 terminals on GSTN, and voice terminals on GSTN or ISDN through the use of Gateways. H.323 entities may be integrated into personal computers or implemented in stand-alone devices such as videotelephones. Note that the title of H.323 (1996) was "Visual telephone systems and equipment for local area networks which provide a non-guaranteed quality of service". The title changed in Version 2 to be consistent with its expanded scope. Products claiming compliance with Version 1 of H.323 shall comply with all of the mandatory requirements of H.323 (1996) which references Rec. ITU-T H.225.0 (1996) and Rec. ITU-T H.245 (1997). Version 1 products shall be identified by H.225.0 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 2250 version(0) 1} and H.245 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 245 version(0) 2}. Products claiming compliance with Version 2 of H.323 shall comply with all of the mandatory requirements of this Recommendation, H.323 (1998), which references Rec. ITU-T H.225.0 (1998) and Rec. ITU-T H.245 (1998 or later). Version 2 products shall be identified by H.225.0 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 2250 version(0) 2} and H.245 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 245 version(0) x}, where "x" is 3 or higher. Products claiming compliance with Version 3 of H.323 shall comply with all of the mandatory requirements of this Recommendation, H.323 (1999), which references Rec. ITU-T H.225.0 (1999) and Rec. ITU-T H.245 (1999 or later). Version 3 products shall be identified by H.225.0 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 2250 version(0) 3} and H.245 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 245 version(0) x}, where "x" is 5 or higher. Products claiming compliance with Version 4 of H.323 shall comply with all of the mandatory requirements of this Recommendation, H.323 (2000), which references Rec. ITU-T H.225.0 (2000) and Rec. ITU-T H.245 (2000 or later). Version 4 products shall be identified by H.225.0 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 2250 version(0) 4} and H.245 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 245 version(0) x}, where "x" is 7 or higher. Products claiming compliance with Version 5 of H.323 shall comply with all of the mandatory requirements of this Recommendation, H.323 (2003), which references Rec. ITU-T H.225.0 (2003) and Rec. ITU-T H.245 (02/2003 or later). Version 5 products shall be identified by H.225.0 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 2250 version(0) 5} and H.245 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 245 version(0) x}, where "x" is 9 or higher. Products claiming compliance with Version 6 of H.323 shall comply with all of the mandatory requirements of this Recommendation, H.323 (2006), which references Rec. ITU-T H.225.0 (2006) and Rec. ITU-T H.245 (05/2006 or later). Version 6 products shall be identified by H.225.0 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 2250 version(0) 6} and H.245 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 245 version(0) x}, where "x" is 13 or higher. Products claiming compliance with Version 7 of H.323 shall comply with all of the mandatory requirements of this Recommendation, H.323 (2009), which references Rec. ITU-T H.225.0 (2009) and Rec. ITU-T H.245 (2009 or later). Version 7 products shall be identified by H.225.0 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 2250 version(0) 7} and H.245 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 245 version(0) x}, where "x" is 15 or higher. Products claiming compliance with Version 8 of H.323 shall comply with all of the mandatory requirements of this Recommendation, H.323 (2022), which references Rec. ITU-T H.225.0 (2022) and Rec. ITU-T H.245 (2022 or later). Version 8 products shall be identified by H.225.0 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 2250 version(0) 8} and H.245 messages containing a protocolIdentifier = {itu-t(0) recommendation(0) h(8) 245 version(0) x}, where "x" is 16 or higher. In addition to many minor corrections and clarifications, this version of Rec. ITU-T H.323 incorporates enhancements and clarifications to Annex O and to Annex M5 to support ITU-T X1303 bis.
Comment: Not stale. This draft revised Recommendation is in a stable state and can be Consented as soon as the IETF references in them are resolved.
Reference(s):
  Historic references:
Contact(s):
Paul E. Jones, Editor
ITU-T A.5 justification(s):
Generate A.5 drat TD
-
[Submit new A.5 justification ]
See guidelines for creating & submitting ITU-T A.5 justifications
First registration in the WP: 2014-05-16 15:11:25
Last update: 2022-04-01 17:16:11