Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 12
- 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.
- Publication Date
- 2014-03-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC7150- Link
- https://doi.org/10.17487/RFC7150
- Author(s)
- Fatai ZhangAdrian Farrel
Latest version of IETF RFC 7150
Document Versions — IETF RFC 7150
-
▶ IETF RFC 7150 (2014-03-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 5440 [Active*]
- IETF RFC 5511 [Active*]
- IETF RFC 6006 [Superseded*]
Bibliographic Reference(s)
- Koushik, A., Stephan, E., Zhao, Q., King, D., and J. Hardwick, "Path Computation Element Protocol (PCEP) Management Information Base", Work in Progress, February 2014. EXTERNAL
- IETF RFC 2578 [Active*]
- IETF RFC 4655 [Active*]
- IETF RFC 4657 [Active*]
- IETF RFC 5088 [Active*]
- IETF RFC 5089 [Active*]
- IETF RFC 5226 [Superseded*]
- IETF RFC 5541 [Active*]
- IETF RFC 5706 [Active*]
- IETF RFC 6123 [Active*]
- IETF RFC 6952 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7150.json
Superseded by:
IETF RFC 7470 [Active*]
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7150, Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol. Available at https://doi.org/10.17487/RFC7150
Snippet:
IETF RFC 7150, Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol. Available at https://doi.org/10.17487/RFC7150
HTML (ISO 690 compliant)
Preview:
IETF RFC 7150, Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol. Available at https://doi.org/10.17487/RFC7150
Snippet:
<span class="citation"><cite>IETF RFC 7150</cite>, Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol. Available at <a href="https://doi.org/10.17487/RFC7150" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7150</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7150, Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol
doi: 10.17487/RFC7150
url: https://doi.org/10.17487/RFC7150
doi: 10.17487/RFC7150
url: https://doi.org/10.17487/RFC7150
Snippet:
<li> <cite id="bib-rfc7150">IETF RFC 7150</cite>, Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol <span class="doi">10.17487/RFC7150</span> </li>
Referenced By
- IETF RFC 7470 [Active*]