%% You should probably cite draft-ietf-pce-pcep-service-aware instead of this I-D. @techreport{dhody-pce-pcep-service-aware-05, number = {draft-dhody-pce-pcep-service-aware-05}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-service-aware/05/}, author = {Dhruv Dhody and Vishwas Manral and Zafar Ali and George Swallow and Kenji Kumaki}, title = {{Extensions to the Path Computation Element Communication Protocol (PCEP) to compute service aware Label Switched Path (LSP).}}, pagetotal = 17, year = 2013, month = feb, day = 25, abstract = {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.}, }