IETF Logo Mail Archive

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

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Tue, 28 April 2026 23:35 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 42F86E5398DC for <tls@mail2.ietf.org>; Tue, 28 Apr 2026 16:35:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777419324; bh=Mr26HN9IUO3Si0lRgkvtu0rOaOTrmAiWPibYVIoUUpA=; h=Date:Subject:To:References:CC:From:In-Reply-To; b=dGCfZxW8TvbiCTj5sEJpMYMbqfAz7+368n3IxP2AjZQACC6xJz50d+XKkqXYDnwMm UfyGhdL/W0CnAp/NE1Mtv21Rtn+TQZUjmcEiGswXht+hG2Kdy5xqjcxATP5TdM41s6 oNVT9J0HRZYWFVwMWGmbnuwbj9DnI1nxa2d1nN58=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 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_HELO_NONE=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 Nc6VstRMit5s for <tls@mail2.ietf.org>; Tue, 28 Apr 2026 16:35:23 -0700 (PDT)
Received: from mailout4.zih.tu-dresden.de (mailout4.zih.tu-dresden.de [141.30.67.75]) (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 23E6FE5394E5 for <tls@ietf.org>; Tue, 28 Apr 2026 16:32:32 -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:CC:References: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=Mr26HN9IUO3Si0lRgkvtu0rOaOTrmAiWPibYVIoUUpA=; b=UBn0ivhTNfAj/7t0eZS0zunwK3 fAgOSMbdW68bJ2G8Wf3OpCPs6vIoTUHcjY1zrmPXNzoIi6n8m4LVzCF5dyULWpmPGL7SnZcb+SMRX p9Ff5DEZX87dwoKhwfG4r4Y50IfiuRjH53ksUI8JVpDUIkFxg2fa31RFfNJ9gX4lX7/ZdKMReHNI4 MAGN2FaQRh4H/sMLpFCsTnEDelaUx1a0ohHNB/s2s+3VKVlLO9lC/Cm3kuZko6njzZCnxdVQ6VZZH bAmGB34wen7mAQsdiFuXTvq0fwRuMQDSC0sHbQJe7aZfV45N7E42MUkeh/dWdtuObumKhc0xQIfGq 8EKNywzw==;
Received: from msx-t422.msx.ad.zih.tu-dresden.de ([172.26.35.139] helo=msx.tu-dresden.de) by mailout4.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 1wHruo-00BWuC-0l; Wed, 29 Apr 2026 01:32:30 +0200
Received: from [10.12.5.228] (141.76.13.165) 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, 29 Apr 2026 01:32:28 +0200
Message-ID: <90f2c421-9398-494a-8940-44fea9e991f4@tu-dresden.de>
Date: Wed, 29 Apr 2026 01:32:27 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Sean Turner <sean@sn3rd.com>
References: <16CF0FDA-7263-461A-9F2B-D37DBEAF5DD9@sn3rd.com> <038E2DBD-EE06-4091-8401-9818FB692459@sn3rd.com> <f1dce979-023f-4756-bd8a-58fe6201bf94@cs.tcd.ie>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <f1dce979-023f-4756-bd8a-58fe6201bf94@cs.tcd.ie>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms050203040807040207020302"
X-ClientProxiedBy: MSX-L416.msx.ad.zih.tu-dresden.de (172.26.34.136) To msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139)
X-TUD-Virus-Scanned: mailout4.zih.tu-dresden.de
Message-ID-Hash: GYFIOVFB7A2GFMAMXVADBD6QP3JIALK5
X-Message-ID-Hash: GYFIOVFB7A2GFMAMXVADBD6QP3JIALK5
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 List <tls@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
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/0nGff3KsUMsJCXMQo_ify6Fm7Ow>
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>

Dear Sean,

On 28.04.26 23:24, Stephen Farrell wrote:
> On 28/04/2026 21:24, Sean Turner wrote:
>> Hi! The chairs have judged that there is consensus to progress this
>> I-D.
>
> Well, that's a terse summary of a surprising conclusion. (And not
> even 'rough'?)
>
> I think it'd be good to understand the chairs' reasoning as to why
> the various objections have been sufficiently deal with.

I have read recent exchanges in the thread again, checked the repo and I 
share Stephen's concerns. It would be helpful to understand the 
rationale of how several concerns have been addressed to consensus. I am 
specially concerned because PR [0] for statement on composites has not 
even been merged, as of now.

Best regards,

-Usama


[0] https://github.com/tlswg/tls-mldsa/pull/32

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