A new Request for Comments is now available in online RFC libraries.
RFC 9746
Title: BGP EVPN Multihoming Extensions for
Split-Horizon Filtering
Author: J. Rabadan,
K. Nagaraj,
W. Lin,
A. Sajassi
Status: Standards Track
Stream: IETF
Date: March 2025
Mailbox: [email protected],
[email protected],
[email protected],
[email protected]
Pages: 17
Updates: RFC 7432, RFC 8365
I-D Tag: draft-ietf-bess-evpn-mh-split-horizon-11.txt
URL: https://www.rfc-editor.org/info/rfc9746
DOI: 10.17487/RFC9746
An Ethernet Virtual Private Network (EVPN) is commonly used with
Network Virtualization Overlay (NVO) tunnels as well as with MPLS and
Segment Routing (SR) tunnels. The multihoming procedures in EVPN may
vary based on the type of tunnel used within the EVPN Broadcast
Domain. Specifically, there are two multihoming split-horizon
procedures designed to prevent looped frames on multihomed Customer
Edge (CE) devices: the Ethernet Segment Identifier (ESI) Label-based
procedure and the local-bias procedure. The ESI Label-based
split-horizon procedure is applied to MPLS-based tunnels such as MPLS
over UDP (MPLSoUDP), while the local-bias procedure is used for other
tunnels such as Virtual eXtensible Local Area Network (VXLAN)
tunnels.
Current specifications do not allow operators to choose which
split-horizon procedure to use for tunnel encapsulations that support
both methods. Examples of tunnels that may support both procedures
include MPLSoUDP, MPLS over GRE (MPLSoGRE), Generic Network
Virtualization Encapsulation (Geneve), and Segment Routing over IPv6
(SRv6) tunnels. This document updates the EVPN multihoming procedures
described in RFCs 7432 and 8365, enabling operators to select the
split-horizon procedure that meets their specific requirements.
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 [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org
