MPLS-TP


Multiprotocol Label Switching - Transport Profile is a variant of the MPLS protocol that is used in packet switched data networks. MPLS-TP is the product of a joint Internet Engineering Task Force / International Telecommunication Union Telecommunication Standardization Sector effort to include an MPLS Transport Profile within the IETF MPLS and PWE3 architectures to support the capabilities and functionalities of a packet transport network.
MPLS-TP is designed for use as a network layer technology in transport networks. It will be a continuation of the work started by the transport network experts of the ITU-T, specifically SG15, as T-MPLS. Since 2008 the work is progressed in a cooperation between ITU-T and IETF. The required protocol extensions to MPLS being designed by the IETF based on requirements provided by service providers. It will be a connection-oriented packet-switched application. It will offer a dedicated MPLS implementation by removing features that are not relevant to CO-PS applications and adding mechanisms that provide support of critical transport functionality.
MPLS-TP is to be based on the same architectural principles of layered networking that are used in longstanding transport network technologies like SDH, SONET and OTN. Service providers have already developed management processes and work procedures based on these principles.
MPLS-TP gives service providers a reliable packet-based technology that is based upon circuit-based transport networking, and thus is expected to align with current organizational processes and large-scale work procedures similar to other packet transport technologies.
MPLS-TP is a low cost L2.5 technology that provides QoS, end-to-end OA&M and protection switching.
In February 2008 the ITU-T and IETF agreed to work jointly
on the design of MPLS-TP. Based on this agreement IETF and ITU-T experts will jointly work out the requirements and solutions. ITU-T in turn will update the existing T-MPLS standards based on the MPLS-TP related RFCs listed below.

ITU-T

The following ITU-T Recommendations exist for MPLS-TP. Some of those Recommendations are superseding the ones that applied to T-MPLS before this work was ceased.
RecommendationTitle
G.8110.1Architecture of the Multi-Protocol Label Switching transport profile layer network
G.8112Interfaces for the MPLS transport profile layer network
G.8113.1Operations, administration and maintenance mechanisms for MPLS-TP in packet transport networks
G.8113.2Operations, administration and maintenance mechanisms for MPLS-TP networks using the tools defined for MPLS
G.8121Characteristics of MPLS-TP equipment functional blocks
G.8121.1Characteristics of MPLS-TP equipment functional blocks supporting ITU-T G.8113.1/Y.1372.1 OAM mechanisms
G.8121.2Characteristics of MPLS-TP equipment functional blocks supporting ITU-T G.8113.2/Y.1372.2 OAM mechanisms
G.8131Linear protection switching for MPLS transport profile
G.8151Management aspects of the MPLS-TP network element
G.8152Protocol-neutral management information model for the MPLS-TP network element

RFC or drafts

The following IETF RFCs or drafts exist for MPLS-TP:
RFCTitleDraft
-
RFC 5317Joint Working Team Report on MPLS Architectural Considerations for a Transport Profiledraft-bryant-mpls-tp-jwt-report
RFC 5586MPLS Generic Associated Channeldraft-ietf-mpls-tp-gach-gal
RFC 5654MPLS-TP Requirementsdraft-ietf-mpls-tp-requirements
RFC 5718An In-Band Data Communication Network For the MPLS Transport Profiledraft-ietf-mpls-tp-gach-dcn
RFC 5860Requirements for Operations, Administration, and Maintenance in MPLS Transport Networksdraft-ietf-mpls-tp-oam-requirements
RFC 5921A Framework for MPLS in Transport Networksdraft-ietf-mpls-tp-framework
RFC 5950Network Management Framework for MPLS-based Transport Networksdraft-ietf-mpls-tp-nm-framework
RFC 5951Network Management Requirements for MPLS-based Transport Networksdraft-ietf-mpls-tp-nm-req
RFC 5960MPLS Transport Profile Data Plane Architecturedraft-ietf-mpls-tp-data-plane
RFC 6215MPLS Transport Profile User-to-Network and Network-to-Network Interfacesdraft-ietf-mpls-tp-uni-nni
RFC 6291Guidelines for the Use of the "OAM" Acronym in the IETFdraft-ietf-opsawg-mpls-tp-oam-def
RFC 6370MPLS-TP Identifiersdraft-ietf-mpls-tp-identifiers
RFC 6371Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networksdraft-ietf-mpls-tp-oam-framework
RFC 6372MPLS Transport Profile Survivability Frameworkdraft-ietf-mpls-tp-survive-fwk
RFC 6373MPLS-TP Control Plane Frameworkdraft-ietf-ccamp-mpls-tp-cp-framework
RFC 6375A Packet Loss and Delay Measurement Profile for MPLS-based Transport Networksdraft-ietf-mpls-tp-loss-delay-profile
RFC 6669MPLS-TP OAM Analysisdraft-ietf-mpls-tp-oam-analysis
RFC 6426MPLS On-demand Connectivity Verification and Route Tracingdraft-ietf-mpls-tp-on-demand-cv
RFC 6378MPLS-TP Linear Protectiondraft-ietf-mpls-tp-linear-protection
RFC 6427MPLS Fault Management OAMdraft-ietf-mpls-tp-fault
RFC 6428Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS Transport Profiledraft-ietf-mpls-tp-cc-cv-rdi
RFC 6478Pseudowire Status for Static Pseudowiresdraft-ietf-pwe3-static-pw-status
RFC 6435MPLS Transport Profile lock Instruct and Loopback Functionsdraft-ietf-mpls-tp-li-lb

Solutions

The solutions for the above requirements and framework are as mentioned below and is under development: