Conveying Vendor-Specific Constraints in the Path Computation Element Protocol

Document Type Replaced Internet-Draft (individual)
Last updated 2011-01-10 (latest revision 2008-11-02)
Replaced by draft-ietf-pce-vendor-constraints
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-pce-vendor-constraints
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.


Adrian Farrel (
Greg Bernstein (

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