Skip to main content

Conveying Vendor-Specific Constraints in the Path Computation Element Protocol
draft-ietf-pce-vendor-constraints-08

The information below is for an old version of the document.
Document Type Expired Internet-Draft (pce WG)
Authors Fatai Zhang , Adrian Farrel , Greg M. Bernstein
Last updated 2013-03-11 (Latest revision 2012-08-30)
Replaces draft-farrel-pce-vendor-constraints
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
plain text htmlized pdfized bibtex
Reviews
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
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:
https://www.ietf.org/archive/id/draft-ietf-pce-vendor-constraints-08.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

Fatai Zhang
Adrian Farrel
Greg M. Bernstein

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