[rfc-dist] RFC 5704 on Uncoordinated Protocol Development Considered Harmful
rfc-editor at rfc-editor.org
Mon Nov 23 16:30:55 PST 2009
A new Request for Comments is now available in online RFC libraries.
Title: Uncoordinated Protocol Development Considered Harmful
Author: S. Bryant, Ed.,
M. Morrow, Ed.,
Date: November 2009
Mailbox: stbryant at cisco.com,
mmorrow at cisco.com,
iab at iab.org
I-D Tag: draft-iab-mpls-tp-uncoord-harmful-02.txt
This document identifies problems that may result from the absence of
formal coordination and joint development on protocols of mutual
interest between standards development organizations (SDOs). Some of
these problems may cause significant harm to the Internet. The
document suggests that a robust procedure is required prevent this
from occurring in the future. The IAB has selected a number of case
studies, such as Transport MPLS (T-MPLS), as recent examples to
describe the hazard to the Internet architecture that results from
uncoordinated adaptation of a protocol.
This experience has resulted in a considerable improvement in the
relationship between the IETF and the ITU-T. In particular, this was
achieved via the establishment of the "Joint working team on
MPLS-TP". In addition, the leadership of the two organizations
agreed to improve inter-organizational working practices so as to
avoid conflict in the future between ITU-T Recommendations and IETF
Whilst we use ITU-T - IETF interactions in these case studies, the
scope of the document extends to all SDOs that have an overlapping
protocol interest with the IETF. This memo provides information for
the Internet community.
This document is a product of the Internet Architecture Board.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist