[jose] Re: Algorithm identifiers for ML-KEM and ML-DSA
Ilari Liusvaara <ilariliusvaara@welho.com> Tue, 20 August 2024 19:31 UTC
Return-Path: <ilariliusvaara@welho.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CEB1C14F61A for <jose@ietfa.amsl.com>; Tue, 20 Aug 2024 12:31:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 Q9Fm1h9fUveQ for <jose@ietfa.amsl.com>; Tue, 20 Aug 2024 12:31:41 -0700 (PDT)
Received: from welho-filter1.welho.com (welho-filter1b.welho.com [83.102.41.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E54A5C1D6FBA for <jose@ietf.org>; Tue, 20 Aug 2024 12:31:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by welho-filter1.welho.com (Postfix) with ESMTP id 62B261B248 for <jose@ietf.org>; Tue, 20 Aug 2024 22:31:29 +0300 (EEST)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp3.welho.com ([IPv6:::ffff:83.102.41.86]) by localhost (welho-filter1.welho.com [::ffff:83.102.41.23]) (amavisd-new, port 10024) with ESMTP id S7OVaORAUKx4 for <jose@ietf.org>; Tue, 20 Aug 2024 22:31:29 +0300 (EEST)
Received: from LK-Perkele-VII2 (78-27-96-203.bb.dnainternet.fi [78.27.96.203]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by welho-smtp3.welho.com (Postfix) with ESMTPSA id 356482309 for <jose@ietf.org>; Tue, 20 Aug 2024 22:31:28 +0300 (EEST)
Date: Tue, 20 Aug 2024 22:31:28 +0300
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: jose@ietf.org
Message-ID: <ZsTvEMKx-NQpF1Aq@LK-Perkele-VII2.locald>
References: <CAMm+LwirtxesE0+4hwUOKgduoPbbqvbZ67qa-kZVSWmkW9GeEg@mail.gmail.com> <CAN8C-_KpyJAzcqiryS8qt_tdoS7z7SSJUCdjP9nX8Z2D7cm58g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <CAN8C-_KpyJAzcqiryS8qt_tdoS7z7SSJUCdjP9nX8Z2D7cm58g@mail.gmail.com>
Sender: ilariliusvaara@welho.com
Message-ID-Hash: 5VBBKB2B6FXJ2ERAMQCOQ4XQ4F3RKTYK
X-Message-ID-Hash: 5VBBKB2B6FXJ2ERAMQCOQ4XQ4F3RKTYK
X-MailFrom: ilariliusvaara@welho.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-jose.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [jose] Re: Algorithm identifiers for ML-KEM and ML-DSA
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/Vw3XRiEJGEroTTHQHzabo0cxWps>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jose>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Owner: <mailto:jose-owner@ietf.org>
List-Post: <mailto:jose@ietf.org>
List-Subscribe: <mailto:jose-join@ietf.org>
List-Unsubscribe: <mailto:jose-leave@ietf.org>
On Tue, Aug 20, 2024 at 01:48:41PM -0500, Orie Steele wrote: > > > Current ML-DSA proposal: > > https://datatracker.ietf.org/doc/html/draft-ietf-cose-dilithium-03#name-the-ml-dsa-algorithm-family As note, there is potential for some confusion in "ML-DSA Algorithm Family". JWK refers to "cryptographic algorithm family", but the meaning is rather different, being defined by kind of key used rather than any algorithmic similarity. ML-DSA belongs to much larger "cryptographic algorithm family", which includes things like SLH-DSA and FALCON. It would also include suitably defined pre-quantum algorithms. > I was hoping we might send the document to WGLC, and make some final > adjustments to test vectors, as soon as a good non -ipd version emerges > that I can use to generate examples. You mean implementation, right? And one does not need to care about performance (unless it is something ridiculous) or side channel attacks in suff like this... -Ilari
- [jose] Algorithm identifiers for ML-KEM and ML-DSA Phillip Hallam-Baker
- [jose] Re: Algorithm identifiers for ML-KEM and M… Orie Steele
- [jose] Re: Algorithm identifiers for ML-KEM and M… Orie Steele
- [jose] Re: Algorithm identifiers for ML-KEM and M… Ilari Liusvaara
- [jose] Re: Algorithm identifiers for ML-KEM and M… Ilari Liusvaara
- [jose] Re: Algorithm identifiers for ML-KEM and M… Ilari Liusvaara
- [jose] Re: Algorithm identifiers for ML-KEM and M… Phillip Hallam-Baker
- [jose] Re: Algorithm identifiers for ML-KEM and M… Orie Steele
- [jose] Re: Algorithm identifiers for ML-KEM and M… Michael Prorock