<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-l3vpn-mvpn-considerations" target="https://datatracker.ietf.org/doc/html/draft-ietf-l3vpn-mvpn-considerations-06">
   <front>
      <title>Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN Solution</title>
      <author initials="R." surname="Zhang" fullname="Raymond Zhang">
         <organization>Alcatel-Lucent</organization>
      </author>
      <author initials="N. N." surname="Bitar" fullname="Dr. Nabil N. Bitar">
         <organization>Verizon</organization>
      </author>
      <author initials="T." surname="Morin" fullname="Thomas Morin">
         </author>
      <author initials="B." surname="Niven-Jenkins" fullname="Ben Niven-Jenkins">
         <organization>BT</organization>
      </author>
      <author initials="N." surname="Leymann" fullname="Nicolai Leymann">
         <organization>Deutsche Telekom</organization>
      </author>
      <author initials="Y." surname="Kamite" fullname="Yuji Kamite">
         <organization>NTT Communications</organization>
      </author>
      <date month="February" day="2" year="2010" />
      <abstract>
	 <t>More that one set of mechanisms to support multicast in a layer 3 BGP/MPLS VPN has been defined. These are presented in the documents that define them as optional building blocks.

 To enable interoperability between implementations, this document defines a subset of features that is considered mandatory for a multicast BGP/MPLS VPN implementation. This will help implementers and deployers understand which L3VPN multicast requirements are best satisfied by each option. This document is not an Internet Standards Track specification; it is published for informational purposes.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-l3vpn-mvpn-considerations-06" />
   
</reference>
