<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.rosen-l3vpn-mvpn-bidir" target="https://datatracker.ietf.org/doc/html/draft-rosen-l3vpn-mvpn-bidir-03">
   <front>
      <title>MVPN: Using Bidirectional P-Tunnels</title>
      <author initials="A." surname="Boers" fullname="Arjen Boers">
         <organization>ZTE Corporation</organization>
      </author>
      <author initials="Y." surname="Cai" fullname="Yiqun Cai">
         <organization>Editor</organization>
      </author>
      <author initials="E. C." surname="Rosen" fullname="Eric C. Rosen">
         <organization>Editor</organization>
      </author>
      <author initials="I." surname="Wijnands" fullname="IJsbrand Wijnands">
         <organization>Cisco Systems</organization>
      </author>
      <date month="February" day="1" year="2011" />
      <abstract>
	 <t>The documents specifying multicast support for BGP/MPLS IP VPNs allow
customer multicast data to be transported through a service
provider&#x27;s network through a set multicast tunnels.  Such tunnels are
advertised by BGP in a BGP attribute known as the &quot;Provider Multicast
Service Interface (PMSI) Tunnel Attribute&quot;.  The base specifications
allow the PMSI Tunnel Attribute to advertise bidirectional multicast
distribution trees as &quot;PMSI Tunnels&quot;; however, those documents do not
provide all the necessary details for using those tunnels.  These
details are provided in this document.  This document also specifies
the procedures for assigning customer multicast flows to specific
bidirectional PMSI tunnels.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-rosen-l3vpn-mvpn-bidir-03" />
   
</reference>
