<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-bess-evpn-inter-subnet-forwarding" target="https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-inter-subnet-forwarding-15">
   <front>
      <title>Integrated Routing and Bridging in Ethernet VPN (EVPN)</title>
      <author initials="A." surname="Sajassi" fullname="Ali Sajassi">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="S." surname="Salam" fullname="Samer Salam">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="S." surname="Thoria" fullname="Samir Thoria">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="J." surname="Drake" fullname="John Drake">
         <organization>Juniper</organization>
      </author>
      <author initials="J." surname="Rabadan" fullname="Jorge Rabadan">
         <organization>Nokia</organization>
      </author>
      <date month="July" day="26" year="2021" />
      <abstract>
	 <t>Ethernet VPN (EVPN) provides an extensible and flexible multihoming VPN solution over an MPLS/IP network for intra-subnet connectivity among Tenant Systems and end devices that can be physical or virtual.  However, there are scenarios for which there is a need for a dynamic and efficient inter-subnet connectivity among these Tenant Systems and end devices while maintaining the multihoming capabilities of EVPN.  This document describes an Integrated Routing and Bridging (IRB) solution based on EVPN to address such requirements.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-bess-evpn-inter-subnet-forwarding-15" />
   
</reference>
