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

Michael Prorock <mprorock@mesur.io> Thu, 22 August 2024 21:37 UTC

Return-Path: <michael.prorock@mesur.io>
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 9E2EAC14F6AF for <jose@ietfa.amsl.com>; Thu, 22 Aug 2024 14:37:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mesur-io.20230601.gappssmtp.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 oNPo1XoSDSFe for <jose@ietfa.amsl.com>; Thu, 22 Aug 2024 14:37:20 -0700 (PDT)
Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (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 CA23BC15152B for <jose@ietf.org>; Thu, 22 Aug 2024 14:37:20 -0700 (PDT)
Received: by mail-ej1-x636.google.com with SMTP id a640c23a62f3a-a8677ae5a35so162467366b.0 for <jose@ietf.org>; Thu, 22 Aug 2024 14:37:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mesur-io.20230601.gappssmtp.com; s=20230601; t=1724362638; x=1724967438; 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=m0U5V5Ryruf2MAHy2LZo3FjUK6gck66z+FWVRJkMs9c=; b=jmhsTqRVyX5RT3o9SL0Q8l/ZXW3O55vx2uBS67OIh3thdtZV5MAnNQeP2Ag1QmCel9 wXRoUbEo3gZzUlYjau0xetHW4vkrby2PeX27tmsEGDdplqtnXFnmG4MNDMXL6bKPQZW+ mg28+ObTAhPSjsC49j6APOc1R+BcJczTizBe931iwxFnSsP5l4LmmwTAC0aerPan/Bd+ FbTvMujFUA8rQeyULZjihw9oQvZKGaG+2/Ea4+v7+cySj/6IKZpA56UXuVciz4OY5/PG yNEBUOlQkR4KM9dqTagzf4xVHaKVTEYq2tERFZ4LQPFYgcjiGhoHY0Ey/BJwYAQBSRlb z98w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724362638; x=1724967438; 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=m0U5V5Ryruf2MAHy2LZo3FjUK6gck66z+FWVRJkMs9c=; b=jOMaxRzis5Dp3mg8aiObN1Me06qRso0MWhK+xu5wM8rrFLR9ouCUuageF2SYCWZvcv 9iazV5kiSSAqkOxGY7GhJnf0lkp3OndGdTnRKoy9JmbSJUtwCvXzaSL6AKYxDIKm+Qc9 TDaeGEYnYwvSibgb5fhjRGMP3Pbzq3oyrnpD+DWZoXF3PiTFgzHYiTuDn93FAbz/aa8Q L9w5oG5t5/ptDIn8ZPsJYwXWIBpAeTv2I5jr5oRkjhGJzm8vUlvhToCYkGV+qMTdUuVU s9hOtCis3nD4/8JLzWvcjvXKwRLWIgH07jBIv9FiADOKlXvfXEqEfABm2LqKIXs3xWjg UDmw==
X-Forwarded-Encrypted: i=1; AJvYcCX55Cr05vxrHLMIrMD32+ia48soqaAhx7rqL7qHlYsdkcMekiEmDAMLsBueRTvtPLF6wvWP@ietf.org
X-Gm-Message-State: AOJu0YyLXdaolS//PXVMvPeMuxQEE7BYdJR/E2RSzk1uHDMhWW0glXJF 7BmW3gXkMNVGH+PrIGhcfBAKU8635pv4FpSiWA8id9kf4jATQs4vJLh+X2zaq/c/kn0RnAw84Ze d987WPPR2z22EkkCzPu1anNaPD444cjNYa7MP
X-Google-Smtp-Source: AGHT+IGHE6VH12KaylG7KpKY6IRKSNP3pBVEDH5FfjVPhoOoqk2QCeAwhxcc+YaSktD7Dkaxh45WRTrdo0p3qz2rkDQ=
X-Received: by 2002:a17:907:d848:b0:a86:9053:d93a with SMTP id a640c23a62f3a-a86a52f0ee8mr2720766b.31.1724362638329; Thu, 22 Aug 2024 14:37:18 -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> <CAN8C-_L1kfuR=2TzESa8KZ3pbRd9DGUyXJsiYZe+dB_1USix5Q@mail.gmail.com> <Zsejs0ENsSuwzVhl@LK-Perkele-VII2.locald> <CAN8C-_K7ukaXXhWiF2Z2cgXeNCBMATBMHdoE-Xrpm6DW7d5F-A@mail.gmail.com>
In-Reply-To: <CAN8C-_K7ukaXXhWiF2Z2cgXeNCBMATBMHdoE-Xrpm6DW7d5F-A@mail.gmail.com>
From: Michael Prorock <mprorock@mesur.io>
Date: Thu, 22 Aug 2024 15:37:01 -0600
Message-ID: <CAGJKSNRXdzKLwvyLO4WvDykKN1RTRd2Ej3kFnfMTwdgxv2vemA@mail.gmail.com>
To: Orie Steele <orie@transmute.industries>
Content-Type: multipart/alternative; boundary="00000000000085a3e406204c764d"
Message-ID-Hash: YUBAXUJLPAPISYGZ2QKQFYIIMCGUDLZ2
X-Message-ID-Hash: YUBAXUJLPAPISYGZ2QKQFYIIMCGUDLZ2
X-MailFrom: michael.prorock@mesur.io
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: Ilari Liusvaara <ilariliusvaara@welho.com>, Mike Prorock <mprorock@mesur.io>, jose@ietf.org, cose <cose@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/znSxUnzziGA4ridp7kHPiDYqYTg>
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>

if alg is mandatory and the group desires this direction i would not block
it.
I think personally it makes more sense for kty to indicate the family as
was the case in a few prior drafts (e.g. LWE, HASH, or similar), but I do
understand the rationale.


On Thu, Aug 22, 2024 at 3:22 PM Orie Steele <orie@transmute.industries>
wrote:

> I am cross posting to COSE WG list since we are defining ML-DSA / SLH-DSA
> keys for both JOSE and COSE in the drafts.
>
> On Thu, Aug 22, 2024 at 3:47 PM Ilari Liusvaara <ilariliusvaara@welho.com>
> wrote:
>
> <snip>
>
> > 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.
>>
>> No, I am arguing that all keys that are:
>>
>> - Subtyped using "alg"
>> - Public key is byte string.
>> - Private key is byte string.
>>
>
> So instead of:
>
> {
>   "kty": "ML-DSA",
>   "alg": "ML-DSA-44",
>   "pub": "V53SIdVF...uvw2nuCQ",
>   "priv": "V53SIdVF...cDKLbsBY"
> }
>
> This?
>
> {
>   "kty": "AKP",
>   "alg": "ML-DSA-44",
>   "pub": "V53SIdVF...uvw2nuCQ",
>   "priv": "V53SIdVF...cDKLbsBY"
> }
>
> Where "alg" is mandatory when kty = AKP?
>
> Should have the same kty regardless of if those are pre-quantum or
>> post-quantum, what cryptographic algorithm is used, etc...
>>
>> This corresponds to the first part in "ways to subtype" above.
>>
>> Earlier I proposed name "AKP" (Algorithm Key Pair) for such key type.
>>
>>
>> And really the only thing in JOSE such keys are suitable for is non-
>> prehashed signatures.
>>
>>
> I'd be fine with this.
>
> @Mike Prorock <mprorock@mesur.io> Would this work for you? Any objections
> from JOSE / COSE list readers?
>
>  <snip>
>
>
>> -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>
>