PCEP Best Current Practices - Message formats and extensions
draft-many-pce-pcep-bcp-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Ramon Casellas , Oscar Gonzalez de Dios , Adrian Farrel , Cyril Margaria , Dhruv Dhody , Xian Zhang | ||
Last updated | 2015-11-02 (Latest revision 2015-04-27) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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
A core standards track RFC defines the main underlying mechanisms, basic object format and message structure of the Path Computation Element (PCE) Communications Protocol (PCEP). PCEP has been later extended in several RFCs, focusing on specific functionalities. The proliferation of such companion RFCs may cause ambiguity when implementing a PCE based solution. This document aims at documenting best current practices and at providing a reference RBNF grammar for PCEP messages, including object ordering and precedence rules.
Authors
Ramon Casellas
Oscar Gonzalez de Dios
Adrian Farrel
Cyril Margaria
Dhruv Dhody
Xian Zhang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)