Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 6513,RFC 6514,RFC 6625

Updated by:

RFC 8534,RFC 9573

Authors:

E. Rosen
IJ. Wijnands
Y. Cai
A. Boers

Stream:

IETF

Source:

bess (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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 7582

Abstract

A set of prior RFCs specify procedures for supporting multicast inBGP/MPLS IP VPNs. These procedures allow customer multicast data totravel across a service provider's backbone network through a set ofmulticast tunnels. The tunnels are advertised in certain BGPmulticast auto-discovery routes, by means of a BGP attribute knownas the "Provider Multicast Service Interface (PMSI) Tunnel"attribute. Encodings have been defined that allow the PMSI Tunnelattribute to identify bidirectional (multipoint-to-multipoint)multicast distribution trees. However, the prior RFCs do not provideall the necessary procedures for using bidirectional tunnels tosupport multicast VPNs. This document updates RFCs 6513, 6514, and6625 by specifying those procedures. In particular, it specifies theprocedures for assigning customer multicast flows (unidirectional orbidirectional) to specific bidirectional tunnels in the providerbackbone, for advertising such assignments, and for determining whichflows have been assigned to which tunnels.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.