<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-pce-state-sync" target="https://datatracker.ietf.org/doc/html/draft-ietf-pce-state-sync-10">
   <front>
      <title>Procedures for Communication between Stateful Path Computation Elements</title>
      <author initials="H." surname="Zheng" fullname="Haomian Zheng">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="S." surname="Litkowski" fullname="Stephane Litkowski">
         <organization>Cisco</organization>
      </author>
      <author initials="S." surname="Sivabalan" fullname="Siva Sivabalan">
         <organization>Ciena Corporation</organization>
      </author>
      <author initials="C." surname="Li" fullname="Cheng Li">
         <organization>Huawei Technologies</organization>
      </author>
      <date month="November" day="29" year="2024" />
      <abstract>
	 <t>   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) 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.  There are some use
   cases, where an 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 computations loops.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-pce-state-sync-10" />
   
</reference>
