[TLS] Re: ML-KEM IANA and draft-connolly-tls-mlkem-key-agreement codepoint and inconsistencies

Viktor Dukhovni <ietf-dane@dukhovni.org> Fri, 07 March 2025 09:47 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: tls@mail2.ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 43E9B8BE1A1 for <tls@mail2.ietf.org>; Fri, 7 Mar 2025 01:47:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 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_MED=-2.3, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=dukhovni.org
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rxrim96X9s14 for <tls@mail2.ietf.org>; Fri, 7 Mar 2025 01:47:53 -0800 (PST)
Received: from chardros.imrryr.org (chardros.imrryr.org [144.6.86.210]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 33DCC8BE19C for <tls@ietf.org>; Fri, 7 Mar 2025 01:47:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dukhovni.org; i=@dukhovni.org; q=dns/txt; s=f8320d6e; t=1741340870; h=date : from : to : subject : message-id : reply-to : references : mime-version : content-type : in-reply-to : from; bh=J5YNJt4rI4rcfzGos8Grt7o2INx8lJ6cS//W0lkHvWQ=; b=x35OeMD7dXg4H4H87qA2n/CZb+lPiT8c0rkLA08xkH18yXkwslqdWrevr0p82WVcebvIE PD2HEhQzQRV5rXtX0AFTzwYuH7Tfg6AfOpOkc+ZcjTJSXeEboB55pv/gw7Va0VDfL/E8uro uOM2Uh7HBpslJNsFGesG2o7nwK5Wo28=
Received: by chardros.imrryr.org (Postfix, from userid 1000) id 2566693558A; Fri, 07 Mar 2025 20:47:50 +1100 (AEDT)
Date: Fri, 07 Mar 2025 20:47:50 +1100
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: tls@ietf.org
Message-ID: <Z8rAxqhpy8-MWKP7@chardros.imrryr.org>
References: <ecbe460a-578e-4c2b-a58b-adecbe63abdf@cryptonext-security.com> <Z8mdhmuunvsHEhkZ@chardros.imrryr.org> <AS5PR07MB96758D66E90B56568326199089CA2@AS5PR07MB9675.eurprd07.prod.outlook.com> <CAMjbhoVhWt6bS0GeMqJDu6goQ=zNXQ_yHLXYukN6Q4O6ij7AtQ@mail.gmail.com> <Z8pv88GK2t_95t2a@chardros.imrryr.org> <GVXPR07MB9678DC0BB871F71EE2568FCA89D52@GVXPR07MB9678.eurprd07.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <GVXPR07MB9678DC0BB871F71EE2568FCA89D52@GVXPR07MB9678.eurprd07.prod.outlook.com>
Mail-Followup-To: <tls@ietf.org>
Message-ID-Hash: OICIS3OZPFPIUDQ2VPYNQONJVEXNFLNI
X-Message-ID-Hash: OICIS3OZPFPIUDQ2VPYNQONJVEXNFLNI
X-MailFrom: ietf-dane@dukhovni.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Reply-To: tls@ietf.org
Subject: [TLS] Re: ML-KEM IANA and draft-connolly-tls-mlkem-key-agreement codepoint and inconsistencies
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/KkkyAWlABrULYuhm0hCDh0OHELU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>

On Fri, Mar 07, 2025 at 08:49:37AM +0000, John Mattsson wrote:

> >Similarly, the most preferred sigalgs are ML-DSA-65, ML-DSA-87, and
> >ML-DSA-44.  Of course these don't take effect unless the server is
> >actually configured with a key+cert of that type.
> 
> How does negotiation of ML-DSA work in TLS? I thought there was no
> code points registered in the TLS SignatureScheme registry yet?

IANA has not assigned code points just yet, but we're hoping that
the assignments requested in:

    https://datatracker.ietf.org/doc/html/draft-tls-westerbaan-mldsa-00#name-iana-considerations

will be made as requested.

-- 
    Viktor.