IETF Logo Mail Archive

[TLS] Re: Composite ML-DSA

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Wed, 15 April 2026 14:11 UTC

Return-Path: <muhammad_usama.sardar@tu-dresden.de>
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 17499DCC9E92 for <tls@mail2.ietf.org>; Wed, 15 Apr 2026 07:11:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776262275; bh=rYrPjyygA0eW4bdwLTDvTR9viaX8n+7o9H7LyZXXZmg=; h=Date:Subject:To:CC:References:From:In-Reply-To; b=LUhZbDmUt4nAecoHSyN/BMo+eZKK+o58DkKNSGaCwq9R1zOT6IjcKNKXFU9uRkBJC 05AMNka7jh90wf2m5AOpP2Fhj00omeLumG0XftZWYq+qUlkI96pftRkuYALkkWXMCm bYRjIh3E/gIKFl3PXv1MsYqWzlGNAuifbgHcVFPs=
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_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=tu-dresden.de
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 hPu2euD86RCT for <tls@mail2.ietf.org>; Wed, 15 Apr 2026 07:11:14 -0700 (PDT)
Received: from mailout3.zih.tu-dresden.de (mailout3.zih.tu-dresden.de [141.30.67.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D9FB6DCC9D19 for <tls@ietf.org>; Wed, 15 Apr 2026 07:09:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tu-dresden.de; s=dkim2022; h=Content-Type:In-Reply-To:From:References:CC:To :Subject:MIME-Version:Date:Message-ID:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=rYrPjyygA0eW4bdwLTDvTR9viaX8n+7o9H7LyZXXZmg=; b=KlcL6Fz3qaYB6GVHuDy7xm1zv0 zpeJw06zqlruLBoPtcr5Q5UgKDKLDLbcVhth4vFaRSqmf2F6xPprLK4WquotlNn3PVFQ3pxumzJmv 4A+P5yPXX6WpHP32xW0PZTnHAqFJ/A01DqY6BoEdPfM9x0N06YM8zIL/yRB8mG/sRtCg2cJ96buN1 zZxzCX/PPGVFldYIlBsn87I4SXiNnbKCa/5qVNrVx9dB7AJX4hNvHF/9abrRPEQ/ykm4+KXXgHBGf 4yFB8kiniWzlP3Zf/il54p/wivfeY4U64Oq6mY1/oU1PzvRxsqbhtor6ZiIiImAP857YW0wHv/nqL SlP0uXXg==;
Received: from msx-t422.msx.ad.zih.tu-dresden.de ([172.26.35.139] helo=msx.tu-dresden.de) by mailout3.zih.tu-dresden.de with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <muhammad_usama.sardar@tu-dresden.de>) id 1wD0vj-00BNtL-24; Wed, 15 Apr 2026 16:09:24 +0200
Received: from [192.168.55.183] (141.76.13.149) by msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.37; Wed, 15 Apr 2026 16:09:12 +0200
Message-ID: <2dae7cd5-8c8b-424b-8197-789d1c386b03@tu-dresden.de>
Date: Wed, 15 Apr 2026 16:09:09 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Filippo Valsorda <filippo@ml.filippo.io>
References: <16CF0FDA-7263-461A-9F2B-D37DBEAF5DD9@sn3rd.com> <25c8d414-e4c8-455b-bd64-28132615ba75@cs.tcd.ie> <68f49a81-dd2c-4bea-896a-87da3e6aff68@tu-dresden.de> <CAMjbhoWwvfkfScpbf4-5PBzk__qb+6M4ZzAOba64kk9aXBba5g@mail.gmail.com> <d47a34ab-7fb9-4687-84aa-a5fa6bcf6a6c@tu-dresden.de> <2971d01a-89e3-43d3-a01d-b9c17b178763@amongbytes.com> <692bb582-ab7e-4d6b-aa75-ac5d93228bb2@tu-dresden.de> <DS4PPFA08475C7DBE27468E40C672197481C1242@DS4PPFA08475C7D.namprd11.prod.outlook.com> <LV0PR21MB6623B48B1F3A05D745F5A79D8C242@LV0PR21MB6623.namprd21.prod.outlook.com> <ad0svakv_WUM3btz@chardros.imrryr.org> <CAF8qwaBU_YHWX2MsWeeaOJ8sutR1wMozvbiTJF5kyvTE8YjWWA@mail.gmail.com> <CACsn0c=GDta824UF7uJ3nw_4U_rT=XhYOGHRemMWa+2AdbsiAg@mail.gmail.com> <3a16c7c4-345e-48ce-af70-a3bf503c8caf@app.fastmail.com> <CACf5n7_0hdeHJXXucva9pb=+pjhcgveHRpjA8XAcXB3LsYUvaw@mail.gmail.com> <CAFpG3gcC+UfO7E=ADGhwr2En5PwipZiq_r6_RdqvmT-5nnh2jw@mail.gmail.com> <d69ba150-0257-4e64-9abb-9229d03a03a6@app.fastmail.com>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <d69ba150-0257-4e64-9abb-9229d03a03a6@app.fastmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms060001060605010001080802"
X-ClientProxiedBy: MSX-L422.msx.ad.zih.tu-dresden.de (172.26.34.142) To msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139)
X-TUD-Virus-Scanned: mailout3.zih.tu-dresden.de
Message-ID-Hash: T2Z2W67MQWML56HGBZVNZO4W3K4SWLEH
X-Message-ID-Hash: T2Z2W67MQWML56HGBZVNZO4W3K4SWLEH
X-MailFrom: muhammad_usama.sardar@tu-dresden.de
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
CC: tls@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Composite ML-DSA
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/OaL5hF1N3Pg08M7bYIBLEO8Sgks>
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>

Hi Filippo,

Thank you for clarifying your concerns. I hope Simon has answered some 
of your concerns, else I am happy to look into them further. My purpose 
of writing this email, however, is different, namely the following:

On 15.04.26 14:43, Filippo Valsorda wrote:
> There's a reason the immediate chorus of "hell no" came from (most of) 
> the implementers.

In case you missed it, please note that Microsoft folks have provided an 
attestation for implementation [0].

Independent of that, that's not my read of this subthread. I don't see 
anyone other than David A to be in such strong position of "hell no." 
ISTM that David B and others (including your explicit mention of "plan" 
[1]) were just sharing their "plans," no?

> But I also don't believe in the IETF being a gatekeeper for 
> implementing/deploying things, so I have no opinions on what does and 
> doesn't become an RFC.

Do I understand correctly that despite your concerns, you are not 
opposed to adoption?

Best,

-Usama


[0] https://mailarchive.ietf.org/arch/msg/tls/eoeUL_BoClXPyro2AEe7zNwuiJo/

[1] https://mailarchive.ietf.org/arch/msg/tls/ejY1J4eu3mbwU0nfd-snznZ0Sxs/

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