RFC 5960: MPLS Transport Profile Data Plane Architecture
In plain English — editorial summary, not part of the RFC
The Multiprotocol Label Switching Transport Profile (MPLS-TP) is the set of MPLS protocol functions applicable to the construction and operation of packet-switched transport networks. This document specifies the subset of these functions that comprises the MPLS-TP data plane: the architectural layer concerned with the encapsulation and forwarding of packets within an MPLS-TP network. 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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5960
- Published
- August 2010
- Authors
- D. Frost; S. Bryant; M. Bocci
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- Also known as
- —
- Updated by:
- RFC 7274
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5921A Framework for MPLS in Transport NetworksUpdated
July 2010
- RFC 5718An In-Band Data Communication Network For the MPLS Transport ProfileCurrent
January 2010
- RFC 5654Requirements of an MPLS Transport ProfileCurrent
September 2009
- RFC 5586MPLS Generic Associated ChannelUpdated
June 2009
- RFC 7260GMPLS RSVP-TE Extensions for Operations, Administration, and Maintenance (OAM) ConfigurationCurrent
June 2014
- RFC 5317Joint Working Team (JWT) Report on MPLS Architectural Considerations for a Transport ProfileCurrent
February 2009
- RFC 5951Network Management Requirements for MPLS-based Transport NetworksCurrent
September 2010
- RFC 5950Network Management Framework for MPLS-based Transport NetworksCurrent
September 2010
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?