From rvanrheenen@amsl.com Wed Mar 13 10:55:55 2024 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE258C14F60F for ; Wed, 13 Mar 2024 10:55:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.907 X-Spam-Level: X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 UE1EJxQxBLdl for ; Wed, 13 Mar 2024 10:55:51 -0700 (PDT) Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (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 71C02C14F61D for ; Wed, 13 Mar 2024 10:55:51 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 4370F4250001; Wed, 13 Mar 2024 10:55:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cXjFjfpOuB0E; Wed, 13 Mar 2024 10:55:51 -0700 (PDT) Received: from [IPv6:2601:641:300:5fb0:444f:c8d:42b:e1bd] (unknown [IPv6:2601:641:300:5fb0:444f:c8d:42b:e1bd]) by c8a.amsl.com (Postfix) with ESMTPSA id F2807424FFEF; Wed, 13 Mar 2024 10:55:50 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) From: Rebecca VanRheenen In-Reply-To: <20240312213452.9A8EBE82C3@rfcpa.amsl.com> Date: Wed, 13 Mar 2024 10:55:49 -0700 Cc: corey.bonnell@digicert.com, simon@josefsson.org, ietf@augustcellars.com, curdle@ietf.org, RFC Editor Content-Transfer-Encoding: quoted-printable Message-Id: <056F14A9-552C-41E5-B29B-DC796A4E961E@amsl.com> References: <20240312213452.9A8EBE82C3@rfcpa.amsl.com> To: Roman Danyliw , Paul Wouters , Deb Cooley X-Mailer: Apple Mail (2.3608.120.23.2.7) Archived-At: Subject: Re: [Curdle] [Editorial Errata Reported] RFC8410 (7848) X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2024 17:55:55 -0000 Hi Roman, Paul, and Deb, We are unable to verify this erratum that the submitter marked as = editorial, so we changed the Type to =E2=80=9CTechnical=E2=80=9D. As = Stream Approver, please review and set the Status and Type accordingly = (see the definitions at https://www.rfc-editor.org/errata-definitions/). Note: The curdle WG has concluded, so we are addressing this to all = Security Area ADs. You may review the report at:=20 https://www.rfc-editor.org/errata/eid7848 Information on how to verify errata reports can be found at:=20 https://www.rfc-editor.org/how-to-verify/ Further information on errata can be found at:=20 https://www.rfc-editor.org/errata.php Thank you. RFC Editor/rv > On Mar 12, 2024, at 2:34 PM, RFC Errata System = wrote: >=20 > The following errata report has been submitted for RFC8410, > "Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in = the Internet X.509 Public Key Infrastructure". >=20 > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid7848 >=20 > -------------------------------------- > Type: Editorial > Reported by: Corey Bonnell >=20 > Section: 6 >=20 > Original Text > ------------- > Certificate ::=3D SEQUENCE { > tbsCertificate TBSCertificate, > signatureAlgorithm AlgorithmIdentifier, > signatureValue BIT STRING } >=20 > ... >=20 >=20 > For the Certificate structure, the signature value is > wrapped in the "signatureValue" BIT STRING field. >=20 > Corrected Text > -------------- > Certificate ::=3D SEQUENCE { > tbsCertificate TBSCertificate, > signatureAlgorithm AlgorithmIdentifier, > signature BIT STRING } >=20 > ... >=20 > For the Certificate structure, the signature value is > wrapped in the "signature" BIT STRING field. >=20 > Notes > ----- > There is no field with the name "signatureValue" in the Certificate = SEQUENCE. It is instead named "signature" according to the ASN.1 module = in RFC 5280 A.1 as well as the ASN.1 module in section 14 of RFC 5912. >=20 > Instructions: > ------------- > This erratum is currently posted as "Reported". (If it is spam, it=20 > 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 =20 > will log in to change the status and edit the report, if necessary. >=20 > -------------------------------------- > RFC8410 (draft-ietf-curdle-pkix-10) > -------------------------------------- > Title : Algorithm Identifiers for Ed25519, Ed448, = X25519, and X448 for Use in the Internet X.509 Public Key Infrastructure > Publication Date : August 2018 > Author(s) : S. Josefsson, J. Schaad > Category : PROPOSED STANDARD > Source : CURves, Deprecating and a Little more Encryption > Area : Security > Stream : IETF > Verifying Party : IESG >=20