A new Request for Comments is now available in online RFC libraries.
RFC 10039
Title: Interconnecting EVPN and IPVPN Domains
Author: J. Rabadan, Ed.,
A. Sajassi, Ed.,
J. Drake,
W. Lin,
J. Uttaro,
A. Simpson
Status: Proposed Standard
Stream: IETF
Date: September 2026
Mailbox: [email protected],
[email protected],
[email protected],
[email protected],
[email protected],
[email protected]
Pages: 31
I-D Tag: draft-ietf-bess-evpn-ipvpn-interworking-18
URL: https://www.rfc-editor.org/info/rfc10039
DOI: 10.17487/RFC10039
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 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 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.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]
