Wildcards in Multicast VPN Auto-Discovery Routes
RFC 6625, “Wildcards in Multicast VPN Auto-Discovery Routes”, is a Proposed Standard document published in May 2012 by E. Rosen, Y. Rekhter, W. Hendrickx, R. Qiu. It updates RFC 6514. It has since been updated by RFC 7582, RFC 7900, RFC 8534. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6625 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6624 Layer 2 Virtual Private Networks Using BGP for Auto-Discovery and Signaling
- RFC 6626 Dynamic Prefix Allocation for Network Mobility for Mobile IPv4
- RFC 6623 IANA Registry for MEDIACTRL Interactive Voice Response Control Package
- RFC 6627 Overview of Pre-Congestion Notification Encoding
- RFC 6622 Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks
- RFC 6628 Efficient Augmented Password-Only Authentication and Key Exchange for IKEv2
- RFC 6621 Simplified Multicast Forwarding
- RFC 6629 Considerations on the Application of the Level 3 Multihoming Shim Protocol for IPv6