Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol
RFC 7470, “Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol”, is a Proposed Standard document published in March 2015 by F. Zhang, A. Farrel. It obsoletes RFC 7150. It has since been updated by RFC 9752. The canonical text is published by the RFC Editor.
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 7470 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7469 Public Key Pinning Extension for HTTP
- RFC 7471 OSPF Traffic Engineering Metric Extensions
- RFC 7468 Textual Encodings of PKIX, PKCS, and CMS Structures
- RFC 7472 Internet Printing Protocol over HTTPS Transport Binding and the 'ipps' URI Scheme
- RFC 7467 URN Namespace for the North Atlantic Treaty Organization
- RFC 7473 Controlling State Advertisements of Non-negotiated LDP Applications
- RFC 7466 An Optimization for the Mobile Ad Hoc Network Neighborhood Discovery Protocol
- RFC 7474 Security Extension for OSPFv2 When Using Manual Key Management