Procedures for Communication between Stateful Path Computation Elements
draft-ietf-pce-state-sync-12
| Document | Type |
Expired Internet-Draft
(pce WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Haomian Zheng , Stephane Litkowski , Siva Sivabalan , Cheng Li | ||
| Last updated | 2025-11-29 (Latest revision 2025-05-29) | ||
| Replaces | draft-litkowski-pce-state-sync | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Reviews | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Waiting for WG Chair Go-Ahead | |
| Associated WG milestone |
|
||
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 towards 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.
Authors
Haomian Zheng
Stephane Litkowski
Siva Sivabalan
Cheng Li
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)