Last Call: <draft-ietf-pce-rfc7150bis-01.txt> (Conveying Vendor-Specific Constraints in the Path Computation Element communication Protocol) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Wed, 10 December 2014 23:03 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C310B1AC418; Wed, 10 Dec 2014 15:03:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lv_KMXfGycKt; Wed, 10 Dec 2014 15:03:40 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D6231A1A4D; Wed, 10 Dec 2014 15:03:40 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-pce-rfc7150bis-01.txt> (Conveying Vendor-Specific Constraints in the Path Computation Element communication Protocol) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20141210230340.17575.27245.idtracker@ietfa.amsl.com>
Date: Wed, 10 Dec 2014 15:03:40 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/lEZMh0fFuomkPDJxlqxFveTebik
Cc: pce@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 23:03:42 -0000

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.