<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.lin-bess-evpn-irb-mcast" target="https://datatracker.ietf.org/doc/html/draft-lin-bess-evpn-irb-mcast-04">
   <front>
      <title>EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding</title>
      <author initials="W." surname="Lin" fullname="Wen Lin">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="Z. J." surname="Zhang" fullname="Zhaohui (Jeffrey) Zhang">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="J." surname="Drake" fullname="John Drake">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="E. C." surname="Rosen" fullname="Eric C. Rosen">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="J." surname="Rabadan" fullname="Jorge Rabadan">
         <organization>Nokia</organization>
      </author>
      <author initials="A." surname="Sajassi" fullname="Ali Sajassi">
         <organization>Cisco Systems</organization>
      </author>
      <date month="October" day="24" year="2017" />
      <abstract>
	 <t>   Ethernet VPN (EVPN) provides a service that allows a single Local
   Area Network (LAN), i.e., a single IP subnet, to be distributed over
   multiple sites.  The sites are interconnected by an IP or MPLS
   backbone.  Intra-subnet traffic (either unicast or multicast) always
   appears to the endusers to be bridged, even when it is actually
   carried over the IP backbone.  When a single &quot;tenant&quot; owns multiple
   such LANs, EVPN also allows IP unicast traffic to be routed between
   those LANs.  This document specifies new procedures that allow inter-
   subnet IP multicast traffic to be routed among the LANs of a given
   tenant, while still making intra-subnet IP multicast traffic appear
   to be bridged.  These procedures can provide optimal routing of the
   inter-subnet multicast traffic, and do not require any such traffic
   to leave a given router and then reenter that same router.  These
   procedures also accommodate IP multicast traffic that needs to travel
   to or from systems that are outside the EVPN domain.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-lin-bess-evpn-irb-mcast-04" />
   
</reference>
