Skip to main content

MPLS-TP Use Cases Studies and Design Considerations
draft-fang-mpls-tp-use-cases-and-design-04

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Dr. Nabil N. Bitar , Raymond Zhang , Luyuan Fang
Last updated 2012-02-08 (Latest revision 2011-10-31)
Replaced by draft-ietf-mpls-tp-use-cases-and-design
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-mpls-tp-use-cases-and-design
Consensus boilerplate Unknown
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:

Abstract

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.

Authors

Dr. Nabil N. Bitar
Raymond Zhang
Luyuan Fang

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