Use of Multipath with MPLS and MPLS Transport Profile
RFC 7190, “Use of Multipath with MPLS and MPLS Transport Profile”, is an Informational document published in March 2014 by C. Villamizar. The canonical text is published by the RFC Editor.
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 Transport Profile (MPLS-TP) has strongly discouraged the use of multipath techniques. Some degradation of MPLS-TP Operations, Administration, and Maintenance (OAM) performance cannot be avoided when operating over many types of multipath implementations.
Using MPLS Entropy Labels (RFC 6790), MPLS Label Switched Paths (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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 7190 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7189 Virtual Circuit Connectivity Verification Capability Advertisement for MPLS Transport Profile
- RFC 7191 Cryptographic Message Syntax Key Package Receipt and Error Content Types
- RFC 7188 Optimized Link State Routing Protocol Version 2 and MANET Neighborhood Discovery Protocol Extension TLVs
- RFC 7192 Algorithms for Cryptographic Message Syntax Key Package Receipt and Error Content Types
- RFC 7187 Routing Multipoint Relay Optimization for the Optimized Link State Routing Protocol Version 2
- RFC 7193 The application/cms Media Type
- RFC 7186 Security Threats for the Neighborhood Discovery Protocol
- RFC 7194 Default Port for Internet Relay Chat via TLS/SSL