<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-l3vpn-mvpn-bidir-ingress-replication" target="https://datatracker.ietf.org/doc/html/draft-ietf-l3vpn-mvpn-bidir-ingress-replication-01">
   <front>
      <title>Simulating &quot;Partial Mesh of MP2MP P-Tunnels&quot; with Ingress Replication</title>
      <author initials="Z. J." surname="Zhang" fullname="Zhaohui (Jeffrey) Zhang">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="Y." surname="Rekhter" fullname="Yakov Rekhter">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="A." surname="Dolganow" fullname="Andrew Dolganow">
         <organization>Alcatel-Lucent</organization>
      </author>
      <date month="July" day="1" year="2014" />
      <abstract>
	 <t>   RFC 6513 described a method to support bidirectional C-flow using
   &quot;Partial Mesh of MP2MP P-Tunnels&quot;.  This document describes how
   partial mesh of MP2MP P-Tunnels can be simulated with Ingress
   Replication, instead of a real MP2MP tunnel.  This enables a Service
   Provider to use Ingress Replication to offer transparent BIDIR-PIM
   service to its VPN customers.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-l3vpn-mvpn-bidir-ingress-replication-01" />
   
</reference>
