RFC 6625: Wildcards in Multicast VPN Auto-Discovery Routes
In plain English — editorial summary, not part of the RFC
In Multicast Virtual Private Networks (MVPNs), customer multicast flows 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-discovery route to advertise the fact that an individual customer multicast flow is being carried in a particular tunnel. However, those specifications do not provide a way to specify, in a single such route, that multiple customer flows are being carried in a single tunnel. Those specifications also do not provide a way to advertise that a particular tunnel is to be used by default to carry all customer flows, except in the case where that tunnel is joined by all the provider edge routers of the MVPN. This document eliminates these restrictions by specifying the use of "wildcard" elements in the customer flow identifiers. With wildcard elements, a single auto-discovery route can refer to multiple customer flows or even to all customer flows. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6625
- Published
- May 2012
- Authors
- E. Rosen; Y. Rekhter; W. Hendrickx; R. Qiu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- Also known as
- —
- Updates:
- RFC 6514
Topics
Referenced by
3 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6515IPv4 and IPv6 Infrastructure Addresses in BGP Updates for Multicast VPNCurrent
February 2012
- RFC 7740Simulating Partial Mesh of Multipoint-to-Multipoint (MP2MP) Provider Tunnels with Ingress ReplicationCurrent
January 2016
- RFC 8502L2L3 VPN Multicast MIBCurrent
December 2018
- RFC 8503BGP/MPLS Layer 3 VPN Multicast Management Information BaseCurrent
December 2018
- RFC 8950Advertising IPv4 Network Layer Reachability Information (NLRI) with an IPv6 Next HopCurrent
November 2020
- RFC 6622Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)Obsoleted
May 2012
- RFC 6621Simplified Multicast ForwardingCurrent
May 2012
- RFC 6639Multiprotocol Label Switching Transport Profile (MPLS-TP) MIB-Based Management OverviewCurrent
June 2012
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?