Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updated by:

RFC 7438

Authors:

IJ. Wijnands, Ed.
T. Eckert
N. Leymann
M. Napierala

Stream:

IETF

Source:

mpls (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6826

Discuss this RFC: Send questions or comments to the mailing listmpls@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6826

Abstract

Consider an IP multicast tree, constructed by Protocol IndependentMulticast (PIM), that needs to pass through an MPLS domain in whichMultipoint LDP (mLDP) point-to-multipoint and/ormultipoint-to-multipoint Labels Switched Paths (LSPs) can be created.The part of the IP multicast tree that traverses the MPLS domain can beinstantiated as a multipoint LSP. When a PIM Join message isreceived at the border of the MPLS domain, information from thatmessage is encoded into mLDP messages. When the mLDP messages reachthe border of the next IP domain, the encoded information is used togenerate PIM messages that can be sent through the IP domain. Theresult is an IP multicast tree consisting of a set of IP multicastsub-trees that are spliced together with a multipoint LSP. Thisdocument describes procedures regarding how IP multicast trees are splicedtogether with multipoint LSPs. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.