EVPN Interworking with IPVPN
draft-rabadan-sajassi-bess-evpn-ipvpn-interworking-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-07-22 (latest revision 2019-01-07) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-rabadan-sajassi-bess-evpn-ipvpn-interworking-02.txt
Abstract
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 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
(jorge.rabadan@nokia.com)
Ali Sajassi
(sajassi@cisco.com)
Eric Rosen
(erosen@juniper.net)
John Drake
(jdrake@juniper.net)
Wen Lin
(wlin@juniper.net)
Jim Uttaro
(ju1738@att.com)
Adam Simpson
(adam.1.simpson@nokia.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)