Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 6513,RFC 6514

Authors:

E. Rosen, Ed.
K. Subramanian
Z. Zhang

Stream:

IETF

Source:

bess (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

RFCs 6513, 6514, and other RFCs describe procedures by which a ServiceProvider may offer Multicast VPN (MVPN) service to its customers.These procedures create point-to-multipoint (P2MP) ormultipoint-to-multipoint (MP2MP) trees across the Service Provider'sbackbone. One type of P2MP tree that may be used is known as an"Ingress Replication (IR) tunnel". In an IR tunnel, a parent nodeneed not be directly connected to its child nodes. When a parent nodehas to send a multicast data packet to its n child nodes, it does notuse 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, thosespecifications are not always very clear or explicit about how theMVPN protocol elements and procedures are applied to IR tunnels. Thisdocument updates RFCs 6513 and 6514 by adding additional details thatare specific to the use of IR tunnels.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.