Post BADSV4chNH6aRQ7vGq by rfceditor@mastodon.online
 (DIR) More posts by rfceditor@mastodon.online
 (DIR) Post #BADSUlxclFYQYolrkW by rfceditor@mastodon.online
       0 likes, 0 repeats
       
       RFC 10039: Interconnecting EVPN and IPVPN Domains, J. Rabadan, Ed., et al., https://www.rfc-editor.org/info/rfc10039 #RFC 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 any combination of EVPN and IPVPN domains, it becomes necessary to 1/3
       
 (DIR) Post #BADSV4chNH6aRQ7vGq by rfceditor@mastodon.online
       0 likes, 0 repeats
       
       define the interworking mechanisms among these BGP domains (EVPN and IPVPN) to ensure seamless end-to-end tenant connectivity. This document defines these interworking procedures.  In addition, this document defines a new BGP Path Attribute, referred to as Domain Path (D-PATH), which provides loop prevention for gateway nodes by protecting against control plane loops. The introduction of 2/3
       
 (DIR) Post #BADSV5R2M7N4xXg7jU by rfceditor@mastodon.online
       0 likes, 0 repeats
       
       D-PATH modifies the BGP best-path selection process for Multiprotocol BGP inter-subnet forwarding (ISF) routes of Subsequent Address Family Identifiers (SAFIs) 128 (IPVPN) and 70 (EVPN).  This document is a product of the BGP Enabled ServiceS Working Group of the IETF. 3/3