[Pce] Re: I-D Action: draft-ietf-pce-state-sync-15.txt

["Andrew Stone (Nokia)" <[e-mail]>]

Thanks Daniel and co authors! Latest looks good to me.

Andrew

From: Daniel King <[e-mail]> on behalf of [e-mail] <[e-mail]>
Date: Thursday, June 11, 2026 at 4:39 PM
To: 'Dhruv Dhody' <[e-mail]>; Andrew Stone (Nokia) <[e-mail]>
Cc: [e-mail] <[e-mail]>
Subject: RE: [Pce] I-D Action: draft-ietf-pce-state-sync-15.txt


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 Dhruv, Andrew,

Thanks again for taking the time to review the latest version; it's much appreciated.

This version squashes all the NITS and comments for both Topic A (Dhruv) and Topic B (Andrew).

Special mention for Section 3.5 - New text from you both (with some tweaks) handles "failure", and specifically of the highest priority PCE being detected.

We've also added a sentence spelling out what failure detection covers in this context (loss of reachability, state-sync session failure, or local policy marking the PCE as temporarily unusable), along with the PCC-side and PCE-side mechanics using the D flag.

Finally, also addressing the comment about how the PCC knows and what it actually sends.

Diff: https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-state-sync-15

Phew, I think that's it for now.

Thanks, Dan (on behalf of the authors)

-----Original Message-----
From: [e-mail] <[e-mail]>
Sent: 11 June 2026 21:29
To: [e-mail]
Cc: [e-mail]
Subject: [Pce] I-D Action: draft-ietf-pce-state-sync-15.txt

Internet-Draft draft-ietf-pce-state-sync-15.txt is now available. It is a work item of the Path Computation Element (PCE) WG of the IETF.

   Title:   Procedures for Communication between Stateful Path Computation Elements
   Authors: Haomian Zheng
            Stephane Litkowski
            Siva Sivabalan
            Cheng Li
            Daniel King
   Name:    draft-ietf-pce-state-sync-15.txt
   Pages:   40
   Dates:   2026-06-11

Abstract:

   The Path Computation Element (PCE) Communication Protocol (PCEP)
   provides mechanisms for PCEs to perform path computation in response
   to a Path Computation Client (PCC) request.  The Stateful PCE
   extensions allow stateful control of Multi-Protocol Label Switching
   (MPLS) Traffic Engineering (TE) and Generalized Multi-Protocol Label
   Switching (GMPLS) Label Switched Paths (LSPs) using PCEP.

   A Path Computation Client (PCC) can synchronize LSP state information
   to a Stateful Path Computation Element (PCE).  A PCC can have
   multiple PCEP sessions toward multiple PCEs.  In some use cases,
   inter-PCE stateful communication can bring additional resiliency in
   the design, for instance, when some PCC-PCE session fails.

   This document describes the procedures to allow stateful
   communication between PCEs for various use cases, and also the
   procedures to prevent computational loops.

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

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-pce-state-sync-15.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-state-sync-15

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
Pce mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]