<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-bess-evpn-prefix-advertisement" target="https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-prefix-advertisement-11">
   <front>
      <title>IP Prefix Advertisement in Ethernet VPN (EVPN)</title>
      <author initials="J." surname="Rabadan" fullname="Jorge Rabadan">
         <organization>Nokia</organization>
      </author>
      <author initials="W." surname="Henderickx" fullname="Wim Henderickx">
         <organization>Nokia</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="A." surname="Sajassi" fullname="Ali Sajassi">
         <organization>Cisco</organization>
      </author>
      <date month="May" day="18" year="2018" />
      <abstract>
	 <t>The BGP MPLS-based Ethernet VPN (EVPN) (RFC 7432) mechanism provides a flexible control plane that allows intra-subnet connectivity in an MPLS and/or Network Virtualization Overlay (NVO) (RFC 7365) network.  In some networks, there is also a need for dynamic and efficient inter-subnet connectivity across Tenant Systems and end devices that can be physical or virtual and do not necessarily participate in dynamic routing protocols.  This document defines a new EVPN route type for the advertisement of IP prefixes and explains some use-case examples where this new route type is used.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-bess-evpn-prefix-advertisement-11" />
   
</reference>
