Hi,

Forwarding the WGLC announcement for your information. Please use PCE
mailing list for any discussion.

Thanks!
Dhruv


Sent from Mobile

---------- Forwarded message ---------
From: Dhruv Dhody via Datatracker <[email protected]>
Date: Tue, 7 Jul 2026 at 12:11
Subject: [Pce] WG Last Call for draft-ietf-pce-sr-p2mp-policy-19 (Ends
2026-08-04)
To: <[email protected]>, <[email protected]>, <
[email protected]>, <[email protected]>


This message starts a WG Last Call for: draft-ietf-pce-sr-p2mp-policy-19

This Working Group Last Call ends on 2026-08-04 (intentionally longer to
accommodate IETF126 and travels)

Abstract:
   Segment Routing (SR) Point-to-Multipoint (P2MP) Policies are a set of
   policies that enable architecture for P2MP service delivery.  This
   document specifies extensions to the Path Computation Element
   Communication Protocol (PCEP) that allow a stateful PCE to compute
   and initiate P2MP paths for SR-MPLS from a Root to a set of Leaf
   nodes.

Please indicate your support or concern for this draft on the mailing list.
If you are opposed to the progression of the draft to RFC, please
articulate your concern. If you support it, please indicate that you have
read the latest version and that it is ready for publication in your
opinion. As always, review comments and nits are most welcome.

A general reminder to the WG to be more vocal during the last-call/adoption.

Thanks,
Dhruv & Julien

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-sr-p2mp-policy/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-pce-sr-p2mp-policy-19

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-sr-p2mp-policy-19

_______________________________________________
Pce mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
spring mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to