<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-pim-p2mp-policy-ping" target="https://datatracker.ietf.org/doc/html/draft-ietf-pim-p2mp-policy-ping-01">
   <front>
      <title>P2MP Policy Ping</title>
      <author initials="H." surname="Bidgoli" fullname="Hooman Bidgoli">
         <organization>Nokia</organization>
      </author>
      <author initials="D." surname="Voyer" fullname="Daniel Voyer">
         <organization>Bell Canada</organization>
      </author>
      <author initials="R." surname="Parekh" fullname="Rishabh Parekh">
         <organization>Cisco System</organization>
      </author>
      <author initials="Z. J." surname="Zhang" fullname="Zhaohui (Jeffrey) Zhang">
         <organization>Juniper Networks</organization>
      </author>
      <date month="December" day="12" year="2021" />
      <abstract>
	 <t>   SR P2MP policies are set of policies that enable architecture for
   P2MP service delivery.  A P2MP Policy consists of candidate paths
   that connects the Root of the Tree to a set of Leaves.  The P2MP
   policy is composed of replication segments.  A replication segment is
   a forwarding instruction for a candidate path which is downloaded to
   the Root, transit nodes and the leaves.

   This document describes a simple and efficient mechanism that can be
   used to detect data plane failures in P2MP Policy Candidate Paths
   (CPs) and Path Instances (PIs).

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-pim-p2mp-policy-ping-01" />
   
</reference>
