Nokia

520 Almanor Avenue Sunnyvale CA 94085 United States of America jorge.rabadan@nokia.com

Nokia

520 Almanor Avenue Sunnyvale CA 94085 United States of America kiran.nagaraj@nokia.com

Juniper Networks

wlin@juniper.net

Cisco Systems, Inc.

sajassi@cisco.com

RTG bess EVPN Multihoming split-horizon filtering split horizon filtering local bias ESI encapsulations SHT 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.

Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at .

Copyright Notice Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents () in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.

Table of Contents

• .  Introduction
  • .  Conventions and Terminology
  • .  Split-Horizon Filtering and Tunnel Encapsulations
• .  BGP EVPN Extensions
  • .  The Split-Horizon Type
  • .  Use of the Split-Horizon Type in A-D per ES Routes
  • .  The ESI Label Value in A-D per ES Routes
  • .  Backwards Compatibility with NVEs from RFC 8365
• .  Procedures for NVEs Supporting Multiple Encapsulations
• .  Security Considerations
• .  IANA Considerations
• .  References
  • .  Normative References
  • .  Informative References
• Acknowledgments
• Authors' Addresses

Introduction Ethernet Virtual Private Networks (EVPNs) are commonly used with the following tunnel encapsulations:

• Network Virtualization Overlay (NVO) tunnels, where the EVPN procedures are specified in . MPLSoGRE , MPLSoUDP , Geneve , or VXLAN tunnels are considered NVO tunnels.
• MPLS and Segment Routing over MPLS (SR-MPLS) tunnels, where the relevant EVPN procedures are specified in . SR-MPLS tunneling is specified in .
• Segment Routing over IPv6 (SRv6) tunnels, where the relevant EVPN procedures are specified in . SRv6 is specified in and .

In this document, the term "split horizon" follows the definition in . Split horizon refers to the EVPN multihoming procedure that prevents a Provider Edge (PE) from sending a frame back to a multihomed Customer Edge (CE) when that CE originated the frame in the first place. EVPN multihoming procedures may vary depending on the type of tunnel utilized within the EVPN Broadcast Domain. Specifically, there are two multihoming split-horizon procedures employed to prevent looped frames on multihomed CE devices: the ESI Label-based procedure and the local-bias procedure. The ESI Label-based split-horizon procedure is used for MPLS or MPLS over X (MPLSoX) tunnels, such as MPLSoUDP, and its procedures are detailed in . Conversely, the local-bias procedure is used for IP-based tunnels, such as VXLAN tunnels, and it is described in .

Conventions and Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

AC:

Attachment Circuit

A-D per ES route:

Auto-Discovery per Ethernet Segment route (as defined in ).

Arg.FE2:

Refers to the ESI filtering argument used for split horizon as specified in .

BD:

Broadcast Domain. Refers to an emulated Ethernet, such that two systems on the same BD will receive each other's BUM traffic. In this document, BD also refers to the instantiation of a BD on an EVPN PE. An EVPN PE can be attached to one or multiple BDs of the same tenant.

BUM:

Broadcast, Unknown Unicast, and Multicast

CE:

Customer Edge

DF:

Designated Forwarder. As defined in , an ES may be multihomed (attached to more than one PE). An ES may also contain multiple BDs of one or more EVIs. For each such EVI, one of the PEs attached to the segment becomes that EVI's DF for that segment. Since a BD may belong to only one EVI, we can speak unambiguously of the BD's DF for a given segment.

ES:

Ethernet Segment

ESI:

Ethernet Segment Identifier

EVI:

EVPN Instance

EVI-RT:

EVI Route Target. Refers to a group of NVEs attached to the same EVI that will share the same EVI-RT.

Geneve:

Generic Network Virtualization Encapsulation (see tunnel type 19 in ).

MPLS tunnels and non-MPLS NVO tunnels:

Refers to Multiprotocol Label Switching (or the absence of it) Network Virtualization Overlay tunnels. NVO tunnels use an IP encapsulation for overlay frames, where the source IP address identifies the ingress NVE and the destination IP address identifies the egress NVE.

MPLSoUDP:

Multiprotocol Label Switching over User Datagram Protocol (see tunnel type 13 in ).

MPLSoGRE:

Multiprotocol Label Switching over Generic Network Encapsulation (see tunnel type 11 in ).

MPLSoX:

Refers to MPLS over any IP encapsulation, for example, MPLSoUDP or MPLSoGRE.

NVE:

Network Virtualization Edge

NVGRE:

Network Virtualization Using Generic Routing Encapsulation (see tunnel type 9 in ).

PE:

Provider Edge

RTs:

Route Targets

VXLAN:

Virtual eXtensible Local Area Network (see tunnel type 8 in ).

VXLAN-GPE:

VXLAN Generic Protocol Extension (see tunnel type 12 in ).

SHT:

Split-Horizon Type. Refers to the split-horizon method that a PE intends to use and advertises in an A-D per ES route.

SRv6:

Segment Routing over IPv6 (see and ).

TLV:

Type-Length-Value

This document also assumes familiarity with the terminology of and .

Split-Horizon Filtering and Tunnel Encapsulations EVPN supports two split-horizon filtering mechanisms:

1. ESI Label-based split-horizon filtering : When EVPN is employed for MPLS transport tunnels, an MPLS label facilitates split-horizon filtering to support All-Active multihoming. The ingress NVE device appends a label corresponding to the source ESI (the ESI label) during packet encapsulation. The egress NVE verifies the ESI label when attempting to forward a multi-destination frame through a local ES interface. If the ESI label matches the site identifier (the ESI) associated with that ES interface, then the packet is not forwarded. This mechanism effectively prevents forwarding loops for BUM traffic. ESI Label split-horizon filtering should also be utilized with Single-Active multihoming to prevent transient loops for in-flight packets when the egress NVE assumes the role of DF for an ES.
2. Local-bias filtering : Since IP tunnels such as VXLAN or NVGRE do not support the ESI label or any MPLS label, an alternative split-horizon filtering procedure must be implemented for All-Active multihoming. This mechanism, known as local bias, relies on the source IP address of the tunnel to determine whether to forward BUM traffic to a local ES interface at the egress NVE. In summary and as specified in , each NVE tracks the IP address(es) of other NVEs with which it shares multihomed ESs. Upon receiving a BUM frame encapsulated in an IP tunnel, the egress NVE inspects the source IP address in the tunnel header, which identifies the ingress NVE. The egress NVE then filters out the frame on all local interfaces connected to ESs that are shared with the ingress NVE. Due to this behavior at the egress NVE, the ingress NVE is required to perform local replication to all directly attached ESs, regardless of the DF election state, for all BUM traffic ingressing from the access ACs. This local replication at the ingress NVE is the basis for the term "local bias". Local bias is not suitable for Single-Active multihoming, as the ingress NVE deactivates the ACs for which it is not the DF. Consequently, local replication to non-DF ACs cannot occur, leading to transient in-flight BUM packets being looped back to the originating site by newly elected DF egress NVEs.

specifies that local bias is exclusively utilized for IP tunnels, while ESI Label-based split horizon is employed for IP-based MPLS tunnels. However, IP-based MPLS tunnels such as MPLSoGRE or MPLSoUDP are also categorized as IP tunnels and have the potential to support both procedures. These tunnels are capable of carrying ESI labels and also utilize a tunnel IP header in which the source IP address identifies the ingress NVE. Similarly, certain IP tunnels (those that include an identifier for the source ES in the tunnel header) may also potentially support either procedure. Examples of such tunnels include Geneve and SRv6:

• In a Geneve tunnel, the source IP address identifies the ingress NVE; therefore, local bias is possible. Also, Section 4.1 of defines an Ethernet option Type-Length-Value (TLV) to encode an ESI label value.
• In an SRv6 tunnel, the source IP address identifies the ingress NVE. By default, and as outlined in , the ingress PE adds specific information to the SRv6 packet to enable the egress PE to identify the source ES of the BUM packet. This information is the ESI filtering argument (Arg.FE2) (see and ) of the service Segment Identifier (SID) received on an A-D per ES route from the egress PE.

presents various tunnel encapsulations along with their supported and default split-horizon methods. For Geneve, the default SHT is contingent upon the negotiation of the Ethernet Option with the Source ID TLV. In the case of SRv6, the default SHT is specified as ESI Label filtering in the table, as its behavior is analogous to that of ESI Label filtering. In this document, "ESI Label filtering" refers to the split-horizon filtering based on the presence of a source ES identifier in the tunnel header. This document classifies the tunnel encapsulations used by EVPN into:

1. IP-based MPLS tunnels
2. MPLS and SR-MPLS tunnels
3. IP tunnels
4. SRv6 tunnels

lists the encapsulations supported by this document. Any tunnel encapsulation not listed in is out of scope. Tunnel encapsulations used by EVPN can be categorized into one of the four encapsulation groups mentioned above and support split-horizon filtering based on the following rules:

• IP-based MPLS tunnels and SRv6 tunnels are capable of supporting both split-horizon filtering methods.
• MPLS and SR-MPLS tunnels only support ESI Label-based split-horizon filtering.
• IP tunnels support local-bias split-horizon filtering and may also support ESI Label-based split-horizon filtering, provided they incorporate a mechanism to identify the source ESI in the header.

Tunnel Encapsulations and Split-Horizon Types

Tunnel Encapsulation	Default Split-Horizon Type (SHT)	Supports Local Bias	Supports ESI Label
MPLSoGRE (IP-based MPLS)	ESI Label filtering	Yes	Yes
MPLSoUDP (IP-based MPLS)	ESI Label filtering	Yes	Yes
MPLS and SR-MPLS	ESI Label filtering	No	Yes
VXLAN (IP tunnels)	Local Bias	Yes	No
NVGRE (IP tunnels)	Local Bias	Yes	No
VXLAN-GPE (IP tunnels)	Local Bias	Yes	No
Geneve (IP tunnels)	Local Bias (if no ESI Lb), ESI Label (if ESI lb)	Yes	Yes
SRv6	ESI Label filtering	Yes	Yes

The ESI Label method is applicable for both All-Active and Single-Active configurations, whereas the local-bias method is suitable only for All-Active configurations. Moreover, the ESI Label method is effective across different network domains, while local bias is constrained to networks where there is no change in the next hop between the NVEs attached to the same ES. Nonetheless, some operators favor the local-bias method due to its simplification of the encapsulation process, reduced resource consumption on NVEs, and the fact that the ingress NVE always forwards traffic locally to other interfaces, thereby decreasing the delay in reaching multihomed hosts. This document extends the EVPN multihoming procedures to allow operators to select the preferred split-horizon method for a given NVO tunnel according to their specific requirements. The choice between local bias and ESI Label split horizon is now allowed (by configuration) for tunnel encapsulations that support both methods, and this selection is advertised along with the EVPN A-D per ES route. IP tunnels that do not support both methods, such as VXLAN or NVGRE, will continue to adhere to the procedures specified in . Note that this document does not modify the local bias or the ESI Label split-horizon procedures themselves, just focuses on the signaling and selection of the split-horizon method to apply by the multihomed NVEs.

BGP EVPN Extensions Extensions to EVPN are required to enable NVEs to advertise their preferred split-horizon method for a given ES. illustrates the ESI Label extended community (), which is consistently advertised alongside the EVPN A-D per ES route. All NVEs connected to an ES advertise an A-D per ES route for that ES, including the extended community, which communicates information regarding the multihoming mode (either All-Active or Single-Active) and, if necessary, specifies the ESI Label to be utilized.

ESI Label Extended Community 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=0x06 | Sub-Type=0x01 | Flags(1 octet)| Reserved=0 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reserved=0 | ESI Label | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

defines the low-order bit of the Flags octet (bit 0) as the "Single-Active" bit:

• A value of 0 means that the multihomed ES is operating in All-Active multihoming redundancy mode.
• A value of 1 means that the multihomed ES is operating in Single-Active multihoming redundancy mode.

establishes a registry for the Flags octet, designating the "Single-Active" bit as the low-order bit of the newly defined Multihoming Redundancy Mode field.

The Split-Horizon Type does not include any explicit indication regarding the split-horizon method in the A-D per ES route. In this document, the split-horizon procedure defined in is considered the default behavior, presuming that local bias is employed exclusively for IP tunnels, while ESI Label-based split horizon is used for IP-based MPLS tunnels. This document specifies that the two high-order bits in the Flags octet (bits 6 and 7) constitute the "Split-Horizon Type" or "SHT" field, where: 7 6 5 4 3 2 1 0 +-+-+-+-+-+-+-+-+ |SHT| |RED| +-+-+-+-+-+-+-+-+ RED = "Multihoming Redundancy Mode" field (see Table 2) SHT bit 7 6 ----------- 0 0 --> Default SHT Backwards compatible with [RFC8365] and [RFC7432] 0 1 --> Local Bias 1 0 --> ESI Label-based filtering 1 1 --> Unassigned

• SHT = 00 is backwards compatible with and , and indicates that the advertising NVE intends to use the default or built-in SHT. The default SHT is shown in for each encapsulation. An egress NVE that follows the behavior and does not support this specification will ignore the SHT bits (which is equivalent to processing them as a value of 00).
• SHT = 01 indicates that the advertising NVE intends to use local-bias procedures in the ES for which the AD per-ES route is advertised.
• SHT = 10 indicates that the advertising NVE intends to use the ESI Label-based split-horizon method procedures in the ES for which the AD per-ES route is advertised.
• SHT = 11 is Unassigned.

Use of the Split-Horizon Type in A-D per ES Routes The following behavior is observed:

• An SHT value of 01 or 10 MUST NOT be used with encapsulations that support only one SHT in , and MAY be used by encapsulations that support the two SHTs in .
• An SHT value different than 00 expresses the intent to use a specific split-horizon method, but does not reflect the actual operational SHT used by the advertising NVE, unless all the NVEs attached to the ES advertise the same SHT.
• In case of an inconsistency in the SHT value advertised by the NVEs attached to the same ES for a given EVI, all the NVEs MUST revert to the behavior in and use the default SHT in , irrespective of the advertised SHT.
• An SHT different than 00 MUST NOT be set if the "Single-Active" bit is set. A received A-D per ES route where the "Single-Active" and SHT bits are different than zero MUST follow the treat-as-withdraw behavior in .
• The SHT MUST have the same value in each Ethernet A-D per ES route that an NVE advertises for a given ES and a given encapsulation (see for NVEs supporting multiple encapsulations).

As an example, egress NVEs that support IP-based MPLS tunnels, such as MPLSoGRE or MPLSoUDP, will advertise A-D per ES routes for the ES along with the BGP Encapsulation Extended Community, as defined in . This extended community indicates the encapsulation type (MPLSoGRE or MPLSoUDP) and may use the SHT value of 01 or 10 to signify the intent to use local bias or the ESI Label, respectively. An egress NVE MUST NOT use an SHT value other than 00 when advertising an A-D per ES route with the following tunnel encapsulation types from : VXLAN (type 8), NVGRE (type 9), MPLS (type 10), or no BGP Tunnel Encapsulation Extended Community at all. In all these cases, it is presumed that there is no choice for the split-horizon method; therefore, the SHT value MUST be set to 00. If a route with any of the mentioned encapsulation options is received and has an SHT value different than 00, it SHOULD apply the treat-as-withdraw behavior, per . An egress NVE advertising A-D per ES route(s) for an ES with Geneve encapsulation (tunnel encapsulation type 19 in the BGP Tunnel Encapsulation attribute ) MAY use an SHT value of 01 or 10. A value of 01 indicates the intent to use local bias, regardless of the presence of an Ethernet option TLV with a non-zero Source-ID, as described in . A value of 10 indicates the intent to use ESI Label-based split horizon, and it is only valid if an Ethernet option TLV with a non-zero Source-ID is present. A value of 00 indicates the default behavior outlined in , which is to use local bias if:

1. no ESI Label is present in the Ethernet option TLV, or
2. there is no Ethernet option TLV.

Otherwise, the ESI Label split-horizon method is applied. These procedures assume a single encapsulation supported in the egress NVE. describes additional procedures for NVEs supporting multiple encapsulations.

The ESI Label Value in A-D per ES Routes This document also updates regarding the value that is advertised in the ESI Label field of the ESI Label extended community, as follows:

• The A-D per ES route(s) for an ES MAY have an ESI Label value of zero if the SHT value is 01. specifies the scenarios where the SHT can be 01. An ESI Label value of zero eliminates the need to allocate labels in cases where they are not utilized, such as in the local-bias method.
• The A-D per ES route(s) for an ES MAY have an ESI Label value of zero for VXLAN or NVGRE encapsulations.

Backwards Compatibility with NVEs from RFC 8365 As discussed in , this specification is backwards compatible with the split-horizon filtering behavior in and a non-upgraded NVE can be attached to the same ES as other NVEs supporting this specification. An NVE maintains an administrative SHT value for an ES, which is advertised alongside the A-D per ES route, and an operational SHT value, which is the one actually used regardless of what the NVE has advertised. The administrative SHT matches the operational SHT if all the NVEs attached to the ES have the same administrative SHT. This document assumes that an implementation of or that does not support the specifications in this document will ignore the values of all the Flags in the ESI Label extended community, except for the "Single-Active" bit. Based on this assumption, a non-upgraded NVE will disregard any SHT value other than 00. If an upgraded NVE receives at least one A-D per ES route for the ES with an SHT value of 00, it MUST revert its operational SHT to the default split-horizon method, as described in , irrespective of its administrative SHT. For instance, consider an NVE attached to ES N that receives two A-D per ES routes for N from different NVEs, NVE1 and NVE2. If the route from NVE1 has an SHT value of 00 and the one from NVE2 has an SHT value of 01, the NVE MUST use the default split-horizon method specified in as its operational SHT, regardless of its administrative SHT. All NVEs attached to an ES with an operational SHT value of 10 MUST advertise a valid, non-zero ESI Label. If the operational SHT value is 01, the ESI Label MAY be zero. If the operational SHT value is 00, the ESI Label may be zero only if the default encapsulation supports local bias exclusively, and the NVEs do not require the presence of a valid, non-zero ESI Label. If an NVE changes its operational SHT value from 01 (Local Bias) to 00 (Default SHT) due to the presence of a new non-upgraded NVE in the ES, and it previously advertised a zero ESI Label, it MUST send an update with a valid, non-zero ESI Label, unless all the non-upgraded NVEs in the ES support only local bias. For example, consider NVE1 and NVE2 using MPLSoUDP as encapsulation, attached to the same Ethernet Segment ES1, and advertising an SHT value of 01 (Local Bias) with a zero ESI Label value. Suppose NVE3, which does not support this specification, joins ES1 and advertises an SHT value of 00 (default). Upon receiving NVE3's A-D per ES route, NVE1 and NVE2 MUST update their A-D per ES routes for ES1 to include a valid, non-zero ESI Label value. The assumption here is that NVE3 only supports the default ESI Label-based split-horizon filtering.

Procedures for NVEs Supporting Multiple Encapsulations As specified in , an NVE that supports multiple data plane encapsulations (e.g., VXLAN, NVGRE, MPLS, MPLSoUDP, Geneve) must indicate all supported encapsulations using BGP Encapsulation extended communities as defined in for all EVPN routes. This section provides clarification on the multihoming split-horizon behavior for NVEs that advertise and receive multiple BGP Encapsulation extended communities along with the A-D per ES routes. This section uses the notation {x, y} (more than two encapsulations is possible too) to denote the encapsulations advertised in BGP Encapsulation extended communities (or the BGP Tunnel Encapsulation Attribute), where x and y represent different encapsulation values. When Geneve is one of the encapsulations, the tunnel type is indicated in either a BGP Encapsulation extended community or a BGP Tunnel Encapsulation Attribute. It is important to note that an NVE MAY advertise multiple A-D per ES routes for the same ES, rather than a single route, with each route conveying a set of Route Targets (RTs). The total set of RTs associated with a given ES is referred to as the RT-set for that ES. Each of the EVIs represented in the RT-set will have its RT included in one, and only one, A-D per ES route for the ES. When multiple A-D per ES routes are advertised for the same ES, each route must have a distinct Route Distinguisher. As per , an NVE that advertises multiple encapsulations in the A-D per ES route(s) for an ES MUST advertise encapsulations that use the same split-horizon filtering method in the same route. For example:

• An A-D per ES route for ES-x may be advertised with {VXLAN, NVGRE} encapsulations.
• An A-D per ES route for ES-y may be advertised with {MPLS, MPLSoUDP, MPLSoGRE} encapsulations (or a subset).
• However, an A-D per ES route for ES-z MUST NOT be advertised with {MPLS, VXLAN} encapsulations.

This document extends the described behavior as follows:

1. An A-D per ES route for ES-x may be advertised with multiple encapsulations, some of which support a single split-horizon method. In this case, the SHT value MUST be 00. For instance, encapsulations such as {VXLAN, NVGRE}, {VXLAN, Geneve}, or {MPLS, MPLSoGRE, MPLSoUDP} can be advertised in an A-D per ES route. In all these cases, the SHT value MUST be 00 and the treat-as-withdraw behavior is applied in case of any other value.
2. An A-D per ES route for ES-y may be advertised with multiple encapsulations that all support both split-horizon methods. In this case, the SHT value MAY be 01 if the preferred method is local bias, or 10 if the ESI Label-based method is desired. For example, encapsulations such as {MPLSoGRE, MPLSoUDP, Geneve} (or a subset) MAY be advertised in an A-D per ES route with an SHT value of 01. The ESI Label value in this case MAY be zero.
3. If ES-z with an RT-set composed of (RT1, RT2, RT3.. RTn) supports multiple encapsulations requiring different split-horizon methods, a distinct A-D per ES route (or group of routes) per split-horizon method MUST be advertised. For example, consider an ES-z with n RTs, where:
   • the EVIs corresponding to (RT1..RTi) support VXLAN,
   • the ones for (RTi+1..RTm) (with i<m) support MPLSoUDP with local bias, and
   • the ones for (RTm+1..RTn) (with m<n) support Geneve with ESI Label-based split horizon.
   In this scenario, three groups of A-D per ES routes MUST be advertised for ES-z:
   • A-D per ES route group 1, including (RT1..RTi) with encapsulation {VXLAN} and an SHT value of 00. The ESI Label MAY be zero.
   • A-D per ES route group 2, including (RTi+1..RTm) with encapsulation {MPLSoUDP} and an SHT value of 01. The ESI Label MAY be zero.
   • A-D per ES route group 3, including (RTm+1..RTn) with encapsulation {Geneve} and an SHT value of 10. The ESI Label MUST have a valid, non-zero value, and the Ethernet option as defined in MUST be advertised.

As per , it is the responsibility of the operator of a given EVI to ensure that all of the NVEs within that EVI support a common encapsulation. Failure to meet this condition may result in service disruption or failure.

Security Considerations All the security considerations described in are applicable to this document. Additionally, this document modifies the procedures for split-horizon filtering as outlined in , offering operators a choice between local bias and ESI Label-based filtering for tunnels that support both methods. Misconfiguration of the desired SHT could lead to forwarding behaviors that differ from the intended configuration. Apart from this risk, this document describes procedures to ensure that all PE devices or NVEs connected to the same ES agree on a common SHT method, with a fallback to a default behavior in case of a mismatch in the SHT bits being advertised by any two PEs or NVEs in the ES. Consequently, unauthorized changes to the SHT configuration by an attacker on a single PE or NVE of the ES should not cause traffic disruption (as long as the SHT value is valid as per this document) but may result in alterations to forwarding behavior.

IANA Considerations Per this document, IANA has created the "EVPN ESI Label Extended Community Flags" registry for the 1-octet Flags field in the ESI Label Extended Community , as follows:

Bit Position	Name	Reference
0-1	Multihoming Redundancy Mode
2-5	Unassigned
6-7	Split-Horizon Type	RFC 9746

IANA has also created the "Multihoming Redundancy Mode" registry for the related field of the "EVPN ESI Label Extended Community Flags". The registry has been populated with the following initial values:

Value	Multihoming Redundancy Mode	Reference
00	All-Active
01	Single-Active
10	Unassigned
11	Unassigned

Finally, IANA has created the "Split-Horizon Type" registry for the related field of the "EVPN ESI Label Extended Community Flags". The registry has been populated with the following initial values:

Value	Split-Horizon Type Value	Reference
00	Default SHT	RFC 9746
01	Local Bias	RFC 9746
10	ESI Label-based filtering	RFC 9746
11	Unassigned

New registrations in the "EVPN ESI Label Extended Community Flags", "Multihoming Redundancy Mode", and "Split-Horizon Type" registries will be made through the "IETF Review" procedure defined in . These registries are located in the "Border Gateway Protocol (BGP) Extended Communities" registry group.

References Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This document describes procedures for BGP MPLS-based Ethernet VPNs (EVPN). The procedures described here meet the requirements specified in RFC 7209 -- "Requirements for Ethernet VPN (EVPN)". Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA). To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry. This is the third edition of this document; it obsoletes RFC 5226. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This document specifies how Ethernet VPN (EVPN) can be used as a Network Virtualization Overlay (NVO) solution and explores the various tunnel encapsulation options over IP and their impact on the EVPN control plane and procedures. In particular, the following encapsulation options are analyzed: Virtual Extensible LAN (VXLAN), Network Virtualization using Generic Routing Encapsulation (NVGRE), and MPLS over GRE. This specification is also applicable to Generic Network Virtualization Encapsulation (GENEVE); however, some incremental work is required, which will be covered in a separate document. This document also specifies new multihoming procedures for split-horizon filtering and mass withdrawal. It also specifies EVPN route constructions for VXLAN/NVGRE encapsulations and Autonomous System Border Router (ASBR) procedures for multihoming of Network Virtualization Edge (NVE) devices. This document defines procedures and messages for SRv6-based BGP services, including Layer 3 Virtual Private Network (L3VPN), Ethernet VPN (EVPN), and Internet services. It builds on "BGP/MPLS IP Virtual Private Networks (VPNs)" (RFC 4364) and "BGP MPLS-Based Ethernet VPN" (RFC 7432). Informative References Ciena Cisco Systems Juniper Networks Nokia Google This document describes how Ethernet VPN (EVPN) control plane can be used with Network Virtualization Overlay over Layer 3 (NVO3) Generic Network Virtualization Encapsulation (Geneve) encapsulation for NVO3 solutions. EVPN control plane can also be used by Network Virtualization Edges (NVEs) to express Geneve tunnel option TLV(s) supported in the transmission and/or reception of Geneve encapsulated data packets. Work in Progress Various applications of MPLS make use of label stacks with multiple entries. In some cases, it is possible to replace the top label of the stack with an IP-based encapsulation, thereby enabling the application to run over networks that do not have MPLS enabled in their core routers. This document specifies two IP-based encapsulations: MPLS-in-IP and MPLS-in-GRE (Generic Routing Encapsulation). Each of these is applicable in some circumstances. [STANDARDS-TRACK] This document describes Virtual eXtensible Local Area Network (VXLAN), which is used to address the need for overlay networks within virtualized data centers accommodating multiple tenants. The scheme and the related protocols can be used in networks for cloud service providers and enterprise data centers. This memo documents the deployed VXLAN protocol for the benefit of the Internet community. This document specifies an IP-based encapsulation for MPLS, called MPLS-in-UDP for situations where UDP (User Datagram Protocol) encapsulation is preferred to direct use of MPLS, e.g., to enable UDP-based ECMP (Equal-Cost Multipath) or link aggregation. The MPLS- in-UDP encapsulation technology must only be deployed within a single network (with a single network operator) or networks of an adjacent set of cooperating network operators where traffic is managed to avoid congestion, rather than over the Internet where congestion control is required. Usage restrictions apply to MPLS-in-UDP usage for traffic that is not congestion controlled and to UDP zero checksum usage with IPv6. According to the base BGP specification, a BGP speaker that receives an UPDATE message containing a malformed attribute is required to reset the session over which the offending attribute was received. This behavior is undesirable because a session reset would impact not only routes with the offending attribute but also other valid routes exchanged over the session. This document partially revises the error handling for UPDATE messages and provides guidelines for the authors of documents defining new attributes. Finally, it revises the error handling procedures for a number of existing attributes. This document updates error handling for RFCs 1997, 4271, 4360, 4456, 4760, 5543, 5701, and 6368. This document describes the usage of the Generic Routing Encapsulation (GRE) header for Network Virtualization (NVGRE) in multi-tenant data centers. Network Virtualization decouples virtual networks and addresses from physical network infrastructure, providing isolation and concurrency between multiple virtual networks on the same physical network infrastructure. This document also introduces a Network Virtualization framework to illustrate the use cases, but the focus is on specifying the data-plane aspect of NVGRE. Segment Routing (SR) leverages the source routing paradigm. A node steers a packet through an ordered list of instructions, called "segments". A segment can represent any instruction, topological or service based. A segment can have a semantic local to an SR node or global within an SR domain. SR provides a mechanism that allows a flow to be restricted to a specific topological path, while maintaining per-flow state only at the ingress node(s) to the SR domain. SR can be directly applied to the MPLS architecture with no change to the forwarding plane. A segment is encoded as an MPLS label. An ordered list of segments is encoded as a stack of labels. The segment to process is on the top of the stack. Upon completion of a segment, the related label is popped from the stack. SR can be applied to the IPv6 architecture, with a new type of routing header. A segment is encoded as an IPv6 address. An ordered list of segments is encoded as an ordered list of IPv6 addresses in the routing header. The active segment is indicated by the Destination Address (DA) of the packet. The next active segment is indicated by a pointer in the new routing header. Segment Routing (SR) leverages the source-routing paradigm. A node steers a packet through a controlled set of instructions, called segments, by prepending the packet with an SR header. In the MPLS data plane, the SR header is instantiated through a label stack. This document specifies the forwarding behavior to allow instantiating SR over the MPLS data plane (SR-MPLS). Segment Routing can be applied to the IPv6 data plane using a new type of Routing Extension Header called the Segment Routing Header (SRH). This document describes the SRH and how it is used by nodes that are Segment Routing (SR) capable. Network virtualization involves the cooperation of devices with a wide variety of capabilities such as software and hardware tunnel endpoints, transit fabrics, and centralized control clusters. As a result of their role in tying together different elements of the system, the requirements on tunnels are influenced by all of these components. Therefore, flexibility is the most important aspect of a tunneling protocol if it is to keep pace with the evolution of technology. This document describes Geneve, an encapsulation protocol designed to recognize and accommodate these changing capabilities and needs. The Segment Routing over IPv6 (SRv6) Network Programming framework enables a network operator or an application to specify a packet processing program by encoding a sequence of instructions in the IPv6 packet header. Each instruction is implemented on one or several nodes in the network and identified by an SRv6 Segment Identifier in the packet. This document defines the SRv6 Network Programming concept and specifies the base set of SRv6 behaviors that enables the creation of interoperable overlays with underlay optimization. This document defines a BGP path attribute known as the "Tunnel Encapsulation attribute", which can be used with BGP UPDATEs of various Subsequent Address Family Identifiers (SAFIs) to provide information needed to create tunnels and their corresponding encapsulation headers. It provides encodings for a number of tunnel types, along with procedures for choosing between alternate tunnels and routing packets into tunnels. This document obsoletes RFC 5512, which provided an earlier definition of the Tunnel Encapsulation attribute. RFC 5512 was never deployed in production. Since RFC 5566 relies on RFC 5512, it is likewise obsoleted. This document updates RFC 5640 by indicating that the Load-Balancing Block sub-TLV may be included in any Tunnel Encapsulation attribute where load balancing is desired. IANA Cisco Systems Arrcus Intel This document describes extending Virtual eXtensible Local Area Network (VXLAN), via changes to the VXLAN header, with four new capabilities: support for multi-protocol encapsulation, support for operations, administration and maintenance (OAM) signaling, support for ingress-replicated BUM Traffic (i.e. Broadcast, Unknown unicast, or Multicast), and explicit versioning. New protocol capabilities can be introduced via shim headers. Work in Progress

Acknowledgments The authors would like to thank , , and for their review and useful comments. Thanks to and as well, for their thorough review.

Authors' Addresses Nokia

520 Almanor Avenue Sunnyvale CA 94085 United States of America jorge.rabadan@nokia.com

Nokia

520 Almanor Avenue Sunnyvale CA 94085 United States of America kiran.nagaraj@nokia.com

Juniper Networks

wlin@juniper.net

Cisco Systems, Inc.

sajassi@cisco.com