Re: [lamps] Small problem with draft-ietf-lamps-cmp-algorithms
Russ Housley <housley@vigilsec.com> Mon, 19 December 2022 15:52 UTC
Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3DEAC152591; Mon, 19 Dec 2022 07:52:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 EtvXAIoDtiU5; Mon, 19 Dec 2022 07:52:08 -0800 (PST)
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 6F8C4C15258E; Mon, 19 Dec 2022 07:52:08 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 2DFFF76CF2; Mon, 19 Dec 2022 10:52:05 -0500 (EST)
Received: from a860b60074bd.fios-router.home (unknown [96.241.2.243]) (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 F23F4772A1; Mon, 19 Dec 2022 10:52:04 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <GV2PR10MB62104E9991DE8DAFD2C6F0B5FEE69@GV2PR10MB6210.EURPRD10.PROD.OUTLOOK.COM>
Date: Mon, 19 Dec 2022 10:52:04 -0500
Cc: "draft-ietf-lamps-cmp-algorithms@ietf.org" <draft-ietf-lamps-cmp-algorithms@ietf.org>, "Roman D. Danyliw" <rdd@cert.org>, LAMPS <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9195F978-B53A-477C-986D-61E6728B50DF@vigilsec.com>
References: <165227060426.48824.9867675337578376233@ietfa.amsl.com> <5DEB65B2-9D13-43A8-8BC7-46688CBAAD3E@vigilsec.com> <GV2PR10MB62104E9991DE8DAFD2C6F0B5FEE69@GV2PR10MB6210.EURPRD10.PROD.OUTLOOK.COM>
To: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
X-Mailer: Apple Mail (2.3445.104.21)
X-Scanned-By: mailmunge 3.10 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/r9nAvmU3nWFjWD6SyZCT7LH8M8M>
Subject: Re: [lamps] Small problem with draft-ietf-lamps-cmp-algorithms
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Dec 2022 15:52:09 -0000
Thanks. I already put the errata in for RFC 8702. Russ > On Dec 16, 2022, at 3:27 AM, Brockhaus, Hendrik <hendrik.brockhaus@siemens.com> wrote: > > Russ > > Thank you for spotting this. I will put it in the backlog for an AUTH48 update. > > OLD > id-KmacWithSHAKE128 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2) > country(16) us(840) organization(1) gov(101) csor(3) > nistAlgorithm(4) 2 19 } > id-KmacWithSHAKE256 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2) > country(16) us(840) organization(1) gov(101) csor(3) > nistAlgorithm(4) 2 20 } > NEW > id-KMACWithSHAKE128 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2) > country(16) us(840) organization(1) gov(101) csor(3) > nistAlgorithm(4) hashAlgs(2) 19 } > id-KMACWithSHAKE256 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2) > country(16) us(840) organization(1) gov(101) csor(3) > nistAlgorithm(4) hashAlgs(2) 20 } > > Hendrik > >> Von: Russ Housley <housley@vigilsec.com> >> >> Dear authors: >> >> I just noticed that draft-ietf-lamps-cmp-algorithms uses a different spelling >> for two OIDs than the ASN.1 module in RFC 8702. >> >> The ASN.1 Module in RFC 8702 defines: >> >> id-KMACWithSHAKE128 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2) >> country(16) us(840) organization(1) >> gov(101) csor(3) nistAlgorithm(4) >> hashAlgs(2) 19 } >> >> id-KMACWithSHAKE256 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2) >> country(16) us(840) organization(1) >> gov(101) csor(3) nistAlgorithm(4) >> hashAlgs(2) 20 } >> >> However, draft-ietf-lamps-cmp-algorithms uses: >> >> id-KmacWithSHAKE128 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2) >> country(16) us(840) organization(1) gov(101) csor(3) >> nistAlgorithm(4) 2 19 } >> >> id-KmacWithSHAKE256 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2) >> country(16) us(840) organization(1) gov(101) csor(3) >> nistAlgorithm(4) 2 20 } >> >> The difference is "KMAC" vs "Kmac". >> >> The authors copied the "Kmac" form from the body of the RFC 8702, which is >> inconsistent with the ASN.1 module. >> >> I will enter an errata against RFC 8702. >> >> Russ > > _______________________________________________ > Spasm mailing list > Spasm@ietf.org > https://www.ietf.org/mailman/listinfo/spasm
- [lamps] Small problem with draft-ietf-lamps-cmp-a… Russ Housley
- Re: [lamps] Small problem with draft-ietf-lamps-c… Brockhaus, Hendrik
- Re: [lamps] Small problem with draft-ietf-lamps-c… Russ Housley