The IESG has received a request from the BGP Enabled ServiceS WG (bess) to
consider the following document: - 'EVPN Multi-Homing Extensions for Split
Horizon Filtering'
  <draft-ietf-bess-evpn-mh-split-horizon-09.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-c...@ietf.org mailing lists by 2024-07-09. Exceptionally, comments may
be sent to i...@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   Ethernet Virtual Private Network (EVPN) is commonly used with Network
   Virtualization Overlay (NVO) tunnels, as well as MPLS and Segment
   Routing tunnels.  The multi-homing procedures in EVPN may vary based
   on the type of tunnel used within the EVPN Broadcast Domain.
   Specifically, there are two multi-homing Split Horizon procedures
   designed to prevent looped frames on multi-homed Customer Edge (CE)
   devices: the ESI Label-based procedure and the Local Bias procedure.
   The ESI Label-based Split Horizon is applied to MPLS-based tunnels,
   such as MPLSoUDP, while the Local Bias procedure is used for other
   tunnels, such as VXLAN.

   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 MPLSoGRE, MPLSoUDP, GENEVE, and SRv6.  This document updates
   the EVPN multi-homing procedures described in RFC 8365 and RFC 7432,
   enabling operators to select the appropriate Split Horizon procedure
   for a given tunnel based on their specific requirements.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-mh-split-horizon/



No IPR declarations have been submitted directly on this I-D.





_______________________________________________
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

Reply via email to