The IESG has received a request from the BGP Enabled ServiceS WG (bess) to consider the following document: - 'EVPN Interworking with IPVPN' <draft-ietf-bess-evpn-ipvpn-interworking-15.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 [email protected] mailing lists by 2025-12-18. Exceptionally, comments may be sent to [email protected] instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract Ethernet Virtual Private Network (EVPN) provides a unified BGP control plane for both intra- and inter-subnet forwarding within tenant networks. When a tenant network spans multiple domains — including EVPN domains as well as domains that use BGP VPN-IP or IP address families for inter-subnet forwarding — it becomes necessary to define the interworking mechanisms among these BGP domains (EVPN, VPN-IP, and IP) to ensure seamless end-to-end tenant connectivity. In addition, this document defines a new BGP Path Attribute, referred to as D-PATH (Domain PATH), which provides loop prevention for gateway nodes by protecting against control plane loops. The introduction of D-PATH modifies the BGP best path selection process for Multiprotocol BGP routes of SAFI 128 (IPVPN) and EVPN IP Prefix routes. As a result, this specification updates the BGP best path selection procedure, but only in the context of IPVPN and EVPN route families. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-ipvpn-interworking/ No IPR declarations have been submitted directly on this I-D. _______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
