PCEP Best Current Practices - Message formats and extensions
draft-many-pce-pcep-bcp-02

Document Type Expired Internet-Draft (individual)
Last updated 2015-11-02 (latest revision 2015-04-27)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
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-many-pce-pcep-bcp-02.txt

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 (ramon.casellas@cttc.es)
Oscar de Dios (oscar.gonzalezdedios@telefonica.com)
Adrian Farrel (adrian@olddog.co.uk)
Cyril Margaria (cmargaria@juniper.net)
Dhruv Dhody (dhruv.dhody@huawei.com)
Xian Zhang (zhang.xian@huawei.com)

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