Received changes through RFC Editor sync (changed abstract to '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.')

[Ballot comment]
For what it is worth, I agree with Robert Spark's Gen-ART review comment that some highlighting of the interoperability challenges of vendor-specific options might have been useful. I don't think it is a big problem in this case (and this seems to be confirmed by Adrian's reply) but some similar RFCs have talked about it. If you want to take a look at what has been done in the past, there's text in RFC 5094 Section 1 last two paragraphs, RFC 4243 Section 3 last paragraph, RFC 3588 Section 11.1.1 two last sentences, for instance. The general thrust is emphasising the local applicability of vendor information, encouraging documentation of vendor's information elements, and recommending standardisation when there's more general interest for the information in question.

IESG/Authors/WG Chairs:

IANA has reviewed draft-ietf-pce-vendor-constraints-11.  Authors should review the comments and/or questions below.  Please report any inaccuracies and respond to any questions as soon as possible.

IANA's reviewer has the following comments/questions:

IANA understands that, upon approval of this document, there are two
actions which must be completed.

First, in the PCEP Objects sub-registry of the Path Computation Element
Protocol (PCEP) Numbers registry located at:

http://www.iana.org/assignments/pcep

IANA is requested to allocate a new Object-Class Value described as
follows:

Object-Class Value    Name                              Reference
  TBD1                  VENDOR-INFORMATION              [RFC-to-be]
              Object-Type
                0: Unassigned
                1: Vendor-Specific Constraints            [RFC-to-be]
                2-255: Unassigned

Second, in the PCEP TLV Type Indicators sub-registry of the Path
Computation Element Protocol (PCEP) Numbers registry located at:

http://www.iana.org/assignments/pcep

IANA is requested to register the following new PCEP TLV:

Value: TBD2
Description: VENDOR-INFORMATION-TLV
Reference: [RFC-to-be]

IANA understands that these are the only actions required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed
until the document has been approved for publication as an RFC.
This message is only to confirm what actions will be performed.

The following Last Call announcement was sent out:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
CC: <pce@ietf.org>
Reply-To: ietf@ietf.org
Sender: <iesg-secretary@ietf.org>
Subject: Last Call: <draft-ietf-pce-vendor-constraints-11.txt> (Conveying Vendor-Specific Constraints in the Path Computation Element communication Protocol) to Proposed Standard

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-vendor-constraints-11.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 2013-12-09. 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 between Path
  Computation Clients (PCCs) and Path Computation Elements (PCEs), and
  also 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.

The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-pce-vendor-constraints/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-pce-vendor-constraints/ballot/

No IPR declarations have been submitted directly on this I-D.