[Pce] [Editorial Errata Reported] RFC5440 (8344)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 24 March 2025 18:03 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@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 1993011B27FF; Mon, 24 Mar 2025 11:03:59 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id C923A21067F; Mon, 24 Mar 2025 11:03:58 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20250324180358.C923A21067F@rfcpa.rfc-editor.org>
Date: Mon, 24 Mar 2025 11:03:58 -0700
Message-ID-Hash: PMCLXBIEOZJVJMC5HS6SWYFBTX4UBZ3C
X-Message-ID-Hash: PMCLXBIEOZJVJMC5HS6SWYFBTX4UBZ3C
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: mrinmoy.ietf@gmail.com, jpv@cisco.com, jeanlouis.leroux@orange-ftgroup.com, pce@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Pce] [Editorial Errata Reported] RFC5440 (8344)
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/RMsoWJE_V7AMntQbKngISYZt2kQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Owner: <mailto:pce-owner@ietf.org>
List-Post: <mailto:pce@ietf.org>
List-Subscribe: <mailto:pce-join@ietf.org>
List-Unsubscribe: <mailto:pce-leave@ietf.org>
The following errata report has been submitted for RFC5440, "Path Computation Element (PCE) Communication Protocol (PCEP)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8344 -------------------------------------- Type: Editorial Reported by: Mrinmoy Das <mrinmoy.ietf@gmail.com> Section: 9.15 Original Text ------------- IANA created a registry for the PCEP TLVs. Value Meaning Reference 1 NO-PATH-VECTOR TLV This document 2 OVERLOAD-DURATION TLV This document 3 REQ-MISSING TLV This document Corrected Text -------------- IANA created a registry for the PCEP TLVs. Value Meaning Reference 1 NO-PATH-VECTOR TLV This document 2 OVERLOADED-DURATION TLV This document 3 REQ-MISSING TLV This document Notes ----- As per RFC 5440, name of PCEP TLV type 2 will be OVERLOADED-DURATION TLV. So, TLV name needs to be corrected at section 9.15 of RFC 5440. Also IANA registry page needs to be reflected with the same. Instructions: ------------- This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- RFC5440 (draft-ietf-pce-pcep-19) -------------------------------------- Title : Path Computation Element (PCE) Communication Protocol (PCEP) Publication Date : March 2009 Author(s) : JP. Vasseur, Ed., JL. Le Roux, Ed. Category : PROPOSED STANDARD Source : Path Computation Element Stream : IETF Verifying Party : IESG
- [Pce] [Editorial Errata Reported] RFC5440 (8344) RFC Errata System