Wildcards in Multicast VPN Auto-Discovery Routes
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 17
- 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]
- Publication Date
- 2012-05-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC6625- Link
- https://doi.org/10.17487/RFC6625
- Author(s)
- Eric C. RosenYakov RekhterWim HenderickxRay Qiu
- Keyword(s)
- MVPN
Latest version of IETF RFC 6625
Document Versions — IETF RFC 6625
-
▶ IETF RFC 6625 (2012-05-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 4364 [Active*]
- IETF RFC 4601 [Superseded*]
- IETF RFC 4760 [Active*]
- IETF RFC 6513 [Active*]
- IETF RFC 6514 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6625.json
Amends:
IETF RFC 6514 [Active*]
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 6625, Wildcards in Multicast VPN Auto-Discovery Routes. Available at https://doi.org/10.17487/RFC6625
Snippet:
IETF RFC 6625, Wildcards in Multicast VPN Auto-Discovery Routes. Available at https://doi.org/10.17487/RFC6625
HTML (ISO 690 compliant)
Preview:
IETF RFC 6625, Wildcards in Multicast VPN Auto-Discovery Routes. Available at https://doi.org/10.17487/RFC6625
Snippet:
<span class="citation"><cite>IETF RFC 6625</cite>, Wildcards in Multicast VPN Auto-Discovery Routes. Available at <a href="https://doi.org/10.17487/RFC6625" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6625</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6625, Wildcards in Multicast VPN Auto-Discovery Routes
doi: 10.17487/RFC6625
url: https://doi.org/10.17487/RFC6625
doi: 10.17487/RFC6625
url: https://doi.org/10.17487/RFC6625
Snippet:
<li> <cite id="bib-rfc6625">IETF RFC 6625</cite>, Wildcards in Multicast VPN Auto-Discovery Routes <span class="doi">10.17487/RFC6625</span> </li>
Referenced By
- IETF RFC 10018 [Active*]
- IETF RFC 7441 [Active*]
- IETF RFC 7582 [Active*]
- IETF RFC 7900 [Active*]
- IETF RFC 7988 [Active*]
- IETF RFC 8534 [Active*]