<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-pce-pce-initiated-lsp" target="https://datatracker.ietf.org/doc/html/draft-ietf-pce-pce-initiated-lsp-11">
   <front>
      <title>Path Computation Element Communication Protocol (PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model</title>
      <author initials="E." surname="Crabbe" fullname="Edward Crabbe">
         <organization>Individual Contributor</organization>
      </author>
      <author initials="I." surname="Minei" fullname="Ina Minei">
         <organization>Google, Inc.</organization>
      </author>
      <author initials="S." surname="Sivabalan" fullname="Siva Sivabalan">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="R." surname="Varga" fullname="Robert Varga">
         <organization>Pantheon Technologies SRO</organization>
      </author>
      <date month="October" day="9" year="2017" />
      <abstract>
	 <t>The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Client (PCC) requests.

 The extensions for stateful PCE provide active control of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSPs) via PCEP, for a model where the PCC delegates control over one or more locally configured LSPs to the PCE. This document describes the creation and deletion of PCE-initiated LSPs under the stateful PCE model.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-pce-pce-initiated-lsp-11" />
   
</reference>
