API Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 9573
[ACTIVE]

MVPN/EVPN Tunnel Aggregation with Common Labels

Metadata

Publisher
IETF
Doc Type
Standard
Pages
14
Abstract
The Multicast VPN (MVPN) specifications allow a single Point-to-Multipoint (P2MP) tunnel to carry traffic of multiple IP VPNs (referred to as VPNs in this document). The EVPN specifications allow a single P2MP tunnel to carry traffic of multiple Broadcast Domains (BDs). These features require the ingress router of the P2MP tunnel to allocate an upstream-assigned MPLS label for each VPN or for each BD. A packet sent on a P2MP tunnel then carries the label that is mapped to its VPN or BD (in some cases, a distinct upstream-assigned label is needed for each flow.) Since each ingress router allocates labels independently, with no coordination among the ingress routers, the egress routers may need to keep track of a large number of labels. The number of labels may need to be as large as, or larger than, the product of the number of ingress routers times the number of VPNs or BDs. However, the number of labels can be greatly reduced if the association between a label and a VPN or BD is made by provisioning, so that all ingress routers assign the same label to a particular VPN or BD. New procedures are needed in order to take advantage of such provisioned labels. These new procedures also apply to Multipoint-to-Multipoint (MP2MP) tunnels. This document updates RFCs 6514, 7432, and 7582 by specifying the necessary procedures.
Publication Date
2024-05-01
Status Note
Proposed Standard
DOI
10.17487/RFC9573
Link
https://doi.org/10.17487/RFC9573
Author(s)
Zhaohui (Jeffrey) Zhang
Eric C. Rosen
Wen Lin
Zhenbin Li
IJsbrand Wijnands
Keyword(s)
DCB, Tunnel Aggregation
Latest version of IETF RFC 9573

Document Versions — IETF RFC 9573

  • ▶ IETF RFC 9573 (2024-05-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC9573.json

Amends:
IETF RFC 6514 [Active*]
IETF RFC 7432 [Active*]
IETF RFC 7582 [Active*]

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 9573, MVPN/EVPN Tunnel Aggregation with Common Labels. Available at https://doi.org/10.17487/RFC9573
Snippet:
IETF RFC 9573, MVPN/EVPN Tunnel Aggregation with Common Labels. Available at https://doi.org/10.17487/RFC9573

HTML (ISO 690 compliant)

Preview:
IETF RFC 9573, MVPN/EVPN Tunnel Aggregation with Common Labels. Available at https://doi.org/10.17487/RFC9573
Snippet:
<span class="citation"><cite>IETF RFC 9573</cite>, MVPN/EVPN Tunnel Aggregation with Common Labels. Available at <a href="https://doi.org/10.17487/RFC9573" target="_blank" rel="noopener">https://doi.org/10.17487/RFC9573</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 9573, MVPN/EVPN Tunnel Aggregation with Common Labels
doi: 10.17487/RFC9573
url: https://doi.org/10.17487/RFC9573
Snippet:
<li>
<cite id="bib-rfc9573">IETF RFC 9573</cite>, MVPN/EVPN Tunnel Aggregation with Common Labels
<span class="doi">10.17487/RFC9573</span>
</li>

Referenced By