Sign in
Version 5.13.0, 2015-03-25
Report a bug

Conveying Vendor-Specific Constraints in the Path Computation Element Protocol

Document type: Replaced Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2011-01-10 (latest revision 2008-11-02)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Replaced by draft-ietf-pce-vendor-constraints
Responsible AD: (None)
Send notices to: No addresses provided

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


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)