[TLS] Re: [EXT] Re: Complaint to chairs regarding false claim of consensus to issue an RFC for draft-ietf-tls-mldsa

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Wed, 06 May 2026 09:13 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 338D1E9C592B for <tls@mail2.ietf.org>; Wed, 6 May 2026 02:13:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778058816; bh=rzMPrx+cqdjs86xZGhwARNNkKhpJ72u44/czSFmP6So=; h=Date:Subject:To:CC:References:From:In-Reply-To; b=oWj5sWimVEwpds48Ivce1F2TfYAYg/+yaAhc4yTwYMK1TmO1QOcla9uZxkm5+9q38 yHqJ2w5JG4/ICLzAhtCQqUo0gLpYYavxPoyxfwBmYA2v1OkH2K8A3imGrlFa8ULHPS sTQ6hhhoEZ5kvoTHmAZZwik8Wh3AENaDN/9sYS/8=
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, HTML_MESSAGE=0.001, 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 (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 EHRfRStFGX05 for <tls@mail2.ietf.org>; Wed, 6 May 2026 02:13:31 -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 AE2ECE9C5921 for <tls@ietf.org>; Wed, 6 May 2026 02:13:31 -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=YmocV2TW6Qqy4qPa4p6tIMRoQnzBMgIs1Y0GmgvC/9U=; b=jqGTpqKMPXRDnS8NuB7c8o2lts YOlB9xJ3i/RIEKFX/CZ2+GFY7mMncJaQw60OrnY7Tp4CSwwfmDOR5lH2lKHkQGwRVSOH/c8kKwbsI ujwSvDBE6iHNn/j8hhQ2Ciod9KPa1sRiH1lqW9RK1PJjPxwik2x0lWi2QYgW/1yDjG51UYFdXYZNi thyUQHYmamdy3lBC4DnlHoExWEBGBtpEB7ioLsFLbbEEgHK3ErZWDHuUB+hr4ls0dOsHpVpU+RQ8M IpN3ql5PZa2L+3RXsKHITMDRBxJq3550RbK9/GV5rCKYauAdTbvCyn5bOr1TyVK1pLy9x3vD3NMSS eYAYkyUw==;
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 1wKYJu-00AyCc-1A; Wed, 06 May 2026 11:13:31 +0200
Received: from [10.12.5.228] (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, 6 May 2026 11:13:19 +0200
Message-ID: <466a6315-ea9c-4720-9f6d-a3de01685bb7@tu-dresden.de>
Date: Wed, 06 May 2026 11:13:18 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: "tls@ietf.org" <tls@ietf.org>
References: <3ed885ae-4fa9-4503-b413-361e519c6317@appelbaum.net> <B85CB867-80D1-4AB9-9CC7-63E63AC95656@ll.mit.edu> <CAChr6Szw7F80R-K=PNAyWSho87CwoifCp_HSacEQVsAafE1ipQ@mail.gmail.com> <BN0P110MB14192BE50024904301CF41ED903FA@BN0P110MB1419.NAMP110.PROD.OUTLOOK.COM> <CAChr6SzWMsujkpaijdv+eO8LTxeEPxATWendEtxvMSwyRXrsMQ@mail.gmail.com> <BN0P110MB14198605936EB45B9263768A903FA@BN0P110MB1419.NAMP110.PROD.OUTLOOK.COM>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <BN0P110MB14198605936EB45B9263768A903FA@BN0P110MB1419.NAMP110.PROD.OUTLOOK.COM>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms090205070506090003050901"
X-ClientProxiedBy: MSX-T416.msx.ad.zih.tu-dresden.de (172.26.35.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: YGY3P43FDBXWRZSAM5M63FXAOLOQE5LF
X-Message-ID-Hash: YGY3P43FDBXWRZSAM5M63FXAOLOQE5LF
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: [EXT] Re: Complaint to chairs regarding false claim of consensus to issue an RFC for draft-ietf-tls-mldsa
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/xPX8AL30UdI-ZjbzfoYISPDfTRo>
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 all,

Not to go into an endless loop here, but just to mention: My technical 
objection is outstanding and has not been addressed to date. The broader 
IETF consensus is captured in [0], since it is in the publication queue. 
I have a formal proof for that for TLS. Please clarify what you see 
wrong in my proof. To overturn that broader IETF consensus captured in 
[0], proponents have to come up with strong technical arguments, because 
the burden of proof here is on the proponents, not the opponents.

Neither making meta arguments (like A-B; rechartering; "milk") nor 
presenting a one-sided story (like counting of proponents) seems to be 
helpful. Please address the technical objections technically, not by 
exhausting the opponents.

Also to say that I will respond only to technical arguments, and no 
longer to these meta points. That doesn't mean my objection is addressed.

It increasingly feels to me that if we had adopted Stephen's draft [1] 
and focused even a small fraction of the energy we have spent on debates 
on ML-DSA and ML-KEM, we would have been far better.

On 06.05.26 02:58, Blumenthal, Uri - 0553 - MITLL wrote:
> Well, I’ve been participating in the IETF WGs only since  ̴1992, so 
> how would I know…

I am very naive in process things but I'm happy to know that I learnt in 
less than 34 years that "consensus" is not the same as "rough 
consensus." Chairs declared the former not the latter.

> But there’s a difference between “declaring” a consensus (which you 
> kindly attributed to me), and repeating what the Chairs already stated 
> a while ago (especially when some people keep contesting their decision).

I don't see how repetition helps, especially without adding any 
technical argument and without addressing my technical objection.

> IMHO, the only “key participant” remaining in this WG today is Eric 
> Rescorla.

To the best of my understanding, Ekr has been swinging back and forth. 
Very recently he has been in /strong opposition/ of publishing such 
drafts: see [2]. I fail to understand what changed it suddenly to 
support the publication of this draft, since it seems to be in the same 
category as pointed out in [2].

In particular, I also haven't seen him refuting my proof of security of 
hybrids.

>     >>  Considering the ratio of the “objectors” to the “supporters”,
>     the consensus seems to be there.
>
I believe ratio alone is not what determines the 'consensus.' Technical 
objections have to be addressed. Chairs, please correct me if I am wrong.


Sincerely,

-Usama


[0] 
https://www.ietf.org/archive/id/draft-ietf-lamps-pq-composite-sigs-19.html#section-9.1

[1] https://datatracker.ietf.org/doc/draft-farrell-tls-pqg/

[2] https://mailarchive.ietf.org/arch/msg/tls/vIGryOB0TU_vD81HUUxXQUNdnN0/