RFC 7988: Ingress Replication Tunnels in Multicast VPN
In plain English — editorial summary, not part of the RFC
RFCs 6513, 6514, and other RFCs describe procedures by which a Service Provider may offer Multicast VPN (MVPN) service to its customers. These procedures create point-to-multipoint (P2MP) or multipoint-to-multipoint (MP2MP) trees across the Service Provider's backbone. One type of P2MP tree that may be used is known as an "Ingress Replication (IR) tunnel". In an IR tunnel, a parent node need not be directly connected to its child nodes. When a parent node has to send a multicast data packet to its n child nodes, it does not use Layer 2 multicast, IP multicast, or MPLS multicast to do so. Rather, it makes n individual copies, and then unicasts each copy, through an IP or MPLS unicast tunnel, to exactly one child node. While the prior MVPN specifications allow the use of IR tunnels, those specifications are not always very clear or explicit about how the MVPN protocol elements and procedures are applied to IR tunnels. This document updates RFCs 6513 and 6514 by adding additional details that are specific to the use of IR tunnels.
Document record
- Document ID
- RFC7988
- Published
- October 2016
- Authors
- E. Rosen; K. Subramanian; Z. Zhang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 23
- Also known as
- —
- Updated by:
- RFC 10018
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 7987IS-IS Minimum Remaining LifetimeCurrent
October 2016
- RFC 7985Security Threats to Simplified Multicast Forwarding (SMF)Current
November 2016
- RFC 7981IS-IS Extensions for Advertising Router InformationCurrent
October 2016
- RFC 7978Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Header ExtensionCurrent
September 2016
- RFC 8001RSVP-TE Extensions for Collecting Shared Risk Link Group (SRLG) InformationCurrent
January 2017
- RFC 7968Transparent Interconnection of Lots of Links (TRILL): Using Data Labels for Tree Selection for Multi-Destination DataCurrent
August 2016
- RFC 7965LDP Extensions for Pseudowire Binding to Label Switched Path (LSP) TunnelsCurrent
August 2016
- RFC 7964Solutions for BGP Persistent Route OscillationCurrent
September 2016
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?