<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-teas-pcecc-use-cases" target="https://datatracker.ietf.org/doc/html/draft-ietf-teas-pcecc-use-cases-18">
   <front>
      <title>Use Cases for a PCE as a Central Controller (PCECC)</title>
      <author initials="Z." surname="Li" fullname="Zhenbin Li">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="D." surname="Dhody" fullname="Dhruv Dhody">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="Q." surname="Zhao" fullname="Quintin Zhao">
         <organization>Etheric Networks</organization>
      </author>
      <author initials="Z." surname="Ke" fullname="Zekung Ke">
         <organization>Tencent Holdings Ltd.</organization>
      </author>
      <author initials="B." surname="Khasanov" fullname="Boris Khasanov">
         <organization>Yandex LLC</organization>
      </author>
      <date month="May" day="31" year="2024" />
      <abstract>
	 <t>   The PCE is a core component of a Software-Defined Networking (SDN)
   system.  It can be used to compute optimal paths for network traffic
   and update existing paths to reflect changes in the network or
   traffic demands.  PCE was developed to derive traffic-engineered
   paths in MPLS networks, which are supplied to the head end of the
   paths using the Path Computation Element Communication Protocol
   (PCEP).

   SDN has much broader applicability than signaled MPLS traffic-
   engineered (TE) networks, and the PCE may be used to determine paths
   in a range of use cases including static LSPs, Segment Routing (SR),
   Service Function Chaining (SFC), and most forms of a routed or
   switched network.  It is, therefore, reasonable to consider PCEP as a
   control protocol for use in these environments to allow the PCE to be
   fully enabled as a central controller.

   A PCE as a Central Controller (PCECC) can simplify the processing of
   a distributed control plane by blending it with elements of SDN
   without necessarily completely replacing it.  This document describes
   general considerations for PCECC deployment and examines its
   applicability and benefits, as well as its challenges and
   limitations, through a number of use cases.  PCEP extensions which
   are required for the PCECC use cases are covered in separate
   documents.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-teas-pcecc-use-cases-18" />
   
</reference>
