Extensions to the Path Computation Element Communication Protocol (PCEP) to compute service aware Label Switched Path (LSP).

Document Type Replaced Internet-Draft (individual)
Last updated 2013-08-29 (latest revision 2013-02-25)
Replaced by draft-ietf-pce-pcep-service-aware
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-pce-pcep-service-aware
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.


Dhruv Dhody (dhruv.dhody@huawei.com)
Vishwas Manral (vishwas.manral@hp.com)
Zafar Ali (zali@cisco.com)
George Swallow (swallow@cisco.com)
Kenji Kumaki (ke-kumaki@kddi.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)