Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol
RFC 7150, “Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol”, is a Proposed Standard document published in March 2014 by F. Zhang, A. Farrel. It has been obsoleted by RFC 7470 — refer to the newer document for the authoritative version. 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-Variable that can be carried in any existing PCEP 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 7150 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7149 Software-Defined Networking: A Perspective from within a Service Provider Environment
- RFC 7151 File Transfer Protocol HOST Command for Virtual Hosts
- RFC 7148 Prefix Delegation Support for Proxy Mobile IPv6
- RFC 7152 Requirements for Metro Ethernet Forum Ethernet-Tree Support in Layer 2 Virtual Private Network
- RFC 7147 Definitions of Managed Objects for the Internet Small Computer System Interface
- RFC 7153 IANA Registries for BGP Extended Communities
- RFC 7146 Securing Block Storage Protocols over IP: RFC 3723 Requirements Update for IPsec v3
- RFC 7154 IETF Guidelines for Conduct