Skip to main content

Use of Multipath with MPLS-TP and MPLS

Document Type Replaced Internet-Draft (mpls WG)
Expired & archived
Author Curtis Villamizar
Last updated 2013-03-14 (Latest revision 2013-01-25)
Replaces draft-villamizar-mpls-tp-multipath
Replaced by draft-ietf-mpls-multipath-use
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-mpls-multipath-use
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:


Many MPLS implementations have supported multipath techniques and many MPLS deployments have used multipath techniques, particularly in very high bandwidth applications, such as provider IP/MPLS core networks. MPLS-TP has strongly discouraged the use of multipath techniques. Some degradation of MPLS-TP OAM performance cannot be avoided when operating over many types of multipath implementations. Using MPLS Entropy label, MPLS LSPs can be carried over multipath links while also providing a fully MPLS-TP compliant server layer for MPLS-TP LSPs. This document describes the means of supporting MPLS as a server layer for MPLS-TP. The use of MPLS-TP LSPs as a server layer for MPLS LSPs is also discussed.


Curtis Villamizar

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