{"draft":"draft-ietf-pim-p2mp-policy-ping-25","doc_id":"RFC9961","title":"MPLS Segment Routing Point-to-Multipoint (P2MP) Policy Ping","authors":["H. Bidgoli, Ed.","Z. Ali","Z. Zhang","A. Budhiraja","D. Voyer"],"format":["HTML","TEXT","PDF","XML"],"page_count":"9","pub_status":"PROPOSED STANDARD","status":"PROPOSED STANDARD","source":"Protocols for IP Multicast","abstract":"Segment Routing (SR) Point-to-Multipoint (P2MP) Policies are used to\r\ndefine and manage explicit P2MP paths within a network. These\r\npolicies are typically calculated via a controller-based mechanism\r\nand installed via, e.g., a Path Computation Element (PCE). In other\r\ncases, these policies can be installed using the Network\r\nConfiguration Protocol (NETCONF) \/ YANG or a Command Line Interface\r\n(CLI). They are used to steer Multicast traffic along optimized paths\r\nfrom a Root to a set of Leaf routers.\r\n\r\nThis document defines extensions to ping and traceroute mechanisms\r\nfor an SR P2MP Policy with MPLS encapsulation to provide Operations,\r\nAdministration, and Maintenance (OAM) capabilities. The extensions\r\nenable operators to verify connectivity, diagnose failures, and\r\ntroubleshoot forwarding issues within SR P2MP Policy Multicast trees.\r\n\r\nBy introducing new mechanisms for detecting failures and validating\r\npath integrity, this document enhances the operational robustness of\r\nP2MP Multicast deployments. Additionally, it ensures that existing\r\nMPLS and SR-based OAM tools can be effectively applied to networks\r\nutilizing SR P2MP Policies.","pub_date":"April 2026","keywords":["SR Multicast","SRv6 Multicast","SR Multicast ping","SR Multicast traceroute","SR Multicast OAM"],"obsoletes":[],"obsoleted_by":[],"updates":[],"updated_by":[],"see_also":[],"doi":"10.17487\/RFC9961","errata_url":null}