IETF Logo Mail Archive

[jose] Re: Algorithm identifiers for ML-KEM and ML-DSA

Orie Steele <orie@transmute.industries> Tue, 20 August 2024 20:02 UTC

Return-Path: <orie@transmute.industries>
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 AE9A1C14F6BC for <jose@ietfa.amsl.com>; Tue, 20 Aug 2024 13:02:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, 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=transmute.industries
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 5z3Wb_9akgfB for <jose@ietfa.amsl.com>; Tue, 20 Aug 2024 13:02:20 -0700 (PDT)
Received: from mail-ot1-x331.google.com (mail-ot1-x331.google.com [IPv6:2607:f8b0:4864:20::331]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92BA8C14CE5D for <jose@ietf.org>; Tue, 20 Aug 2024 13:02:20 -0700 (PDT)
Received: by mail-ot1-x331.google.com with SMTP id 46e09a7af769-7093abb12edso4303089a34.3 for <jose@ietf.org>; Tue, 20 Aug 2024 13:02:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=transmute.industries; s=google; t=1724184139; x=1724788939; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=mYqlFs+G6Epqjp+k02xt1v1hLsgr9ZHB8iXi39HOoaY=; b=jcdguAdlxj3Rw8pch4h5T2BloROBmJTesaqbMMj/Swep6slWEZ+RsliTGOCtQnqJTe WHy8Kh5AYgA/f5i7hY7DmkF5sgkIL0jhebDrfHQqdue3DyTVCLjMyB5KyPUgpq9bFM8l kADYIe3mLpeZJBbLou2d/btTgUgs7AzkbmJlRckePca8pVADlXMR0REjxNwJG98u7v2X majSk3qAkyMwXL7PSp5qxHc4I36uQ08cFloJnuVMtPX3HgRkeAgqeoF3WeJXbFQP4aQS 2cs9m/Z+KC/drGZRbMu5tIXiR1+nNVcEIf+5RiEGQZVi4gKTcmmrGiXCFhhfWDk1Bhsm qz4A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724184139; x=1724788939; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=mYqlFs+G6Epqjp+k02xt1v1hLsgr9ZHB8iXi39HOoaY=; b=jL/MrOJLCODUdrw665IuVs34ZzIf81oDndT52eufmxMyTeXMJtP8KgHH1hns5wrlNz RXRUAtLQ+KD9q114oIN5j7XSQWU8YTRE7NfBPxbYZ+U07b+k15kWKIhs6qz7qbPfVPzL U7zsqIA2loU/AnZOgabcYPaNw1o7vcMasMkgn0GuD4NTOmBACD34lZYkqOlivc1QpyqD I3xbrxnnBiPYUBXGXlZ3T+elZ6RVrzPuobbqas2pyUjlZQQ1EN1RIHvnsiQ/hnP1opKc 9RBpuT6oueRKSywTX/mo7nH3JfrHH2V7OfEZ/jLGsePQaf/TuGs1EqCcKnRLbOEq7fiQ PDKw==
X-Gm-Message-State: AOJu0Yy8/34KsdzVhq+B8xEY1K1cQB9q0WEGJGKXfMiJNDdUCC8fPeb4 69HxYehDxRs8WKn8mHuvQsEv740RCo0I8dm/4e0cvOaba3PkxT5MWyV7RFjHSYxLJsWOSWpB38O OG9I8fmea0oWTclZaREAb9cVY2quPY7Rbf501vg==
X-Google-Smtp-Source: AGHT+IFIoPeaIa99U3azo0kdqkMUQ3x6YEI/NBx3mL/uk5vlpW1djXzy19RlJBm+RFFK9b37OY30aeCMVU+6nqhOLpM=
X-Received: by 2002:a05:6830:418a:b0:709:4677:4236 with SMTP id 46e09a7af769-70df85f4a0amr185208a34.10.1724184139493; Tue, 20 Aug 2024 13:02:19 -0700 (PDT)
MIME-Version: 1.0
References: <CAMm+LwirtxesE0+4hwUOKgduoPbbqvbZ67qa-kZVSWmkW9GeEg@mail.gmail.com> <CAN8C-_KpyJAzcqiryS8qt_tdoS7z7SSJUCdjP9nX8Z2D7cm58g@mail.gmail.com> <ZsTvEMKx-NQpF1Aq@LK-Perkele-VII2.locald>
In-Reply-To: <ZsTvEMKx-NQpF1Aq@LK-Perkele-VII2.locald>
From: Orie Steele <orie@transmute.industries>
Date: Tue, 20 Aug 2024 15:02:07 -0500
Message-ID: <CAN8C-_L1kfuR=2TzESa8KZ3pbRd9DGUyXJsiYZe+dB_1USix5Q@mail.gmail.com>
To: Ilari Liusvaara <ilariliusvaara@welho.com>
Content-Type: multipart/alternative; boundary="000000000000298a0c062022e713"
Message-ID-Hash: KW6T6YH3464ACKSCYWD7VXEBJYL5MUTS
X-Message-ID-Hash: KW6T6YH3464ACKSCYWD7VXEBJYL5MUTS
X-MailFrom: orie@transmute.industries
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
CC: jose@ietf.org
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/bmj5jKEWPsLP7uURFzf_DJOAM38>
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 2:31 PM Ilari Liusvaara <ilariliusvaara@welho.com>
wrote:

> 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.
>
>
The use of the term is intentionally aligned:

https://datatracker.ietf.org/doc/html/rfc7517#section-4.1
https://datatracker.ietf.org/doc/html/draft-ietf-cose-dilithium-03#name-the-ml-dsa-key-type
https://datatracker.ietf.org/doc/html/draft-ietf-cose-dilithium-03#appendix-A.1.1

I think you are arguing that "kty" : "ML-DSA" should be "kty: "PQK", so
that both ML-DSA and SLH-DSA can use the same kty, just with different
algorithms.
... see:
https://datatracker.ietf.org/doc/html/draft-ietf-cose-sphincs-plus-04#appendix-A.1.1
... and then we add some "crv" like property to tell ML-DSA and SLH-DSA
apart, like we do for kty OKP and kty EC...

I am not in favor of making this change.

If any other readers of this list want this change, please let us know.


>
> > 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...
>

Yes, I meant implementation.

If you have an implementation, I am happy to add it to the implementation
report as well.

I have one that I am waiting to update.


>
>
>
>
> -Ilari
>
> _______________________________________________
> jose mailing list -- jose@ietf.org
> To unsubscribe send an email to jose-leave@ietf.org
>


-- 


ORIE STEELE
Chief Technology Officer
www.transmute.industries

<https://transmute.industries>

v2.27.8 | Report a Bug | By Email | System Status