[Pce] RFC 9504 on Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE Usage in GMPLS-Controlled Networks

rfc-editor@rfc-editor.org Thu, 07 December 2023 01:08 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id CB16AC09C23E; Wed, 6 Dec 2023 17:08:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id lV7EdRDwedbr; Wed, 6 Dec 2023 17:08:41 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com []) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F9A0C09036F; Wed, 6 Dec 2023 17:07:15 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 3F91919073C5; Wed, 6 Dec 2023 17:07:15 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20231207010715.3F91919073C5@rfcpa.amsl.com>
Date: Wed, 06 Dec 2023 17:07:15 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/Ia9GQI6G7U_i2KWejv1PVp9evKk>
Subject: [Pce] RFC 9504 on Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE Usage in GMPLS-Controlled Networks
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Dec 2023 01:08:45 -0000

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

        RFC 9504

        Title:      Path Computation Element Communication Protocol 
                    (PCEP) Extensions for Stateful PCE Usage 
                    in GMPLS-Controlled Networks 
        Author:     Y. Lee,
                    H. Zheng,
                    O. Gonzalez de Dios,
                    V. Lopez,
                    Z. Ali
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2023
        Mailbox:    younglee.tx@gmail.com,
        Pages:      22
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-pcep-stateful-pce-gmpls-23.txt

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

        DOI:        10.17487/RFC9504

The Path Computation Element Communication Protocol (PCEP) has been
extended to support stateful PCE functions where the stateful PCE
maintains information about paths and resource usage within a
network; however, these extensions do not cover all requirements for
GMPLS networks.

This document provides the extensions required for PCEP so as to
enable the usage of a stateful PCE capability in GMPLS-controlled

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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