<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.skr-bess-evpn-pim-proxy" target="https://datatracker.ietf.org/doc/html/draft-skr-bess-evpn-pim-proxy-00">
   <front>
      <title>PIM Proxy in EVPN Networks</title>
      <author initials="J." surname="Rabadan" fullname="Jorge Rabadan">
         <organization>Nokia</organization>
      </author>
      <author initials="J." surname="Kotalwar" fullname="Jayant Kotalwar">
         <organization>Nokia</organization>
      </author>
      <author initials="S." surname="Sathappan" fullname="Senthil Sathappan">
         <organization>Nokia</organization>
      </author>
      <author initials="Z. J." surname="Zhang" fullname="Zhaohui (Jeffrey) Zhang">
         <organization>Juniper</organization>
      </author>
      <author initials="A." surname="Sajassi" fullname="Ali Sajassi">
         <organization>Cisco</organization>
      </author>
      <date month="July" day="3" year="2017" />
      <abstract>
	 <t>   Ethernet Virtual Private Networks [RFC7432] are becoming prevalent in
   Data Centers, Data Center Interconnect (DCI) and Service Provider VPN
   applications. One of the goals that EVPN pursues is the reduction of
   flooding and the efficiency of CE-based control plane procedures in
   Broadcast Domains. Examples of this are [EVPN-PROXY-ARP-ND] for
   improving the efficiency of CE&#x27;s ARP/ND protocols, and [EVPN-IGMP-
   MLD-PROXY] for IGMP/MLD protocols. This document complements the
   latter, describing the procedures required to minimize the flooding
   of PIM messages in EVPN Broadcast Domains, and optimize the IP
   Multicast delivery between PIM routers.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-skr-bess-evpn-pim-proxy-00" />
   
</reference>
