<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-bess-mvpn-extranet" target="https://datatracker.ietf.org/doc/html/draft-ietf-bess-mvpn-extranet-04">
   <front>
      <title>Extranet Multicast in BGP/IP MPLS VPNs</title>
      <author initials="Y." surname="Rekhter" fullname="Yakov Rekhter">
         </author>
      <author initials="E. C." surname="Rosen" fullname="Eric C. Rosen">
         </author>
      <author initials="R." surname="Aggarwal" fullname="Rahul Aggarwal">
         </author>
      <author initials="Y." surname="Cai" fullname="Yiqun Cai">
         </author>
      <author initials="T." surname="Morin" fullname="Thomas Morin">
         </author>
      <date month="November" day="17" year="2015" />
      <abstract>
	 <t>   Previous RFCs specify the procedures necessary to allow IP multicast
   traffic to travel from one site to another within a BGP/MPLS IP VPN
   (Virtual Private Network).  However, it is sometimes desirable to
   allow multicast traffic whose source is in one VPN to be received by
   systems that are in another VPN.  This is known as a &quot;Multicast VPN
   (MVPN) extranet&quot;.  This document updates RFCs 6513, 6514, and 6625 by
   specifying the procedures that are necessary in order to provide MVPN
   extranet service.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-bess-mvpn-extranet-04" />
   
</reference>
