MPLS-TP Applicability; Use Cases and Design
draft-ietf-mpls-tp-use-cases-and-design-02

The information below is for an old version of the document
Document Type Expired Internet-Draft (mpls WG)
Last updated 2012-12-13 (latest revision 2012-06-11)
Replaces draft-fang-mpls-tp-use-cases-and-design
Stream IETF
Intended RFC status Informational
Formats
Expired & archived
pdf htmlized bibtex
Reviews
Additional URLs
- Mailing list discussion
Stream WG state WG Document
Document shepherd None
IESG IESG state Expired (IESG: Dead)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Adrian Farrel
IESG note Loa Andersson (loa@pi.nu) is the document shepherd.
Send notices to mpls-chairs@tools.ietf.org, draft-ietf-mpls-tp-use-cases-and-design@tools.ietf.org

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-mpls-tp-use-cases-and-design-02.txt

Abstract

This document provides applicability, 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

Luyuan Fang (lufang@cisco.com)
Nabil Bitar (nabil.bitar@verizon.com)
Raymond Zhang (raymond.zhang@alcatel-lucent.com)
Masahiro Daikoku (ms-daikoku@kddi.com)

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