RFC 7470

Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol, March 2015

Canonical URL:
File formats:
Plain TextPDF
RFC 7150
F. Zhang
A. Farrel
pce (rtg)

Cite this RFC: TXT  |  XML

DOI:  http://dx.doi.org/10.17487/RFC7470

Discuss this RFC: Send questions or comments to pce@ietf.org

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


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-Value (TLV) that can be carried in any PCEP object that supports TLVs. This document obsoletes RFC 7150. The only changes from that document are a clarification of the use of the new Type-Length-Value and the allocation of a different code point for the VENDOR-INFORMATION object.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.

Download PDF Reader

Search RFCs
Advanced Search