EVPN Interworking with IPVPN
draft-ietf-bess-evpn-ipvpn-interworking-11
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Authors | Jorge Rabadan , Ali Sajassi , Eric C. Rosen , John Drake , Wen Lin , Jim Uttaro , Adam Simpson | ||
Last updated | 2024-12-26 (Latest revision 2024-06-24) | ||
Replaces | draft-rabadan-sajassi-bess-evpn-ipvpn-interworking | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | In WG Last Call | |
Document shepherd | Stephane Litkowski | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Yes | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | slitkows.ietf@gmail.com |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Ethernet Virtual Private Network (EVPN) is used as a unified control plane for tenant network intra and inter-subnet forwarding. When a tenant network spans not only EVPN domains but also domains where BGP VPN-IP or IP families provide inter-subnet forwarding, there is a need to specify the interworking aspects between BGP domains of type EVPN, VPN-IP and IP, so that the end to end tenant connectivity can be accomplished. This document specifies how EVPN interworks with VPN-IPv4/VPN-IPv6 and IPv4/IPv6 BGP families for inter-subnet forwarding. The document also addresses the interconnect of EVPN domains for Inter-Subnet Forwarding routes. In addition, this specification defines a new BGP Path Attribute called D-PATH (Domain PATH) that protects gateways against control plane loops. D-PATH modifies the BGP best path selection for multiprotocol BGP routes of SAFI 128 and EVPN IP Prefix routes, and therefore this document updates the BGP best path selection specification, but only for IPVPN and EVPN families.
Authors
Jorge Rabadan
Ali Sajassi
Eric C. Rosen
John Drake
Wen Lin
Jim Uttaro
Adam Simpson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)