Conveying Vendor-Specific Constraints in the Path Computation Element Protocol

The information below is for an old version of the document
Document Type Expired Internet-Draft (pce WG)
Last updated 2013-03-11 (latest revision 2012-08-30)
Replaces draft-farrel-pce-vendor-constraints
Stream IETF
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Additional Resources
- Mailing list discussion
Stream WG state WG Document
Document shepherd None
IESG IESG state Expired
Consensus Boilerplate Unknown
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


The Path Computation Element Protocol (PCEP) is used to convey path computation requests and responses between Path Computation Clients (PCCs) and Path Computation Elements (PCEs), and also between cooperating PCEs. In PCEP the path computation requests carry details of the constraints and objective functions that the PCC wishes the PCE to apply in its computation. The mechanisms defined for indicating objective functions include the capability to convey vendor-specific objective functions. This document defines a facility to carry vendor-specific constraints in PCEP.


Fatai Zhang (
Adrian Farrel (
Greg Bernstein (

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