EVPN Interworking with IPVPN
draft-ietf-bess-evpn-ipvpn-interworking-04

The information below is for an old version of the document
Document Type Expired Internet-Draft (bess WG)
Authors Jorge Rabadan  , Ali Sajassi  , Eric Rosen  , John Drake  , Wen Lin  , Jim Uttaro  , Adam Simpson 
Last updated 2021-06-22 (latest revision 2020-12-19)
Replaces draft-rabadan-sajassi-bess-evpn-ipvpn-interworking
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
plain text pdf htmlized bibtex
Stream WG state In WG Last Call
Revised I-D Needed - Issue raised by WG
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Yes
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
https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ipvpn-interworking-04.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 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.

Authors

Jorge Rabadan (jorge.rabadan@nokia.com)
Ali Sajassi (sajassi@cisco.com)
Eric Rosen (erosen52@gmail.com)
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.)