<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-bess-evpn-ipvpn-interworking" target="https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-ipvpn-interworking-00">
   <front>
      <title>EVPN Interworking with IPVPN</title>
      <author initials="J." surname="Rabadan" fullname="Jorge Rabadan">
         <organization>Nokia</organization>
      </author>
      <author initials="A." surname="Sajassi" fullname="Ali Sajassi">
         <organization>Cisco</organization>
      </author>
      <author initials="E. C." surname="Rosen" fullname="Eric C. Rosen">
         <organization>Juniper</organization>
      </author>
      <author initials="J." surname="Drake" fullname="John Drake">
         <organization>Juniper</organization>
      </author>
      <author initials="W." surname="Lin" fullname="Wen Lin">
         <organization>Juniper</organization>
      </author>
      <author initials="J." surname="Uttaro" fullname="Jim Uttaro">
         <organization>AT&amp;T</organization>
      </author>
      <author initials="A." surname="Simpson" fullname="Adam Simpson">
         <organization>Nokia</organization>
      </author>
      <date month="March" day="6" year="2019" />
      <abstract>
	 <t>   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.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-bess-evpn-ipvpn-interworking-00" />
   
</reference>
