[TLS] Re: Working Group Last Call for Use of ML-DSA in TLS 1.3

Viktor Dukhovni <ietf-dane@dukhovni.org> Thu, 23 April 2026 14:30 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 EC488E1BB06F for <tls@mail2.ietf.org>; Thu, 23 Apr 2026 07:30:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776954633; bh=rDrEHdXos3EoSUV3V0Z9PmjmFHPqtA7aPmdyZeXJQQU=; h=Date:From:To:Subject:Reply-To:References:In-Reply-To; b=bDNjwC7uQNEq5o3FHqKFbRCSmv/OalpstqgfEnw3+BUPSkmIHRiOhnzoId8jg1oia NbTY8Rh5O+RudY/rbx2CSuZYu942Ew86zpdBTVb/6u+KxnCYEYwq9zzuf3SiHRdEfC LTpckE6YqwEQ11Hrvic/VP9fmejcCcF5+JEa6DWY=
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_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_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 BuAQOkOVRWXA for <tls@mail2.ietf.org>; Thu, 23 Apr 2026 07:30:28 -0700 (PDT)
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 4A692E1BAD7E for <tls@ietf.org>; Thu, 23 Apr 2026 07:26:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dukhovni.org; i=@dukhovni.org; q=dns/txt; s=f8320d6e; t=1776954375; h=date : from : to : subject : message-id : reply-to : references : mime-version : content-type : in-reply-to : content-transfer-encoding : from; bh=rDrEHdXos3EoSUV3V0Z9PmjmFHPqtA7aPmdyZeXJQQU=; b=T4UPvAwQymK62xc3SxQLs41VvxgS+/M5vpJ9nEdojbcEspgHPyMAqC9NyGPMk6jz5NTfj 38gWCN3h+NHo7ADX+pPiMiGULpoiE+xjYJg0FMC3lSQKaLSFM/cWSlJl6ka6++kMF70mSp+ 0UcV7CtpBJiKqL6mvgNAMbUkycPWKmQ=
Received: by chardros.imrryr.org (Postfix, from userid 1000) id 7DA5F937704; Fri, 24 Apr 2026 00:26:15 +1000 (AEST)
Date: Fri, 24 Apr 2026 00:26:15 +1000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: tls@ietf.org
Message-ID: <aeosB-UX6Zti3Ojw@chardros.imrryr.org>
References: <16CF0FDA-7263-461A-9F2B-D37DBEAF5DD9@sn3rd.com> <0F6EABCB-1A16-447D-8F25-2CE20A9B5A97@sn3rd.com> <F0230E5E-4DEB-4E75-9141-24E2506CA07E@sn3rd.com> <CAFN1edq6rBSdCBCa=Px66h4AWoZq5UXrqP1zayN80Wcn+FO+-g@mail.gmail.com> <MN2PR17MB4031562558B6E4D2D3FC7631CD2A2@MN2PR17MB4031.namprd17.prod.outlook.com> <87bjf9eqb7.fsf@josefsson.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <87bjf9eqb7.fsf@josefsson.org>
Mail-Followup-To: <tls@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: VZJMMYNWA5IZ7BSW4SGRP6IX37UAKD46
X-Message-ID-Hash: VZJMMYNWA5IZ7BSW4SGRP6IX37UAKD46
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: Working Group Last Call for Use of ML-DSA in TLS 1.3
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/4S-BW2QMQF7cNR_tjX1zQvCgC-M>
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 Thu, Apr 23, 2026 at 03:53:16PM +0200, Simon Josefsson wrote:

> So why do the document needs to be published through the TLS WG?
> 
> I believe it would be better to spend WG cycles on solutions based on
> careful risk assessment -- which I believe is in favor of hybrids both
> for KEM's and more strongly for signatures -- rather than spend endless
> cycles pushing vanity registrations for commercial/political reasons.

Well, because, for reasons that for me are neither commercial, nor
political, my view is that just ML-DSA is by far the more sensible
signature choice to standardise first than any of the plethora of
hybrids.

It is I think prudent to avoid disparaging the motives of those who
happen to disagree with your assessment of the pros/cons.  You are
of course free to disagree with my or anyone else's take.  I might
not agree with your judgement, but I will not question your motives.

In particular, I strongly support a preference for hybrid KEMs (but not
exclusivity wrt. standardisation), but not at all for signatures, so
the "more strongly" is not a position I share with you.

As to the endless cycles, ... my view is that those wasted cycles are
mostly a result of stubborn opposition to what are technically sound
specifications of how the algorithms (already implemented and in use)
integrate into TLS.  I support carefully crafted security considerations
that spell out the risks to be considered, but not what I see as futile
blocking tactics.

-- 
    Viktor.  đŸ‡ºđŸ‡¦ Đ¡Đ»Đ°Đ²Đ° Đ£ĐºÑ€Đ°Ñ—Đ½Ñ–!