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

 
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)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Replaced by draft-ietf-pce-vendor-constraints
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
//www.ietf.org/archive/id/draft-farrel-pce-vendor-constraints-02.txt

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 (adrian@olddog.co.uk)
Greg Bernstein (gregb@grotto-networking.com)

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