Conveying Vendor-Specific Constraints in the Path Computation Element communication Protocol
draft-farrel-pce-rfc7150bis-01
| Document | Type | Replaced Internet-Draft (candidate for pce WG) | |
|---|---|---|---|
| Last updated | 2014-07-21 | ||
| Replaced by | draft-ietf-pce-rfc7150bis | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-pce-rfc7150bis | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-farrel-pce-rfc7150bis-01.txt
Abstract
The Path Computation Element communication Protocol (PCEP) is used to convey path computation requests and responses both between Path Computation Clients (PCCs) and Path Computation Elements (PCEs) and 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. This document defines a facility to carry vendor-specific information in PCEP using a dedicated object and a new Type-Length-Variable that can be carried in any existing PCEP object. This document obsoletes RFC 7150. The only change from that document is the allocation of a different code point for the VENDOR-INFORMATION object.
Authors
Fatai Zhang
(zhangfatai@huawei.com)
Adrian Farrel
(adrian@olddog.co.uk)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)