<?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-12">
   <front>
      <title>Secure Transport for PCEP</title>
      <author initials="D." surname="Lopez" fullname="Diego Lopez">
         </author>
      <author initials="O. G." surname="de Dios" fullname="Oscar Gonzalez de Dios">
         </author>
      <author initials="Q." surname="Wu" fullname="Qin Wu">
         </author>
      <author initials="D." surname="Dhody" fullname="Dhruv Dhody">
         </author>
      <date month="April" day="11" 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 describe the usage of Transport Layer Security (TLS) to
   enhance PCEP security, hence the PCEPS acronym proposed for it.  The
   additional security mechanisms are provided by the transport protocol
   supporting PCEP, and therefore they do not affect the flexibility and
   extensibility of PCEP.

   This document updates RFC 5440 regarding the PCEP initialization
   phase specification.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-pce-pceps-12" />
   
</reference>
