[TLS] Re: Complaint to ADs and IESG regarding TLS WG chairs falsely claiming WG consensus to issue an RFC for draft-ietf-tls-mldsa

Nico Williams <nico@cryptonector.com> Wed, 27 May 2026 21:18 UTC

Return-Path: <nico@cryptonector.com>
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 BE2C7F63BEBB; Wed, 27 May 2026 14:18:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1779916705; bh=3ZsGHvoT3gvTIZ4bkPE2Dzj7aiZhtoBuS6xZw3OboAg=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=l9tVVObkbZJBFYKitgytqyEFnoh/IKhQE/9Hu2sijrWFhYXoVlUeDfnThPWG+IBLP Jec8Pg5U8Sc0fav/faH1FXp0yx9JNRgpHkUAJI3i9zDM4sNa+Wprn4D9nACC85ddeh +/VYrC/YHryLqVUFk4WuEacZIxeX4Kbn/XI//yqg=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=cryptonector.com
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 RWv9uRlIppG4; Wed, 27 May 2026 14:18:24 -0700 (PDT)
Received: from tiger.tulip.relay.mailchannels.net (tiger.tulip.relay.mailchannels.net [23.83.218.248]) (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 9AD11F63BEAE; Wed, 27 May 2026 14:18:24 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 8B370380F48; Wed, 27 May 2026 21:18:18 +0000 (UTC)
Received: from pdx1-sub0-mail-a209.dreamhost.com (trex-green-8.trex.outbound.svc.cluster.local [100.109.11.13]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 1B23138059E; Wed, 27 May 2026 21:18:18 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Spicy-Versed: 3ddc896901b6f3e3_1779916698358_310729621
X-MC-Loop-Signature: 1779916698358:2981341201
X-MC-Ingress-Time: 1779916698357
Received: from pdx1-sub0-mail-a209.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.109.11.13 (trex/7.1.5); Wed, 27 May 2026 21:18:18 +0000
Received: from ubby (unknown [24.28.102.31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a209.dreamhost.com (Postfix) with ESMTPSA id 4gQjCF1fg9zTF; Wed, 27 May 2026 14:18:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptonector.com; s=dreamhost; t=1779916697; bh=eQElM78x+gLJ1Tk9c5sg3VUI4dg0thxRo4uefjqtyXo=; h=Date:From:To:Cc:Subject:Content-Type:Content-Transfer-Encoding; b=RKZ0hc+SP1yCAo5XnJP2TqKqxtdoXA/fPwOqU4CtUJzodVC5ZV2WNbGGKFjAEczy6 GROXd0z1rwvEyEfW7UJVVx3A0khpnE3a47CjW3TNsXdHdGDrspe4G4WZRrFXdvkRT2 CTxbQs/TomoZTX4zcP+8rAIT0rztJkBmJ6BoKRei1pG0LUoOP8P/xNnr87PRw8W1P7 Gy8GQK0kYorDHfRsh2Uj6kvE82ahVgZqYx7+bZEKJgq2tzLUROkXIWPSKtCXUNSOYN zQPtHBlG/xpDqHzqOqYzOOEmDLMmWGx/kD2cno7IY9dNJg2PE86ulHmRu2uo/yZRmF wivgnQkBv1Hqw==
Date: Wed, 27 May 2026 16:18:14 -0500
From: Nico Williams <nico@cryptonector.com>
To: Watson Ladd <watsonbladd@gmail.com>
Message-ID: <ahdflj/Xy8VoOfH5@ubby>
References: <20260519112813.1254795.qmail@cr.yp.to> <CAGgd1Ocy8f4HeQy-qWauAJAxizznXdXA53kWVp_FV1QUVGuxWw@mail.gmail.com> <5DFBF81F-4A98-4C5E-A060-580DC6960021@symbolic.software> <87v7c8lgt8.fsf@josefsson.org> <CACsn0cmaOdG4vCdeOVSxAPnJtPRH8rBJ3sfAY3o0f1fm-ouceg@mail.gmail.com> <ahddRzOIvQDXcvaG@ubby> <CACsn0cnStbBw8Szq+McPumjExnbL=3wmwESYEMWczJJZbJXRgw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CACsn0cnStbBw8Szq+McPumjExnbL=3wmwESYEMWczJJZbJXRgw@mail.gmail.com>
Message-ID-Hash: XUDMWSZE7SUTX6TAMUBJEBFQ76E7R3OS
X-Message-ID-Hash: XUDMWSZE7SUTX6TAMUBJEBFQ76E7R3OS
X-MailFrom: nico@cryptonector.com
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: Simon Josefsson <simon=40josefsson.org@dmarc.ietf.org>, Nadim Kobeissi <nadim@symbolic.software>, TLS List <tls@ietf.org>, "D. J. Bernstein" <djb@cr.yp.to>, stndrds-inacio@andrew.cmu.edu, "<iesg@ietf.org>" <iesg@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Complaint to ADs and IESG regarding TLS WG chairs falsely claiming WG 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/HOIRgcJjrEB5DAphsEfiIGPYQXA>
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 Wed, May 27, 2026 at 02:11:16PM -0700, Watson Ladd wrote:
> On Wed, May 27, 2026 at 2:08 PM Nico Williams <nico@cryptonector.com> wrote:
> >
> > On Wed, May 27, 2026 at 02:01:08PM -0700, Watson Ladd wrote:
> > > On Wed, May 27, 2026, 1:48 PM Simon Josefsson <simon=
> > > 40josefsson.org@dmarc.ietf.org> wrote:
> > > > Repeating that statement doesn't make it true.  The analog motivation
> > > > for doing PQ hybrids is Man-In-The-Middle attacks.  If your non-hybrid
> > > > PQ signature has a weakness (e.g., implementation bug), it facilitate
> > > > man-in-the-middle's.
> > > >
> > >
> > > The only way to achieve that is to have a quantum computer at the time of
> > > attack
> >
> > Not so.  Find the victim's classical public key (they'll gladly tell you
> > it), use a quantum computer to break it off-line and recover the private
> > key, then use the private key at will to impersonate the victim, then
> > its counterparties become victims too.
> 
> Correct: you have to have a quantum computer *before* mounting the attack.
> 
> Or to put another way, todays connections are not compromised by
> tomorrows computers.

Sure, but today's _credentials_ -if they are still in use 'tomorrow'-
will be.  Who wants to suddenly have to hurry up and deploy new code and
change keys all at once on PQ day?  Worse: who wants to be dependent on
their counterparties to have to do that on PQ day?

But at the same time the same pure-PQC vs. hybrid concerns arise.
Therefore if we thinkg HNDL justifies hybrid KEMs now then surely MITM
justifies hybrid signature algorithms now as well.

Nico
--