Last Call: <draft-ietf-bess-evpn-ipvpn-interworking-15.txt> (EVPN Interworking with IPVPN) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Thu, 04 December 2025 20:41 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-bess-evpn-ipvpn-interworking-15.txt> (EVPN Interworking with IPVPN) to Proposed Standard
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Message-ID: <176488091701.155624.11347159190727152872@dt-datatracker-5bd94c585b-wk4l4>
Date: Thu, 04 Dec 2025 12:41:57 -0800
Message-ID-Hash: UNQP2BA7PKFF4IH5VKAAMA5VJ5SBZ2AU
CC: bess-chairs@ietf.org, bess@ietf.org, draft-ietf-bess-evpn-ipvpn-interworking@ietf.org, gunter@vandevelde.cc
Reply-To: last-call@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/FHux0DKIN1gi-ck7n50-Uv1_qVM>

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
last-call@ietf.org mailing lists by 2025-12-18. Exceptionally, comments may
be sent to iesg@ietf.org 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.

Last Call: <draft-ietf-bess-evpn-ipvpn-interworki… The IESG