RFC 5704: Uncoordinated Protocol Development Considered Harmful

This document identifies problems that may result from the absence of formal coordination and joint development on protocols of mutual interest between…

Read RFC 5704 on the RFC Editor

Outgoing relationships (17 related RFCs)

Informative reference — RFC 3031: Multiprotocol Label Switching Architecture
Informative reference — RFC 3032: MPLS Label Stack Encoding
Informative reference — RFC 4379: Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures
Informative reference — RFC 5654: Requirements of an MPLS Transport Profile
Informative reference — RFC 3270: Multi-Protocol Label Switching (MPLS) Support of Differentiated Services
Informative reference — RFC 5462: Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field
Informative reference — RFC 5129: Explicit Congestion Marking in MPLS
Informative reference — RFC 3356: Internet Engineering Task Force and International Telecommunication Union - Telecommunications Standardization Sector Collaboration Guidelines
Informative reference — RFC 4929: Change Process for Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Protocols and Procedures
Informative reference — RFC 5317: Joint Working Team (JWT) Report on MPLS Architectural Considerations for a Transport Profile
Informative reference — RFC 1393: Traceroute Using an IP Option
Informative reference — RFC 3429: Assignment of the 'OAM Alert Label' for Multiprotocol Label Switching Architecture (MPLS) Operation and Maintenance (OAM) Functions
Informative reference — RFC 2436: Collaboration between ISOC/IETF and ITU-T
Informative reference — RFC 2615: PPP over SONET/SDH
Informative reference — RFC 4775: Procedures for Protocol Extensions and Variations
Informative reference — RFC 1619: PPP over SONET/SDH
Informative reference — RFC 3245: The History and Context of Telephone Number Mapping (ENUM) Operational Decisions: Informational Documents Contributed to ITU-T Study Group 2 (SG2)

Incoming relationships (4 related RFCs)

Informatively referenced by — RFC 6709: Design Considerations for Protocol Extensions
Informatively referenced by — RFC 8799: Limited Domains and Internet Protocols
Informatively referenced by — RFC 9170: Long-Term Viability of Protocol Extension Mechanisms
Informatively referenced by — RFC 6569: Guidelines for Development of an Audio Codec within the IETF