RFC 6826: Multipoint LDP In-Band Signaling for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths
In plain English — editorial summary, not part of the RFC
Consider an IP multicast tree, constructed by Protocol Independent Multicast (PIM), that needs to pass through an MPLS domain in which Multipoint LDP (mLDP) point-to-multipoint and/or multipoint-to-multipoint Labels Switched Paths (LSPs) can be created. The part of the IP multicast tree that traverses the MPLS domain can be instantiated as a multipoint LSP. When a PIM Join message is received at the border of the MPLS domain, information from that message is encoded into mLDP messages. When the mLDP messages reach the border of the next IP domain, the encoded information is used to generate PIM messages that can be sent through the IP domain. The result is an IP multicast tree consisting of a set of IP multicast sub-trees that are spliced together with a multipoint LSP. This document describes procedures regarding how IP multicast trees are spliced together with multipoint LSPs. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6826
- Published
- January 2013
- Authors
- IJ. Wijnands; T. Eckert; N. Leymann; M. Napierala
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
- Updated by:
- RFC 7438
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6825Traffic Engineering Database Management Information Base in Support of MPLS-TE/GMPLSCurrent
January 2013
- RFC 6827Automatically Switched Optical Network (ASON) Routing for OSPFv2 ProtocolsCurrent
January 2013
- RFC 6823Advertising Generic Information in IS-ISCurrent
December 2012
- RFC 6829Label Switched Path (LSP) Ping for Pseudowire Forwarding Equivalence Classes (FECs) Advertised over IPv6Obsoleted
January 2013
- RFC 6830The Locator/ID Separation Protocol (LISP)Obsoleted
January 2013
- RFC 6822IS-IS Multi-InstanceObsoleted
December 2012
- RFC 6831The Locator/ID Separation Protocol (LISP) for Multicast EnvironmentsCurrent
January 2013
- RFC 6832Interworking between Locator/ID Separation Protocol (LISP) and Non-LISP SitesCurrent
January 2013
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?