%% You should probably cite draft-ietf-pim-p2mp-policy-ping-25 instead of this revision.
@techreport{ietf-pim-p2mp-policy-ping-24,
    number =    {draft-ietf-pim-p2mp-policy-ping-24},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-pim-p2mp-policy-ping/24/},
    author =    {Hooman Bidgoli and Zafar Ali and Zhaohui (Jeffrey) Zhang and Anuj Budhiraja and Daniel Voyer},
    title =     {{Segment Routing MPLS Point-to-Multipoint (P2MP) Policy Ping}},
    pagetotal = 11,
    year =      2025,
    month =     sep,
    day =       23,
    abstract =  {SR Point-to-Multipoint (P2MP) Policies are used to define and manage explicit P2MP paths within a network. These policies are typically calculated via a controller-based mechanism and installed via, e.g., a Path Computation Element (PCE). In other cases these policies can be installed via using NETCONF/YANG or CLI. They are used to steer multicast traffic along optimized paths from a Root to a set of Leaf routers. This document defines extensions to Ping and Traceroute mechanisms for SR P2MP Policy with MPLS encapsulation to provide OAM (Operations, Administration, and Maintenance) capabilities. The extensions enable operators to verify connectivity, diagnose failures and troubleshoot forwarding issues within SR P2MP Policy multicast trees. By introducing new mechanisms for detecting failures and validating path integrity, this document enhances the operational robustness of P2MP multicast deployments. Additionally, it ensures that existing MPLS and SR-based OAM tools can be effectively applied to networks utilizing SR P2MP Policies.},
}