Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

S. Bryant, Ed.
M. Morrow, Ed.
IAB

Stream:

IAB

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5704

Discuss this RFC: Send questions or comments to the mailing listiab@iab.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5704

Abstract

This document identifies problems that may result from the absence offormal coordination and joint development on protocols of mutualinterest between standards development organizations (SDOs). Some ofthese problems may cause significant harm to the Internet. Thedocument suggests that a robust procedure is required prevent thisfrom occurring in the future. The IAB has selected a number of casestudies, such as Transport MPLS (T-MPLS), as recent examples todescribe the hazard to the Internet architecture that results fromuncoordinated adaptation of a protocol.

This experience has resulted in a considerable improvement in therelationship between the IETF and the ITU-T. In particular, this wasachieved via the establishment of the "Joint working team onMPLS-TP". In addition, the leadership of the two organizationsagreed to improve inter-organizational working practices so as toavoid conflict in the future between ITU-T Recommendations and IETFRFCs.

Whilst we use ITU-T - IETF interactions in these case studies, thescope of the document extends to all SDOs that have an overlappingprotocol interest with the IETF. This memo provides information forthe Internet community.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.