Skip to main content

Operator Considerations on MPLS-TP OAM Mechanisms

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Lei Wang , Juan Pedr Gi , Ruiquan Jing , China Unicom , Han Li , Fang Li
Last updated 2011-07-11
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Multi-Protocol Label Switching (MPLS) Transport Profile (MPLS-TP) is based on a profile of the MPLS and pseudo wire (PW) procedures as specified in the MPLS Traffic Engineering (MPLS-TE), pseudo wire (PW) and multi-segment PW (MS-PW) architectures complemented with additional Operations, Administration and Maintenance (OAM) procedures for fault, performance and protection-switching management for packet transport applications that do not rely on the presence of a control plane. This document is intended to explain the criticality of progressing the essential suite of MPLS-TP OAM solution elements in order to meet the urgent and increasing requirements for metro packet transport networks. It describes examples of key packet transport network applications for several operators, reviews associated MPLS-TP service provider requirements, and analyzes MPLS-TP OAM solution approaches that have been submitted to the IETF. Based upon this, it is recommended that the solution elements described in draft-bhh- mpls-tp-oam-y1731 [6] be included within the MPLS-TP toolkit for supporting MPLS-TP OAM Functions, and that the draft be progressed as a Standards Track RFC.


Lei Wang
Juan Pedr Gi
Ruiquan Jing
China Unicom
Han Li
Fang Li

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)