RFC 8751 on Hierarchical Stateful Path Computation Element (PCE)

rfc-editor@rfc-editor.org Tue, 31 March 2020 18:34 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6BB253A28AC; Tue, 31 Mar 2020 11:34:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id oG0mzcOR32gE; Tue, 31 Mar 2020 11:34:44 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 277BC3A2835; Tue, 31 Mar 2020 11:34:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 89B39F40721; Tue, 31 Mar 2020 11:34:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg3NTEgb24gSGllcmFyY2hpY2FsIFN0YXRlZnVsIFBhdGggQ29tcHV0YXRpb24gRWxlbWVudCAoUENFKQ==?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, pce@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200331183415.89B39F40721@rfc-editor.org>
Date: Tue, 31 Mar 2020 11:34:15 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/IBMT8zp04kLyT1-ymdPvahcbH8A>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Tue, 31 Mar 2020 18:34:53 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8751

        Title:      Hierarchical Stateful Path Computation Element (PCE) 
        Author:     D. Dhody,
                    Y. Lee,
                    D. Ceccarelli,
                    J. Shin,
                    D. King
        Status:     Informational
        Stream:     IETF
        Date:       March 2020
        Mailbox:    dhruv.ietf@gmail.com, 
        Pages:      21
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-stateful-hpce-15.txt

        URL:        https://www.rfc-editor.org/info/rfc8751

        DOI:        10.17487/RFC8751

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

The Hierarchical Path Computation Element (H-PCE) architecture allows
the optimum sequence of interconnected 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, but not stateless, PCEs
using the hierarchical PCE architecture.

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

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC