<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.dhodylee-pce-pcep-te-data-extn" target="https://datatracker.ietf.org/doc/html/draft-dhodylee-pce-pcep-te-data-extn-02">
   <front>
      <title>PCEP Extension for Transporting TE Data</title>
      <author initials="D." surname="Dhody" fullname="Dhruv Dhody">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="Y." surname="Lee" fullname="Young Lee">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="D." surname="Ceccarelli" fullname="Daniele Ceccarelli">
         <organization>Ericsson</organization>
      </author>
      <date month="March" day="4" year="2015" />
      <abstract>
	 <t>   In order to compute and provide optimal paths, Path Computation
   Elements (PCEs) require an accurate and timely Traffic Engineering
   Database (TED).  Traditionally this TED has been obtained from a link
   state routing protocol supporting traffic engineering extensions.

   This document extends the Path Computation Element Communication
   Protocol (PCEP) with TED population capability.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-dhodylee-pce-pcep-te-data-extn-02" />
   
</reference>
