[pkix] [Errata Verified] RFC5480 (8026)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 10 July 2024 17:39 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: pkix@ietf.org
Delivered-To: pkix@ietfa.amsl.com
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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27E05C14CE22; Wed, 10 Jul 2024 10:39:26 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 5DD367FA8D; Wed, 10 Jul 2024 10:39:25 -0700 (PDT)
To: loic.jonas.etienne@gmail.com, turners@ieca.com, kelviny@microsoft.com, dbrown@certicom.com, housley@vigilsec.com, wpolk@nist.gov
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240710173925.5DD367FA8D@rfcpa.rfc-editor.org>
Date: Wed, 10 Jul 2024 10:39:25 -0700
Message-ID-Hash: ZUETEAXT4H3YBOQJBOXEZOBNG4UMRFWY
X-Message-ID-Hash: ZUETEAXT4H3YBOQJBOXEZOBNG4UMRFWY
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pkix.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-ed@rfc-editor.org, iesg@ietf.org, pkix@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [pkix] [Errata Verified] RFC5480 (8026)
List-Id: PKIX Working Group <pkix.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/YjqgbHfKexjkqIxoebYGy0jz-yY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Owner: <mailto:pkix-owner@ietf.org>
List-Post: <mailto:pkix@ietf.org>
List-Subscribe: <mailto:pkix-join@ietf.org>
List-Unsubscribe: <mailto:pkix-leave@ietf.org>
The following errata report has been verified for RFC5480, "Elliptic Curve Cryptography Subject Public Key Information". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8026 -------------------------------------- Status: Verified Type: Editorial Reported by: Loïc Etienne <loic.jonas.etienne@gmail.com> Date Reported: 2024-07-10 Verified by: RFC Editor Section: 4 Original Text ------------- ---------+----------+------------+----------- 80 | 160-223 | SHA-1 | sect163k1 | | SHA-224 | secp163r2 | | SHA-256 | secp192r1 | | SHA-384 | | | SHA-512 | ---------+----------+------------+----------- Corrected Text -------------- ---------+----------+------------+----------- 80 | 160-223 | SHA-1 | sect163k1 | | SHA-224 | sect163r2 | | SHA-256 | secp192r1 | | SHA-384 | | | SHA-512 | ---------+----------+------------+----------- Notes ----- Misspelling: secp163r2 is not defined, whereas sect163r2 is. -------------------------------------- RFC5480 (draft-ietf-pkix-ecc-subpubkeyinfo-11) -------------------------------------- Title : Elliptic Curve Cryptography Subject Public Key Information Publication Date : March 2009 Author(s) : S. Turner, D. Brown, K. Yiu, R. Housley, T. Polk Category : PROPOSED STANDARD Source : Public-Key Infrastructure (X.509) Stream : IETF
- [pkix] [Errata Verified] RFC5480 (8026) RFC Errata System