EVPN Interworking with IPVPN
draft-rabadan-sajassi-bess-evpn-ipvpn-interworking-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Jorge Rabadan , Ali Sajassi , Eric C. Rosen , John Drake , Wen Lin , Jim Uttaro , Adam Simpson | ||
| Last updated | 2018-04-28 (Latest revision 2017-10-25) | ||
| Replaced by | draft-ietf-bess-evpn-ipvpn-interworking | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
EVPN is used as a unified control plane for tenant intra and inter- subnet-forwarding. When tenant connectivity spans not only EVPN domains but also domains where IPVPN provides inter-subnet- forwarding, there is a need to specify the interworking aspects between both EVPN and IPVPN domains, so that the end to end tenant connectivity can be accomplished. This document specifies how EVPN should interwork with VPN-IPv4/VPN-IPv6 and IPv4/IPv6 BGP families for inter-subnet-forwarding.
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.)