Re: [Curdle] [IANA #1362871] [Errata Verified] RFC8410 (7384)

Russ Housley <housley@vigilsec.com> Fri, 12 April 2024 17:53 UTC

Return-Path: <housley@vigilsec.com>
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 DEA33C14CEFA for <curdle@ietfa.amsl.com>; Fri, 12 Apr 2024 10:53:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=vigilsec.com
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 19k9u5x1Pllw for <curdle@ietfa.amsl.com>; Fri, 12 Apr 2024 10:53:05 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (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 266C3C14F736 for <curdle@ietf.org>; Fri, 12 Apr 2024 10:51:27 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 73B2714D790; Fri, 12 Apr 2024 13:51:26 -0400 (EDT)
Received: from smtpclient.apple (pfs.iad.rg.net [198.180.150.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 47C3214D3C0; Fri, 12 Apr 2024 13:51:26 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6.1.1\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <rt-5.0.3-1696220-1712875298-543.1362871-37-0@icann.org>
Date: Fri, 12 Apr 2024 13:51:16 -0400
Cc: Simon Josefsson <simon@josefsson.org>, Deb Cooley <debcooley1@gmail.com>, curdle@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B184491-835F-4E2A-ABC3-9441940D0D4B@vigilsec.com>
References: <RT-Ticket-1362871@icann.org> <20240411195633.4C0D0CE3BD@rfcpa.amsl.com> <rt-5.0.3-1696220-1712875298-543.1362871-37-0@icann.org>
To: iana-matrix@iana.org
X-Mailer: Apple Mail (2.3731.700.6.1.1)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=content-type:mime-version:subject:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=pair-202402141609; bh=QZ5eB9nlyHa29MP7ehQ03y+6HXTW3cxUNoafbbpMqhc=; b=ZdI5nqj4LNgspV5ynUFrRmz3EGh6vqp/IQufm2u8dc8f/aOUSu/ITfljFOaRJBwR6fsZ72gHe0ylk7r4K2dNMLJ8pk63RqeKN4fF4lJGv+C+yPxOCvofMeGUYBasa+JneuldzpZgQnkdQfDDWynkmN90fXXaCHpM0AYWP6CGh09spk9jGthvPQsMj41hqPO4OL+RBw/GIHzKpb5mzBoYpUYTcY7HjHVd7PDPUcquY4seOiGb9oGaYxnFn7ah8uCJ+cAcBn3plRUUKPDAbDqRtvqEsBIkSNYeEmsJ67Y67IIeqnYQc6vQ/WySPRpAn1F8O3dixkZ0P16/CBHNn0G7fQ==
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/qzpCbrZu3bw3tmdP96pWVtGT9Kc>
Subject: Re: [Curdle] [IANA #1362871] [Errata Verified] RFC8410 (7384)
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Apr 2024 17:53:10 -0000

Sabrina:

I do not think so.  The OIDs are listed properly in the RFC.

Russ


> On Apr 11, 2024, at 6:41 PM, Sabrina Tanamal via RT <iana-matrix@iana.org> wrote:
> 
> Hi Russ, all,
> 
> Do we need to list this errata report as an additional reference for any of the RFC 8410 registrations in the SMI Security for Cryptographic Algorithms registry? 
> 
> https://www.iana.org/assignments/smi-numbers
> 
> Thanks, 
> Sabrina
> 
> On Thu Apr 11 19:56:55 2024, rfc-editor@rfc-editor.org wrote:
>> The following errata report has been verified for RFC8410,
>> "Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use
>> in the Internet X.509 Public Key Infrastructure".
>> 
>> --------------------------------------
>> You may review the report below and at:
>> https://www.rfc-editor.org/errata/eid7384
>> 
>> --------------------------------------
>> Status: Verified
>> Type: Technical
>> 
>> Reported by: Russ Housley <housley@vigilsec.com>
>> Date Reported: 2023-03-12
>> Verified by: Deb Cooley (IESG)
>> 
>> Section: 9
>> 
>> Original Text
>> -------------
>> sa-Ed25519 SIGNATURE-ALGORITHM ::= {
>>   IDENTIFIER id-Ed25519
>>    PARAMS ARE absent
>>    PUBLIC-KEYS {pk-Ed25519}
>>    SMIME-CAPS { IDENTIFIED BY id-Ed25519 }
>> }
>> 
>> pk-Ed25519 PUBLIC-KEY ::= {
>>    IDENTIFIER id-Ed25519
>>    -- KEY no ASN.1 wrapping --
>>    PARAMS ARE absent
>>    CERT-KEY-USAGE {digitalSignature, nonRepudiation,
>>                    keyCertSign, cRLSign}
>>    PRIVATE-KEY CurvePrivateKey
>> }
>> 
>> Corrected Text
>> --------------
>> sa-Ed25519 SIGNATURE-ALGORITHM ::= {
>>   IDENTIFIER id-Ed25519
>>    PARAMS ARE absent
>>    PUBLIC-KEYS {pk-Ed25519}
>>    SMIME-CAPS { IDENTIFIED BY id-Ed25519 }
>> }
>> 
>> pk-Ed25519 PUBLIC-KEY ::= {
>>    IDENTIFIER id-Ed25519
>>    -- KEY no ASN.1 wrapping --
>>    PARAMS ARE absent
>>    CERT-KEY-USAGE {digitalSignature, nonRepudiation,
>>                    keyCertSign, cRLSign}
>>    PRIVATE-KEY CurvePrivateKey
>> }
>> 
>> sa-Ed448 SIGNATURE-ALGORITHM ::= {
>>   IDENTIFIER id-Ed448
>>    PARAMS ARE absent
>>    PUBLIC-KEYS {pk-Ed448}
>>    SMIME-CAPS { IDENTIFIED BY id-Ed448 }
>> }
>> 
>> pk-Ed448 PUBLIC-KEY ::= {
>>    IDENTIFIER id-Ed448
>>    -- KEY no ASN.1 wrapping --
>>    PARAMS ARE absent
>>    CERT-KEY-USAGE {digitalSignature, nonRepudiation,
>>                    keyCertSign, cRLSign}
>>    PRIVATE-KEY CurvePrivateKey
>> }
>> 
>> Notes
>> -----
>> The definitions for sa-Ed448 and pk-Ed448 are missing from RFC 8410.
>> 
>> --------------------------------------
>> 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
>> Stream              : IETF
>> Verifying Party     : IESG
> 
> _______________________________________________
> Curdle mailing list
> Curdle@ietf.org
> https://www.ietf.org/mailman/listinfo/curdle