Skip to main content

Conveying Vendor-Specific Constraints in the Path Computation Element Protocol
draft-farrel-pce-vendor-constraints-02

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Adrian Farrel , Greg M. Bernstein
Last updated 2011-01-10 (Latest revision 2008-11-02)
Replaced by draft-ietf-pce-vendor-constraints
RFC stream (None)
Intended RFC status (None)
Formats
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 (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

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.

Authors

Adrian Farrel
Greg M. Bernstein

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