CurrentPROPOSED STANDARDIETF stream

RFC 6512: Using Multipoint LDP When the Backbone Has No Route to the Root

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC6512
Published
February 2012
Authors
IJ. Wijnands; E. Rosen; M. Napierala; N. Leymann
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
12
Also known as

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/6512-using-multipoint-ldp-when-the-backbone-has-no-route-to-the-root