Internet-Draft draft-ietf-bess-evpn-ipvpn-interworking-16.txt is now
available. It is a work item of the BGP Enabled ServiceS (BESS) WG of the
IETF.

   Title:   Interconnecting EVPN and IPVPN Domains
   Authors: J. Rabadan
            A. Sajassi
            E. Rosen
            J. Drake
            W. Lin
            J. Uttaro
            A. Simpson
   Name:    draft-ietf-bess-evpn-ipvpn-interworking-16.txt
   Pages:   38
   Dates:   2026-02-28

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 any combination of EVPN and IPVPN domains, it becomes
   necessary to define the interworking mechanisms among these BGP
   domains (EVPN and VPN-IP) 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 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 inter-subnet forwarding routes of SAFI 128
   (IPVPN) and SAFI 70 (EVPN).  As a result, this specification updates
   the BGP best path selection procedure, but only in the context of
   IPVPN and EVPN route families.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-ipvpn-interworking/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-ipvpn-interworking-16

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-bess-evpn-ipvpn-interworking-16

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
BESS mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to