[Pce] RFC 9488 on Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP)
rfc-editor@rfc-editor.org Wed, 18 October 2023 18:44 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 CF382C151087; Wed, 18 Oct 2023 11:44:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.468
X-Spam-Level:
X-Spam-Status: No, score=-4.468 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 E2xJNjsbPvYE; Wed, 18 Oct 2023 11:44:19 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [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 04E8BC151061; Wed, 18 Oct 2023 11:44:19 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id D809D563EF; Wed, 18 Oct 2023 11:44:18 -0700 (PDT)
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: <20231018184418.D809D563EF@rfcpa.amsl.com>
Date: Wed, 18 Oct 2023 11:44:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/DF34Zxf0T_j8hhayBZ3Jjm5txA4>
Subject: [Pce] RFC 9488 on Local Protection Enforcement in the Path Computation Element Communication Protocol (PCEP)
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: Wed, 18 Oct 2023 18:44:19 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9488
Title: Local Protection Enforcement in the
Path Computation Element Communication Protocol (PCEP)
Author: A. Stone,
M. Aissaoui,
S. Sidor,
S. Sivabalan
Status: Standards Track
Stream: IETF
Date: October 2023
Mailbox: andrew.stone@nokia.com,
mustapha.aissaoui@nokia.com,
ssidor@cisco.com,
ssivabal@ciena.com
Pages: 9
Updates: RFC 5440
I-D Tag: draft-ietf-pce-local-protection-enforcement-11.txt
URL: https://www.rfc-editor.org/info/rfc9488
DOI: 10.17487/RFC9488
This document updates RFC 5440 to clarify usage of the Local
Protection Desired bit signaled in the Path Computation Element
Communication Protocol (PCEP). This document also introduces a new
flag for signaling protection enforcement in PCEP.
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