RFC 9960: Segment Routing Point-to-Multipoint Policy

The Point-to-Multipoint (P2MP) Policy enables creation of P2MP trees for efficient multipoint packet delivery in a Segment Routing (SR) domain. This document…

Read RFC 9960 on the RFC Editor

Outgoing relationships (13 related RFCs)

Updates, Normative reference — RFC 9524: Segment Routing Replication for Multipoint Service Delivery
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 8402: Segment Routing Architecture
Normative reference — RFC 9256: Segment Routing Policy Architecture
Informative reference — RFC 4655: A Path Computation Element (PCE)-Based Architecture
Informative reference — RFC 8754: IPv6 Segment Routing Header (SRH)
Informative reference — RFC 5286: Basic Specification for IP Fast Reroute: Loop-Free Alternates
Informative reference — RFC 8986: Segment Routing over IPv6 (SRv6) Network Programming
Informative reference — RFC 8660: Segment Routing with the MPLS Data Plane
Informative reference — RFC 5715: A Framework for Loop-Free Convergence
Informative reference — RFC 9573: MVPN/EVPN Tunnel Aggregation with Common Labels
Informative reference — RFC 9855: Topology Independent Fast Reroute Using Segment Routing

Incoming relationships (2 related RFCs)

Normatively referenced by — RFC 9961: MPLS Segment Routing Point-to-Multipoint (P2MP) Policy Ping
Normatively referenced by — RFC 10018: Multicast and Ethernet VPN with Segment Routing Point-to-Multipoint (P2MP) and Ingress Replication