[Pce] RFC 9358 on Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths and Virtual Networks

rfc-editor@rfc-editor.org Tue, 14 February 2023 22:24 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57810C1782C0; Tue, 14 Feb 2023 14:24:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Level:
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kWfxoGFrLWtW; Tue, 14 Feb 2023 14:24:49 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (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 87F80C17EE11; Tue, 14 Feb 2023 14:22:55 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 756811BA3FFB; Tue, 14 Feb 2023 14:22:55 -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: <20230214222255.756811BA3FFB@rfcpa.amsl.com>
Date: Tue, 14 Feb 2023 14:22:55 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/7RfQEaePbAklvA9U1k1lV9P3mqA>
Subject: [Pce] RFC 9358 on Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths and Virtual 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: Tue, 14 Feb 2023 22:24:50 -0000

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

        
        RFC 9358

        Title:      Path Computation Element Communication Protocol 
                    (PCEP) Extensions for Establishing Relationships 
                    between Sets of Label Switched Paths and 
                    Virtual Networks 
        Author:     Y. Lee,
                    H. Zheng,
                    D. Ceccarelli
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2023
        Mailbox:    younglee.tx@gmail.com,
                    zhenghaomian@huawei.com,
                    daniele.ietf@gmail.com
        Pages:      12
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-vn-association-11.txt

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

        DOI:        10.17487/RFC9358

This document describes how to extend the Path Computation Element
Communication Protocol (PCEP) association mechanism introduced by RFC
8697 to further associate sets of Label Switched Paths (LSPs) with a
higher-level structure such as a Virtual Network (VN) requested by a
customer or application.  This extended association mechanism can be
used to facilitate control of a VN using the PCE architecture.

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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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