RFC 9756 on Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes
rfc-editor@rfc-editor.org Wed, 12 March 2025 23:05 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id E9B5BA95893; Wed, 12 Mar 2025 16:05:23 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id AD77B236A9C; Wed, 12 Mar 2025 16:05:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9756 on Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250312230523.AD77B236A9C@rfcpa.rfc-editor.org>
Date: Wed, 12 Mar 2025 16:05:23 -0700
Message-ID-Hash: 6JF65HFIOMQFTA4MXZHABSVHCNP4OEVV
X-Message-ID-Hash: 6JF65HFIOMQFTA4MXZHABSVHCNP4OEVV
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, pce@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/uBCfF8sSNwSxePRzAL7CtHZUAvE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9756
Title: Update to the IANA Path Communication Element
Protocol (PCEP) Numbers Registration Procedures
and the Allowance of Experimental Error Codes
Author: D. Dhody,
A. Farrel
Status: Standards Track
Stream: IETF
Date: March 2025
Mailbox: dhruv.ietf@gmail.com,
adrian@olddog.co.uk
Pages: 11
Updates: RFC 5440, RFC 8231, RFC 8233, RFC 8281,
RFC 8623, RFC 8664, RFC 8685, RFC 8697,
RFC 8733, RFC 8745, RFC 8779, RFC 8780,
RFC 8800, RFC 8934, RFC 9050, RFC 9059,
RFC 9168, RFC 9357, RFC 9504, RFC 9603,
RFC 9604
I-D Tag: draft-ietf-pce-iana-update-03.txt
URL: https://www.rfc-editor.org/info/rfc9756
DOI: 10.17487/RFC9756
This document updates the registration procedure within the IANA
"Path Computation Element Protocol (PCEP) Numbers" registry group.
This specification changes some of the registries with Standards
Action to IETF Review as defined in RFC 8126 and thus updates RFCs
8231, 8233, 8281, 8623, 8664, 8685, 8697, 8733, 8745, 8779, 8780,
8800, 8934, 9050, 9059, 9168, 9357, 9504, 9603, and 9604.
Designating "experimental use" sub-ranges within codepoint registries
is often beneficial for protocol experimentation in controlled
environments. Although the registries for PCEP messages, objects, and
TLV types have sub-ranges assigned for Experimental Use, the registry
for PCEP Error-Types and Error-values currently does not. This
document updates RFC 5440 by designating a specific range of PCEP
Error-Types for Experimental Use.
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