RFC 9960: Segment Routing Point-to-Multipoint Policy
In plain English — editorial summary, not part of the RFC
The Point-to-Multipoint (P2MP) Policy enables creation of P2MP trees for efficient multipoint packet delivery in a Segment Routing (SR) domain. This document specifies the architecture, signaling, and procedures for SR P2MP Policies with Segment Routing over MPLS (SR-MPLS) and Segment Routing over IPv6 (SRv6). It defines the SR P2MP Policy construct, candidate paths (CPs) of an SR P2MP Policy, and the instantiation of the P2MP tree instances (PTIs) of a CP using Replication segments. Additionally, it describes the required extensions for a controller to support P2MP path computation and provisioning. This document updates RFC 9524.
Document record
- Document ID
- RFC9960
- Published
- April 2026
- Authors
- R. Parekh; D. Voyer; C. Filsfils; H. Bidgoli; Z. Zhang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 24
- Also known as
- —
- Updates:
- RFC 9524
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9961MPLS Segment Routing Point-to-Multipoint (P2MP) Policy PingCurrent
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 9938A Framework for the Deterministic Networking (DetNet) Controller PlaneCurrent
March 2026
- RFC 9983OSPFv2 Anycast Property AdvertisementCurrent
May 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?