RFC 9961: MPLS Segment Routing Point-to-Multipoint (P2MP) Policy Ping
In plain English — editorial summary, not part of the RFC
Segment Routing (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 using the Network Configuration Protocol (NETCONF) / YANG or a Command Line Interface (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 an SR P2MP Policy with MPLS encapsulation to provide Operations, Administration, and Maintenance (OAM) 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.
Document record
- Document ID
- RFC9961
- Published
- April 2026
- Authors
- H. Bidgoli; Z. Ali; Z. Zhang; A. Budhiraja; D. Voyer
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9960Segment Routing Point-to-Multipoint PolicyCurrent
April 2026
- RFC 9974Operations, Administration, and Maintenance (OAM) Requirements for the Bit Index Explicit Replication (BIER) LayerCurrent
June 2026
- RFC 9978Bidirectional Forwarding Detection (BFD) StabilityCurrent
June 2026
- RFC 9983OSPFv2 Anycast Property AdvertisementCurrent
May 2026
- RFC 9938A Framework for the Deterministic Networking (DetNet) Controller PlaneCurrent
March 2026
- RFC 9985Optimizing Bidirectional Forwarding Detection (BFD) AuthenticationCurrent
June 2026
- RFC 9986Meticulous Keyed ISAAC for Bidirectional Forwarding Detection (BFD) Optimized AuthenticationCurrent
June 2026
- RFC 9933Carrying SR-Algorithm in Path Computation Element Communication Protocol (PCEP)Current
July 2026
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?