The IESG has received a request from the Path Computation Element WG (pce) to consider the following document: - 'Conveying Vendor-Specific Constraints in the Path Computation Element communication Protocol' <draft-ietf-pce-rfc7150bis-01.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2014-12-24. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. 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. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-pce-rfc7150bis/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-pce-rfc7150bis/ballot/ No IPR declarations have been submitted directly on this I-D.
