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

daniel@olddog.co.uk Mon, 08 June 2026 10:19 UTC

Sender: Daniel King <dk@danielking.net>
From: daniel@olddog.co.uk
To: pce@ietf.org
References: <178088852952.832953.17144493683757041243@dt-datatracker-6784c69984-gl6cv>
In-Reply-To: <178088852952.832953.17144493683757041243@dt-datatracker-6784c69984-gl6cv>
Date: Mon, 08 Jun 2026 11:17:02 +0100
Message-ID: <05d901dcf72f$f3376650$d9a632f0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQJttcjBuZG230R3iEbNBVLynseLObUS81Lw
Content-Language: en-gb
Message-ID-Hash: 4KHL65A6HYH3WF5NPQJV27OZWIFF4Q4O
Precedence: list
Subject: [Pce] Re: I-D Action: draft-ietf-pce-state-sync-14.txt
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/4Jclc6WNg_jHee995-EuWGt1c5E>

Howdy PCE'rs, 

We just posted version -14 of draft-ietf-pce-state-sync:

https://datatracker.ietf.org/doc/draft-ietf-pce-state-sync/

This revision addresses OPSDIR, RTGDIR, and shepherd review comments. We will follow up with the reviewers to ensure we fully address their comments. 

You will find several updates, such as:

- Clarified the relationship with H-PCE and positioned these procedures as complementary to hierarchical deployments.

- Cleaned up the discussion on state freshness, LSP-DB version handling, and the ORIGINAL-LSP-DB-VERSION TLV length.

- Explained computation priority, switch-over behaviour, and PCUpd forwarding rules between state-sync PCEs and PCCs.

- Refined the PATH-VECTOR loop-prevention text and clarified the scope of the full-mesh requirement.

Along with editorial cleanup, squashing various NITS, English consistency and minor wording fixes.

Thanks, Dan (on behalf of the authors). 

-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
Sent: 08 June 2026 04:15
To: i-d-announce@ietf.org
Cc: pce@ietf.org
Subject: [Pce] I-D Action: draft-ietf-pce-state-sync-14.txt

Internet-Draft draft-ietf-pce-state-sync-14.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-14.txt
   Pages:   39
   Dates:   2026-06-07

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-14.html

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

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


_______________________________________________
Pce mailing list -- pce@ietf.org
To unsubscribe send an email to pce-leave@ietf.org

[Pce] I-D Action: draft-ietf-pce-state-sync-14.txt internet-drafts
[Pce] Re: I-D Action: draft-ietf-pce-state-sync-1… daniel