MPLS-TP Use Cases Studies and Design Considerations

Document Type Replaced Internet-Draft (individual)
Authors Nabil Bitar  , Raymond Zhang  , Luyuan Fang 
Last updated 2012-02-08 (latest revision 2011-10-31)
Replaced by RFC 6965
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream WG state Call For Adoption By WG Issued
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-mpls-tp-use-cases-and-design
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document provides use case studies and network design considerations for Multiprotocol Label Switching Transport Profile (MPLS-TP). In the recent years, MPLS-TP has emerged as the technology of choice for the new generation of packet transport. Many service providers (SPs) are working to replace the legacy transport technologies, e.g. SONET/SDH, TDM, and ATM technologies, with MPLS-TP for packet transport, in order to achieve higher efficiency, lower operational cost, while maintaining transport characteristics. The use cases for MPLS-TP include Metro Ethernet access and aggregation, Mobile backhaul, and packet optical transport. The design considerations discussed in this documents ranging from operational experience; standards compliance; technology maturity; end-to-end forwarding and OAM consistency; compatibility with IP/MPLS networks; multi-vendor interoperability; and optimization vs. simplicity design trade off discussion. The general design principle is to provide reliable, manageable, and scalable transport solutions.


Nabil Bitar (
Raymond Zhang (
Luyuan Fang (

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