RFC 9746: BGP EVPN Multihoming Extensions for Split-Horizon Filtering
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9746
- Published
- March 2025
- Authors
- J. Rabadan; K. Nagaraj; W. Lin; A. Sajassi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9747Unaffiliated Bidirectional Forwarding Detection (BFD) EchoCurrent
March 2025
- RFC 9744EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) ServiceCurrent
March 2025
- RFC 9752Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCECurrent
April 2025
- RFC 9739Protocol Independent Multicast Light (PIM Light)Current
March 2025
- RFC 9753Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) ObjectsCurrent
April 2025
- RFC 9756Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error CodesCurrent
March 2025
- RFC 9735Locator/ID Separation Protocol (LISP) Distinguished Name EncodingCurrent
February 2025
- RFC 9757Path Computation Element Communication Protocol (PCEP) Extensions for Native IP NetworksCurrent
March 2025
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?