Last Call: <draft-ietf-pce-stateful-hpce-11.txt> (Hierarchical Stateful Path Computation Element (PCE).) to Informational RFC

The IESG <iesg-secretary@ietf.org> Wed, 14 August 2019 20:07 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D92C9120F04; Wed, 14 Aug 2019 13:07:02 -0700 (PDT)
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>
Subject: Last Call: <draft-ietf-pce-stateful-hpce-11.txt> (Hierarchical Stateful Path Computation Element (PCE).) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
CC: db3546@att.com, Adrian Farrel <adrian@olddog.co.uk>, draft-ietf-pce-stateful-hpce@ietf.org, pce@ietf.org, pce-chairs@ietf.org, adrian@olddog.co.uk
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <156581322288.2426.2480687848308427813.idtracker@ietfa.amsl.com>
Date: Wed, 14 Aug 2019 13:07:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/RMT9L5AZ5RZCSIA0ix_obdfhiVg>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2019 20:07:07 -0000

The IESG has received a request from the Path Computation Element WG (pce) to
consider the following document: - 'Hierarchical Stateful Path Computation
Element (PCE).'
  <draft-ietf-pce-stateful-hpce-11.txt> as Informational RFC

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 2019-08-28. 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


   A Stateful Path Computation Element (PCE) maintains information on
   the current network state, including: computed Label Switched Path
   (LSPs), reserved resources within the network, and pending path
   computation requests. This information may then be considered when
   computing new traffic engineered LSPs, and for associated and
   dependent LSPs, received from Path Computation Clients (PCCs). The
   Path computation response from a PCE is helpful for the PCC to
   gracefully establish the computed LSP.

   The Hierarchical Path Computation Element (H-PCE) architecture,
   provides an architecture to allow the optimum sequence of
   inter-connected domains to be selected, and network policy to be
   applied if applicable, via the use of a hierarchical relationship
   between PCEs.

   Combining the capabilities of Stateful PCE and the Hierarchical PCE
   would be advantageous. This document describes general considerations
   and use cases for the deployment of Stateful, and not Stateless, PCEs
   using the Hierarchical PCE architecture.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/ballot/


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