RFC 7150
Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol, March 2014
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoleted by:
- RFC 7470
- Authors:
- F. Zhang
A. Farrel - Stream:
- IETF
- Source:
- pce (rtg)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7150
Discuss this RFC: Send questions or comments to the mailing list pce@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7150
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.