%% You should probably cite rfc8233 instead of this I-D.
@techreport{ietf-pce-pcep-service-aware-05,
    number =    {draft-ietf-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-ietf-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 = 19,
    year =      2014,
    month =     aug,
    day =       11,
    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. IGP Traffic Engineering (TE) Metric extensions describes mechanisms with which network performance information is distributed via OSPF and IS-IS respectively. The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Clients (PCCs) requests. This document describes the extension to PCEP to carry Latency, Latency-Variation and Packet Loss as constraints for end to end path computation.},
}