<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-pce-pceps" target="https://datatracker.ietf.org/doc/html/draft-ietf-pce-pceps-18">
   <front>
      <title>PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)</title>
      <author initials="D." surname="Lopez" fullname="Diego Lopez">
         <organization>Telefonica I+D</organization>
      </author>
      <author initials="O. G." surname="de Dios" fullname="Oscar Gonzalez de Dios">
         <organization>Telefonica I+D</organization>
      </author>
      <author initials="Q." surname="Wu" fullname="Qin Wu">
         <organization>Huawei</organization>
      </author>
      <author initials="D." surname="Dhody" fullname="Dhruv Dhody">
         <organization>Huawei</organization>
      </author>
      <date month="September" day="4" year="2017" />
      <abstract>
	 <t>The Path Computation Element Communication Protocol (PCEP) defines the mechanisms for the communication between a Path Computation Client (PCC) and a Path Computation Element (PCE), or among PCEs. This document describes PCEPS -- the usage of Transport Layer Security (TLS) to provide a secure transport for PCEP. The additional security mechanisms are provided by the transport protocol supporting PCEP; therefore, they do not affect the flexibility and extensibility of PCEP.

 This document updates RFC 5440 in regards to the PCEP initialization phase procedures.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-pce-pceps-18" />
   
</reference>
