Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 14
- 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-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.
- Publication Date
- 2015-03-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC7470- Link
- https://doi.org/10.17487/RFC7470
- Author(s)
- Fatai ZhangAdrian Farrel
Latest version of IETF RFC 7470
Document Versions — IETF RFC 7470
-
▶ IETF RFC 7470 (2015-03-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 5440 [Active*]
- IETF RFC 5511 [Active*]
- IETF RFC 6006 [Superseded*]
Bibliographic Reference(s)
- 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*]
- IETF RFC 7150 [Superseded*]
- IETF RFC 7420 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7470.json
Supersedes:
IETF RFC 7150 [Superseded*]
Amended by:
IETF RFC 9752 [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 7470, Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol. Available at https://doi.org/10.17487/RFC7470
Snippet:
IETF RFC 7470, Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol. Available at https://doi.org/10.17487/RFC7470
HTML (ISO 690 compliant)
Preview:
IETF RFC 7470, Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol. Available at https://doi.org/10.17487/RFC7470
Snippet:
<span class="citation"><cite>IETF RFC 7470</cite>, Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol. Available at <a href="https://doi.org/10.17487/RFC7470" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7470</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7470, Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol
doi: 10.17487/RFC7470
url: https://doi.org/10.17487/RFC7470
doi: 10.17487/RFC7470
url: https://doi.org/10.17487/RFC7470
Snippet:
<li> <cite id="bib-rfc7470">IETF RFC 7470</cite>, Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol <span class="doi">10.17487/RFC7470</span> </li>
Referenced By
- IETF RFC 8800 [Active*]
- IETF RFC 9005 [Active*]
- IETF RFC 9358 [Active*]
- IETF RFC 9752 [Active*]