<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-pce-pcep-service-aware" target="https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-service-aware-00">
   <front>
      <title>Extensions to the Path Computation Element Communication Protocol (PCEP) to compute service aware Label Switched Path (LSP).</title>
      <author initials="D." surname="Dhody" fullname="Dhruv Dhody">
         </author>
      <author initials="V." surname="Manral" fullname="Vishwas Manral">
         </author>
      <author initials="Z." surname="Ali" fullname="Zafar Ali">
         </author>
      <author initials="G." surname="Swallow" fullname="George Swallow">
         </author>
      <author initials="K." surname="Kumaki" fullname="Kenji Kumaki">
         </author>
      <date month="March" day="26" year="2013" />
      <abstract>
	 <t>   In certain networks like financial information network (stock/
   commodity trading) and enterprises using cloud based applications,
   Latency (delay), Latency-Variation (jitter) and Packet loss is
   becoming a key requirement for path computation along with other
   constraints and metrics.  Latency, Latency-Variation and Packet Loss
   is associated with the Service Level Agreement (SLA) between
   customers and service providers.

   [MPLS-DELAY-FWK] describes MPLS architecture to allow Latency
   (delay), Latency-Variation (jitter) and Packet loss as properties.
   [OSPF-TE-EXPRESS] and [ISIS-TE-EXPRESS] describes mechanisms with
   which network performance information is distributed via OSPF and
   ISIS respectively.  This document describes the extension to PCEP to
   carry Latency, Latency-Variation and Loss as constraints for end to
   end path computation.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-pce-pcep-service-aware-00" />
   
</reference>
