EVPN Interworking with IPVPN

Document Type Replaced Internet-Draft (individual)
Authors Jorge Rabadan  , Ali Sajassi  , Eric Rosen  , John Drake  , Wen Lin  , Jim Uttaro  , Adam Simpson 
Last updated 2019-07-22 (latest revision 2019-01-07)
Replaced by draft-ietf-bess-evpn-ipvpn-interworking
Stream (None)
Intended RFC status (None)
Expired & archived
plain text htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-bess-evpn-ipvpn-interworking
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.


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.)