Skip to main content

Concluded Program IAB ITU-T Coordination Program (iabitutcoord)

Note: The data for concluded Programs is occasionally incorrect.

Program Name IAB ITU-T Coordination Program
Acronym iabitutcoord
State Concluded
Document dependencies

Final Group description

NOTE: Work in the ITU-T Coordination Program was folded into the Liaison Oversight Program in March 2015.

Description:

The ITU-T Coordination Program is an effort focusing on the relationship between the IETF and ITU-T, where some of the highest frequency interaction currently takes place. The objective of this program is to establish and maintain a cooperative and mutually respectful relationship that serves the best interests of both SDOs.

As with other Programs, the ITU-T Coordination Program develops recommendations for consideration by the IAB, and the IAB retains its oversight responsibilities under RFC 2850.

This program is divided into two components. One component (going by the name ITU-T strategic planning) provides strategic coordination planning, while the other (going by the name ITU-T liaison coordination) provides tactical, detailed, and specific liaison coordination.

Both components provide advice to the IAB, and to any other activities in the IETF that need to work with the ITU-T, especially the IESG. Both components provide recommendations to the IAB.

Specifically, the ITU-T Strategic Planning Component:

  • Develops the principles guiding the relationship and implements and maintains them
  • Provides advice to the IAB relating to strategic and directional developments within ITU-T
  • Prepares specific strategic recommendations and documents at the request of the IAB

The ITU-T liaison coordination component:

  • Ensures that the liaison managers are aware of relevant activities in the ITU-T
  • Ensures that the participants speaking on behalf of the IETF are all aware of the messages and goals of our interaction with the ITU-T
  • Monitors and guides the emergence and development of close or possibly overlapping work items in IETF and ITU-T. Examples include: Q.Flowstatesig in ITU-T SG11 Q5, Codec in IETF RAI, Deep Packet Inspection in ITU-T SG13 Q17, MPLS-TP in ITU-T SG15.
  • Tracks technical work within the ITU-T that relates to or has impact on IETF work items and/or responsibilities and reports consistently to the IAB
  • Coordinates the liaison activity at all levels: at the level of a WG, an IETF Area, the IETF, and the IAB
  • Organizes periodic reviews of the liaison relationships with ITU-T

All ITU-T Coordination Program members are appointed by the IAB. Membership is based primarily on expertise and/or perspective, as well as joint participation that members bring to the group. Members serve on personal title. All appointed IETF liaisons to ITU-T are expected to be members of this group, participating in the liaison coordination activities.

ISOC is an important contributor to all aspects of this program and provides participants to both components; both to provide their expertise and to ensure coordination with ISOC activities in this area.

Documents

  • ITU-T liaison Job Description
  • ITU-­T / IETF Leadership Meeting Report (August 2010)

References

  • “Liaisons to National, Multi-National or Regional Organizations”
  • “Collaboration between ISOC/IETF and ITU-T”, RFC 2436 (obsoleted by RFC 3356)
  • “Internet Engineering Task Force and International Telecommunication Union – Telecommunications Standardization Sector Collaboration Guidelines”, RFC 3356
  • “OMA-IETF Standardization Collaboration”, RFC 3975
  • “IAB Processes for Management of IETF Liaison Relationships”, RFC 4052
  • “Procedures for Handling Liaison Statements to and from the IETF”, RFC 4053
  • “The IEEE 802/IETF Relationship”, RFC 4441
  • “Guidelines for Acting as an IETF Liaison to Another Organization”, RFC 4691
  • “Uncoordinated Protocol Development Considered Harmful”, RFC 5704