[TLS] Re: Confirming PQ+T Signatures Consensus

Ilari Liusvaara <ilariliusvaara@welho.com> Tue, 29 September 2026 16:58 UTC

Received: from smtp.dnamail.fi (sender103.dnamail.fi [83.102.40.157]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 6E20731 for <tls@ietf.org>; Tue, 29 Sep 2026 16:58:51 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=welho.com header.s=2025-03 header.b=EHCkC9bo; dmarc=pass (policy=none) header.from=welho.com; spf=pass (mx.ietf.org: domain of ilariliusvaara@welho.com designates 83.102.40.157 as permitted sender) smtp.mailfrom=ilariliusvaara@welho.com
Received: from localhost (localhost [127.0.0.1]) by smtp.dnamail.fi (Postfix) with ESMTP id D565540979C6 for <tls@ietf.org>; Tue, 29 Sep 2026 19:58:43 +0300 (EEST)
X-Virus-Scanned: X-Virus-Scanned: amavis at smtp.dnamail.fi
Received: from smtp.dnamail.fi ([83.102.40.157]) by localhost (dmail-psmtp02.s.dnaip.fi [127.0.0.1]) (amavis, port 10024) with ESMTP id rY7mzhUlTHVH for <tls@ietf.org>; Tue, 29 Sep 2026 19:58:43 +0300 (EEST)
Received: from LK-Perkele-VII2 (87-92-117-27.bb.dnainternet.fi [87.92.117.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: hliusvaa@dnamail.internal) by smtp.dnamail.fi (Postfix) with ESMTPSA id 50B174098E81 for <tls@ietf.org>; Tue, 29 Sep 2026 19:58:43 +0300 (EEST)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.dnamail.fi 50B174098E81
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=welho.com; s=2025-03; t=1790701123; bh=lOKQd+6pDwF3BJQ2pMsKWeBhQlUM0L1pRO4+w081IE0=; h=Date:From:To:Subject:References:In-Reply-To:From; b=EHCkC9bo8rmKMyC0OxtSXxXYwbqBIujCdvaR2wdNkgrabKcvA+0Nk+RWM6Rv7rxly IzMWm7KGnrkrLxLAefK61f2CHrsIZxc9tYgjUOysy00uSHzVhm6QQWoL3brSy0Zdll nepEr9pXGTeyjbrcs7d0IyQ0u6kPambulOwgGf5FuyBgnuz8P8s3I7sOqFEInty4rD s0tjw6avz/S79gDUFKeR92YgMKcXNfKjtI/rg3RUMQktmxWR+ZGR5BMk8V1ARpFnI1 wruV/HA8SMyXO0ZXOH4wNHNDGvs3/Ys7wu/oYOLWsBK7sMUkzIhyJ5xbHCfyYy69Yg 5ECJiuUxR5WOg==
Date: Tue, 29 Sep 2026 19:58:43 +0300
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: TLS List <tls@ietf.org>
Message-ID: <arvuQ5Hnh6otA14q@LK-Perkele-VII2.locald>
References: <A383CF85-CF66-4A3D-AFBC-3F2CCFEE265C@sn3rd.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <A383CF85-CF66-4A3D-AFBC-3F2CCFEE265C@sn3rd.com>
Sender: ilariliusvaara@welho.com
X-Spamd-Bar: -
Message-ID-Hash: 73WDKDWBRVAKOBTJ273ATL4HYWFPBOUG
X-Message-ID-Hash: 73WDKDWBRVAKOBTJ273ATL4HYWFPBOUG
X-MailFrom: ilariliusvaara@welho.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-tls.ietf.org-0; header-match-tls.ietf.org-1; header-match-tls.ietf.org-2; header-match-tls.ietf.org-3; header-match-tls.ietf.org-4; header-match-tls.ietf.org-5; header-match-tls.ietf.org-6; header-match-tls.ietf.org-7; header-match-tls.ietf.org-8; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [TLS] Re: Confirming PQ+T Signatures Consensus
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/BfCplzsA4FR6cO08ZNcHgHg9q60>
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 Mon, Sep 28, 2026 at 12:52:21PM -0400, Sean Turner wrote:
> 
> Please provide your answers to the following questions by 12 October 2026:
> 
> 1. Should the WG work on PQ + T Hybrid Signatures for TLS?

No. I consider the use case too niche. 


> 2. Should the WG only work on one: -pqt-dual-certs or -composite-ml-dsa?

No.


> 3. Should the WG work on: -pqt-dual-certs?

No. There seems to be no way to make this not play merry hell with TLS
library APIs. Which is bad.


> 4. Should the WG work on: -composite-ml-dsa?

No. I think this is too limited applicability, and the registration
policy is SR (with interpretation from looser end).

I think the best use case for this is IoT devices that spend a lot of
time on the shelf, and where vendor is also the CA.




-Ilari