Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 6514

Updated by:

RFC 7582,RFC 7900,RFC 8534

Authors:

E. Rosen, Ed.
Y. Rekhter, Ed.
W. Hendrickx
R. Qiu

Stream:

IETF

Source:

l3vpn (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

In Multicast Virtual Private Networks (MVPNs), customer multicastflows are carried in "tunnels" through a service provider's network.The base specifications for MVPN define BGP multicast VPN"auto-discovery routes" and specify how to use an auto-discoveryroute to advertise the fact that an individual customer multicastflow is being carried in a particular tunnel. However, thosespecifications do not provide a way to specify, in a single suchroute, that multiple customer flows are being carried in a singletunnel. Those specifications also do not provide a way to advertisethat a particular tunnel is to be used by default to carry allcustomer flows, except in the case where that tunnel is joined by allthe provider edge routers of the MVPN. This document eliminatesthese restrictions by specifying the use of "wildcard" elements inthe customer flow identifiers. With wildcard elements, a singleauto-discovery route can refer to multiple customer flows or even toall customer flows. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.