Skip to main content

Use of Multipath with MPLS-TP and MPLS

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Curtis Villamizar
Last updated 2013-01-10 (Latest revision 2012-10-02)
Replaced by draft-villamizar-mpls-multipath-use
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-villamizar-mpls-multipath-use
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 can LSP can be carried over multipath links while also providing a fully MPLS-TP compliant server layer for MPLS-TP LSP. This document describes the means of supporting MPLS as a server layer for MPLS-TP. The use of MPLS-TP LSP as a server layer for MPLS LSP is also discussed.


Curtis Villamizar

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