RFC 5921: A Framework for MPLS in Transport Networks
In plain English — editorial summary, not part of the RFC
This document specifies an architectural framework for the application of Multiprotocol Label Switching (MPLS) to the construction of packet-switched transport networks. It describes a common set of protocol functions -- the MPLS Transport Profile (MPLS-TP) -- that supports the operational models and capabilities typical of such networks, including signaled or explicitly provisioned bidirectional connection-oriented paths, protection and restoration mechanisms, comprehensive Operations, Administration, and Maintenance (OAM) functions, and network operation in the absence of a dynamic control plane or IP forwarding support. Some of these functions are defined in existing MPLS specifications, while others require extensions to existing specifications to meet the requirements of the MPLS-TP. This document defines the subset of the MPLS-TP applicable in general and to point-to-point transport paths. The remaining subset, applicable specifically to point-to-multipoint transport paths, is outside the scope of this document. This document is a product of a joint Internet Engineering Task Force (IETF) / International Telecommunication Union Telecommunication Standardization Sector (ITU-T) effort to include an MPLS Transport Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge (PWE3) architectures to support the capabilities and functionalities of a packet transport network as defined by the ITU-T. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5921
- Published
- July 2010
- Authors
- M. Bocci; S. Bryant; D. Frost; L. Levrau; L. Berger
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 56
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5960MPLS Transport Profile Data Plane ArchitectureUpdated
August 2010
- RFC 5317Joint Working Team (JWT) Report on MPLS Architectural Considerations for a Transport ProfileCurrent
February 2009
- RFC 5860Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport NetworksCurrent
May 2010
- RFC 5654Requirements of an MPLS Transport ProfileCurrent
September 2009
- RFC 5586MPLS Generic Associated ChannelUpdated
June 2009
- RFC 6428Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport ProfileUpdated
November 2011
- RFC 7260GMPLS RSVP-TE Extensions for Operations, Administration, and Maintenance (OAM) ConfigurationCurrent
June 2014
- RFC 7324Updates to MPLS Transport Profile Linear ProtectionCurrent
July 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?