<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.lee-pce-transporting-te-data" target="https://datatracker.ietf.org/doc/html/draft-lee-pce-transporting-te-data-01">
   <front>
      <title>PCE in Support of Transporting Traffic Engineering Data</title>
      <author initials="Y." surname="Lee" fullname="Young Lee">
         <organization>Huawei</organization>
      </author>
      <author initials="H." surname="Zheng" fullname="Haomian Zheng">
         <organization>Huawei</organization>
      </author>
      <date month="October" day="24" year="2014" />
      <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 discusses possible alternatives and enhancements to
   the existing approach to TED creation. This document gives
   architectural alternatives for these alternatives and their
   potential impacts on network nodes, routing protocols, and PCEP.



	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-lee-pce-transporting-te-data-01" />
   
</reference>
