Hi Authors,

I have a question which I realize is a bit late in the process: was it 
considered to move out carrying of Router IDs in the Open Object (Section 5.4 + 
7.1.2) to be in an independent document?  I find that function would be quite 
useful independent of any specific dataplane or path setup type as a generic 
capability in PCEP.

Thanks
Andrew

From: Dhruv Dhody via Datatracker <[email protected]>
Date: Wednesday, January 7, 2026 at 2:00 PM
To: [email protected] 
<[email protected]>, [email protected] 
<[email protected]>, [email protected] <[email protected]>
Subject: WG Last Call: draft-ietf-pce-pcep-extension-pce-controller-sr-11 (Ends 
2026-01-26)


CAUTION: This is an external email. Please be very careful when clicking links 
or opening attachments. See the URL nok.it/ext for additional information.



Hi WG,

This email marks the start of the WG last call for 
draft-ietf-pce-pcep-extension-pce-controller-sr -

https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-extension-pce-controller-sr/

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.

This Working Group Last Call ends on Monday, 2026-01-26.

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-pcep-extension-pce-controller-sr/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-pce-pcep-extension-pce-controller-sr-11.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-pcep-extension-pce-controller-sr-11
_______________________________________________
Pce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to