<?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-06">
   <front>
      <title>The Use Cases for Path Computation Element (PCE) as a Central Controller (PCECC).</title>
      <author initials="Z." surname="Li" fullname="Zhenbin Li">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="B." surname="Khasanov" fullname="Boris Khasanov">
         <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="L." surname="Fang" fullname="Luyuan Fang">
         <organization>Expedia, Inc.</organization>
      </author>
      <author initials="C." surname="Zhou" fullname="Chao Zhou">
         <organization>HPE</organization>
      </author>
      <author initials="T." surname="Communications" fullname="Telus Communications">
         <organization>Telus Communications</organization>
      </author>
      <author initials="A." surname="Rachitskiy" fullname="Artem Rachitskiy">
         <organization>Mobile TeleSystems JLLC</organization>
      </author>
      <author initials="A." surname="Gulida" fullname="Anton Gulida">
         <organization>LLC &quot;Lifetech&quot;</organization>
      </author>
      <date month="September" day="2" year="2020" />
      <abstract>
	 <t>   The Path Computation Element (PCE) is a core component of a Software-
   Defined Networking (SDN) system.  It can compute optimal paths for
   traffic across a network and can also update the paths to reflect
   changes in the network or traffic demands.  PCE was developed to
   derive paths for MPLS Label Switched Paths (LSPs), which are supplied
   to the head end of the LSP using the Path Computation Element
   Communication Protocol (PCEP).

   SDN has a 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.

   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 required for stateful PCE usage are covered in separate
   documents.

   This is a living document to catalogue the use cases for PCECC.
   There is currently no intention to publish this work as an RFC.


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