Using Multipoint LDP When the Backbone Has No Route to the Root
RFC 6512, “Using Multipoint LDP When the Backbone Has No Route to the Root”, is a Proposed Standard document published in February 2012 by IJ. Wijnands, E. Rosen, M. Napierala, N. Leymann. The canonical text is published by the RFC Editor.
Abstract
The control protocol used for constructing Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths ("MP LSPs") contains a field that identifies the address of a "root node". Intermediate nodes are expected to be able to look up that address in their routing tables. However, this is not possible if the route to the root node is a BGP route and the intermediate nodes are part of a BGP-free core. This document specifies procedures that enable an MP LSP to be constructed through a BGP-free core. In these procedures, the root node address is temporarily replaced by an address that is known to the intermediate nodes and is on the path to the true root node. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6512 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6511 Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for RSVP-TE Label Switched Paths
- RFC 6513 Multicast in MPLS/BGP IP VPNs
- RFC 6510 Resource Reservation Protocol Message Formats for Label Switched Path Attributes Objects
- RFC 6514 BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs
- RFC 6509 MIKEY-SAKKE: Sakai-Kasahara Key Encryption in Multimedia Internet KEYing
- RFC 6515 IPv4 and IPv6 Infrastructure Addresses in BGP Updates for Multicast VPN
- RFC 6508 Sakai-Kasahara Key Encryption
- RFC 6516 IPv6 Multicast VPN Support Using PIM Control Plane and Selective Provider Multicast Service Interface Join Messages