Use of Multipath with MPLS-TP and MPLS
draft-ietf-mpls-multipath-use-00

The information below is for an old version of the document
Document Type Expired Internet-Draft (mpls WG)
Last updated 2013-08-29 (latest revision 2013-02-25)
Replaces draft-villamizar-mpls-multipath-use
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state Expired
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
https://www.ietf.org/archive/id/draft-ietf-mpls-multipath-use-00.txt

Abstract

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.

Authors

Curtis Villamizar (curtis@occnc.com)

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