RFC 7246: Multipoint Label Distribution Protocol In-Band Signaling in a Virtual Routing and Forwarding (VRF) Table Context
In plain English — editorial summary, not part of the RFC
An IP Multicast Distribution Tree (MDT) may traverse both label switching (i.e., Multiprotocol Label Switching, or MPLS) and non-label switching regions of a network. Typically, the MDT begins and ends in non-MPLS regions, but travels through an MPLS region. In such cases, it can be useful to begin building the MDT as a pure IP MDT, then convert it to an MPLS Multipoint Label Switched Path (MP-LSP) when it enters an MPLS-enabled region, and then convert it back to a pure IP MDT when it enters a non-MPLS-enabled region. Other documents specify the procedures for building such a hybrid MDT, using Protocol Independent Multicast (PIM) in the non-MPLS region of the network, and using Multipoint Label Distribution Protocol (mLDP) in the MPLS region. This document extends those procedures to handle the case where the link connecting the two regions is a Virtual Routing and Forwarding (VRF) table link, as defined in the "BGP IP/MPLS VPN" specification. However, this document is primarily aimed at particular use cases where VRFs are used to support multicast applications other than multicast VPN.
Document record
- Document ID
- RFC7246
- Published
- June 2014
- Authors
- IJ. Wijnands; P. Hitchen; N. Leymann; W. Henderickx; A. Gulko; J. Tantsura
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 13
- 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 7257Virtual Private LAN Service (VPLS) Management Information BaseCurrent
July 2014
- RFC 7260GMPLS RSVP-TE Extensions for Operations, Administration, and Maintenance (OAM) ConfigurationCurrent
June 2014
- RFC 7226Requirements for Advanced Multipath in MPLS NetworksCurrent
May 2014
- RFC 7267Dynamic Placement of Multi-Segment PseudowiresCurrent
June 2014
- RFC 7271MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network OperatorsUpdated
June 2014
- RFC 7274Allocating and Retiring Special-Purpose MPLS LabelsUpdated
June 2014
- RFC 7275Inter-Chassis Communication Protocol for Layer 2 Virtual Private Network (L2VPN) Provider Edge (PE) RedundancyCurrent
June 2014
- RFC 7215Locator/Identifier Separation Protocol (LISP) Network Element Deployment ConsiderationsCurrent
April 2014
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?