[Pce] I-D Action: draft-ietf-pce-state-sync-15.txt
internet-drafts@ietf.org Thu, 11 June 2026 20:28 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@mail2.ietf.org
Received: from [10.244.21.151] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 17137FF9E157; Thu, 11 Jun 2026 13:28:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1781209737; bh=Hoyix95PAUpeLSSPCUQumJBv9YLt8VetMehl/zlDByU=; h=From:To:Cc:Subject:Reply-To:Date; b=Avol4EcftOQv/BYJA+7n/WOxW/y7aMdyM94kdF6vW4uzrxzwdMITk7Ii4GAowDr93 wz2DujmQI3qAZrj2+HkT+9aowd/ZExvppzOKYj/712XVdgEZhmipEHgSFtEXslWii1 s/NrUWmnKK/4yP/8qwHP+uge0dST0siMJNuJ4cfw=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.67.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178120973701.584.12236043548079505574@dt-datatracker-f9b87776f-8pmmg>
Date: Thu, 11 Jun 2026 13:28:57 -0700
Message-ID-Hash: F7CHINDKS3U44TPERVWL5P7RAPOLOACE
X-Message-ID-Hash: F7CHINDKS3U44TPERVWL5P7RAPOLOACE
X-MailFrom: internet-drafts@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: pce@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: pce@ietf.org
Subject: [Pce] I-D Action: draft-ietf-pce-state-sync-15.txt
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/3vDQjmq2s96h-1aHCYzr_frDauc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Owner: <mailto:pce-owner@ietf.org>
List-Post: <mailto:pce@ietf.org>
List-Subscribe: <mailto:pce-join@ietf.org>
List-Unsubscribe: <mailto:pce-leave@ietf.org>
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] I-D Action: draft-ietf-pce-state-sync-15.txt internet-drafts
- [Pce] Re: I-D Action: draft-ietf-pce-state-sync-1… daniel
- [Pce] Re: I-D Action: draft-ietf-pce-state-sync-1… Andrew Stone (Nokia)