A new Request for Comments is now available in online RFC libraries.
RFC 9573
Title: MVPN/EVPN Tunnel Aggregation with Common Labels
Author: Z. Zhang,
E. Rosen,
W. Lin,
Z. Li,
IJ. Wijnands
Status: Standards Track
Stream: IETF
Date: May 2024
Mailbox: zzh...@juniper.net,
erose...@gmail.com,
w...@juniper.net,
lizhen...@huawei.com,
i...@braindump.be
Pages: 14
Updates: RFC 6514, RFC 7432, RFC 7582
I-D Tag: draft-ietf-bess-mvpn-evpn-aggregation-label-14.txt
URL: https://www.rfc-editor.org/info/rfc9573
DOI: 10.17487/RFC9573
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.
This document is a product of the BGP Enabled ServiceS Working Group of the
IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org
