| rfc9746v2.txt | rfc9746.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) J. Rabadan, Ed. | Internet Engineering Task Force (IETF) J. Rabadan, Ed. | |||
| Request for Comments: 9746 K. Nagaraj | Request for Comments: 9746 K. Nagaraj | |||
| Updates: 7432, 8365 Nokia | Updates: 7432, 8365 Nokia | |||
| Category: Standards Track W. Lin | Category: Standards Track W. Lin | |||
| ISSN: 2070-1721 Juniper | ISSN: 2070-1721 Juniper | |||
| A. Sajassi | A. Sajassi | |||
| Cisco | Cisco | |||
| February 2025 | March 2025 | |||
| BGP EVPN Multihoming Extensions for Split Horizon Filtering | BGP EVPN Multihoming Extensions for Split-Horizon Filtering | |||
| Abstract | Abstract | |||
| An Ethernet Virtual Private Network (EVPN) is commonly used with | An Ethernet Virtual Private Network (EVPN) is commonly used with | |||
| Network Virtualization Overlay (NVO) tunnels as well as with MPLS and | Network Virtualization Overlay (NVO) tunnels as well as with MPLS and | |||
| Segment Routing (SR) tunnels. The multihoming procedures in EVPN may | Segment Routing (SR) tunnels. The multihoming procedures in EVPN may | |||
| vary based on the type of tunnel used within the EVPN Broadcast | vary based on the type of tunnel used within the EVPN Broadcast | |||
| Domain. Specifically, there are two multihoming split-horizon | Domain. Specifically, there are two multihoming split-horizon | |||
| procedures designed to prevent looped frames on multihomed Customer | procedures designed to prevent looped frames on multihomed Customer | |||
| Edge (CE) devices: the Ethernet Segment Identifier (ESI) Label-based | Edge (CE) devices: the Ethernet Segment Identifier (ESI) Label-based | |||
| skipping to change at line 450 ¶ | skipping to change at line 450 ¶ | |||
| (which is equivalent to processing them as a value of 00). | (which is equivalent to processing them as a value of 00). | |||
| * SHT = 01 indicates that the advertising NVE intends to use local- | * SHT = 01 indicates that the advertising NVE intends to use local- | |||
| bias procedures in the ES for which the AD per-ES route is | bias procedures in the ES for which the AD per-ES route is | |||
| advertised. | advertised. | |||
| * SHT = 10 indicates that the advertising NVE intends to use the ESI | * SHT = 10 indicates that the advertising NVE intends to use the ESI | |||
| Label-based split-horizon method procedures in the ES for which | Label-based split-horizon method procedures in the ES for which | |||
| the AD per-ES route is advertised. | the AD per-ES route is advertised. | |||
| * SHT = 11 is a reserved value, for future use. | * SHT = 11 is Unassigned. | |||
| 2.2. Use of the Split-Horizon Type in A-D per ES Routes | 2.2. Use of the Split-Horizon Type in A-D per ES Routes | |||
| The following behavior is observed: | The following behavior is observed: | |||
| * An SHT value of 01 or 10 MUST NOT be used with encapsulations that | * An SHT value of 01 or 10 MUST NOT be used with encapsulations that | |||
| support only one SHT in Table 1, and MAY be used by encapsulations | support only one SHT in Table 1, and MAY be used by encapsulations | |||
| that support the two SHTs in Table 1. | that support the two SHTs in Table 1. | |||
| * An SHT value different than 00 expresses the intent to use a | * An SHT value different than 00 expresses the intent to use a | |||
| End of changes. 3 change blocks. | ||||
| 3 lines changed or deleted | 3 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||