[Pce] Protocol Action: 'PCEP Extensions for Stateful PCE' to Proposed Standard (draft-ietf-pce-stateful-pce-21.txt)

The IESG <iesg-secretary@ietf.org> Fri, 23 June 2017 15:46 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
Cc: db3546@att.com, Julien Meuric <julien.meuric@orange.com>, rfc-editor@rfc-editor.org, pce@ietf.org, pce-chairs@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-pce@ietf.org, julien.meuric@orange.com
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <149823276123.17110.16355451795890549720.idtracker@ietfa.amsl.com>
Date: Fri, 23 Jun 2017 08:46:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/QCED1x1XElSONENbJ1aA3AWkG4A>
Subject: [Pce] Protocol Action: 'PCEP Extensions for Stateful PCE' to Proposed Standard (draft-ietf-pce-stateful-pce-21.txt)

The IESG has approved the following document:
- 'PCEP Extensions for Stateful PCE'
  (draft-ietf-pce-stateful-pce-21.txt) as Proposed Standard

This document is the product of the Path Computation Element Working
Group.

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah
Brungard.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce/





Technical Summary

  The Path Computation Element Communication Protocol (PCEP) provides
  mechanisms for Path Computation Elements (PCEs) to perform path
  computations in response to Path Computation Clients (PCCs) requests.

  Although PCEP explicitly makes no assumptions regarding the
  information available to the PCE, it also makes no provisions for PCE
  control of timing and sequence of path computations within and across
  PCEP sessions.  This document describes a set of extensions to PCEP
  to enable stateful control of MPLS-TE and GMPLS LSPs via PCEP. 

Working Group Summary

The document already has a long history. It started with squatting some codepoints,
which resulted in publishing RFC 7470, a.k.a. "RFC 7150 bis".
Some changes have been heavily argued, mainly because of some reluctance to update
existing implementations, but this version reflects a WG consensus. 

Document Quality

There are several implementations, including one open source (OpenDaylight).

Have a significant number of vendors indicated their plan to implement the specification? 

Yes, even more have plans.

Are there any reviewers that merit special mention as having done a thorough review, 
e.g., one that resulted in important changes or a conclusion that the document had no
substantive issues? 

Some updates have been triggered by a couple of operators, thanks to some
interoperability testing between several implementations.

If there was a MIB Doctor, Media Type or other expert review, 
what was its course (briefly)? In the case of a Media Type 
review, on what date was the request posted?

N/A

Personnel

   Who is the Document Shepherd for this document?  Julien Meuric
   Who is the Responsible Area Director?  Deborah Brungard

[Pce] Protocol Action: 'PCEP Extensions for State… The IESG