[TLS] Re: Confirming PQ+T Signatures Consensus

Ryan Appel <ryan.appel.333@gmail.com> Thu, 01 October 2026 12:04 UTC

Received: from mail-oo2-x29.google.com (mail-oo2-x29.google.com [IPv6:2607:f8b0:4864:31::29]) (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 45E2742 for <tls@ietf.org>; Thu, 01 Oct 2026 12:04:58 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=gmail.com header.s=20251104 header.b=Y0LtUGxM; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx.ietf.org: domain of ryan.appel.333@gmail.com designates 2607:f8b0:4864:31::29 as permitted sender) smtp.mailfrom=ryan.appel.333@gmail.com
Received: by mail-oo2-x29.google.com with SMTP id 46e09a7af769-7fcb425fc2bso4046712a34.3 for <tls@ietf.org>; Thu, 01 Oct 2026 05:04:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1790856291; x=1791461091; darn=ietf.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:content-type:from:to:cc:subject:date :message-id:reply-to:content-type; bh=NR+Xo9nscsCArAe+mmEIAEx52rVAUva54aDI7449p4M=; b=Y0LtUGxMq4QKqpPtpMJS6dKX3NyQCQ6dWVaNANl6ZV/Jsbu7csAAtswRXTLMpSor5/ GGjoCvVNLBvMyzbsI2/UYtlaxYIdKg07ofZaMB+MfEATo57Qlb9qWymDiREkg/A9do0R QaBMYVjYB0T3hgMofYFmFgYJ//nlzaxQuimU0VvpCDeeGEPK6gf3kZvlBcYiDTw3WxM9 a4mDuNz6YXtBX5V6dymqPQSHA5/39+Zn+hnn37+G7d/Dz822969jQJ1S5ILhDv/mwCwD 5/Uyq2edgRw8a6LkKdmqrRlO1ZltTf3p3AS0TglFaKDZL51SMFxDw7z5kjPfGheF8SXP SaZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1790856291; x=1791461091; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:content-type:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=NR+Xo9nscsCArAe+mmEIAEx52rVAUva54aDI7449p4M=; b=F87E2h4eiSinErjf4BoBrR0jTg7RBNAPHNmCFN4KcwVqhEw/a6TDKNS/SFtfuA6op4 ugS3woPXitozZjDdhkYhYKUlREukftTrShwyYjwpumRVLtMg64Wl9Dpq0LDrDhxWxoSW 6IvXlfxN5FLgrIDnGPjXPYmTvJ+BXOTb7+aDmIXy5drUlRlzxM4gDXLzcyzZje0k6QU5 GKulwcioT6p3X+KL2+/gQrnIrsTQ361V4KdeSiYII0MtV2tpbywPEYcMbyr6CBH8dJ4L 2+VwCakEQxcF0EWXQkxU7TzU3Q8uEZ4Ey6uf+O5LypPXmhnORTJFw3trUNRD63vPBxqL JJSw==
X-Gm-Message-State: AFuF++lyX5PeZyVntj7MFLRPgJ0je+F2c+LeMUeheV5RtR3qH3CXw2YU APVfRQuYYoF6rReg4WUWoV1JasOpRPN5+KQRNRXGAkIpamifG8gF1bHlT7t8yZap
X-Gm-Gg: AYBFou3aDF40vgni6TV5G/T9PAUMCeYyEOujmHmxM8gEaHRPWxuI+W/lufHjHX+mog9 QkpxvtVrucCRty7D/kETkcZNamsLpGoYzSNQhy+vKZC94vTvRvG0vVHOFkQTiDu44LZi+8DRgkA OplYfxEPH1soYdUHfQ7PSHpfcEV5UDF+1s1X20Ch4ykchEGLN6ibWIglKNigiG+vqq0Gcam7Sjk onTVDQixGVQcgn7JEX9HA2tPp/1uXimrJJivNT/pHARpx437b763eU6YFhCLozd5tHf+LYVjN8z 1Wd63ks3a07aNqv0JxKohD9J91cWYyGo7cT1/bQD2A5Pn7A9Q+5xcCy4EtZtpE7a3mFdK1LNv2l 24PXmf5xuo2mJx1DcuoCtaWYS38wxufaUMkoAk/psITiSTClzB1jm1i2mpMAgIgCreXmilRzzB3 vJDNP8cLi4t612/kORddrHJ+yrACo8fSSU8PL8d0/cC3KA7judbC7vWctJGCg4A7wZBGzvm85E6 1O8Rd9kbkhBi1gLLeQF1fwlhMCKWIJagw==
X-Received: by 2002:a9d:6c87:0:b0:822:27d6:c281 with SMTP id 46e09a7af769-82227e66750mr224570a34.8.1790856290504; Thu, 01 Oct 2026 05:04:50 -0700 (PDT)
Received: from smtpclient.apple ([2600:1702:5238:9080:cc60:2d00:f4:53dc]) by smtp.gmail.com with ESMTPSA id 46e09a7af769-8212b52c1ecsm2163296a34.25.2026.10.01.05.04.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 01 Oct 2026 05:04:49 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Ryan Appel <ryan.appel.333@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Thu, 01 Oct 2026 07:04:38 -0500
Message-Id: <8C17B3B4-5683-4852-86B9-597720EF82F1@gmail.com>
References: <21C4A5BF-AC6D-418E-9E70-C90AD0D2DE4F@klaussner.biz>
In-Reply-To: <21C4A5BF-AC6D-418E-9E70-C90AD0D2DE4F@klaussner.biz>
To: tls@ietf.org
X-Mailer: iPhone Mail (24A437)
X-Spamd-Bar: -
Message-ID-Hash: MLHOHCGMCH5YNFRZJEAMALDBZY5CAWOS
X-Message-ID-Hash: MLHOHCGMCH5YNFRZJEAMALDBZY5CAWOS
X-MailFrom: ryan.appel.333@gmail.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
CC: TLS List <tls@ietf.org>
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/E3LHVeT1NYhy3N_xwcQd4abAClc>
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>

1. Should the WG work on PQ + T Hybrid Signatures for TLS?

Yes

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

Yes

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

No

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

Yes. And as a question, has anyone considered serializing the composite, rather than parallelizing it? 

IF ML-DSA gives SUF-CMA over anything that it signs, wouldn’t it be plausible to sign something with ECDSA:

Sig_E = ECDSA(key, message)

And then combine that with the message to produce the signature for ML_DSA?

Message_2 = message || Sig_E

Sig_M = ML-DSA(key, Message_2)

Then the output would be SIG = SIG_E || SIG_M

Verification can happen in parallel and we get the benefit of PQ/T hybrid, plus we get SUF-CMA. 

Thoughts?


Thank you,
    Ryan Appel

> On Sep 30, 2026, at 3:12 PM, Jan Klaußner <jan@klaussner.biz> wrote:
> 
> 1. Should the WG work on PQ + T Hybrid Signatures for TLS?
> 
> Yes
> 
> 2. Should the WG only work on one: -pqt-dual-certs or -composite-ml-dsa?
> 
> Yes
> 
> 3. Should the WG work on: -pqt-dual-certs?
> 
> No
> 
> 4. Should the WG work on: -composite-ml-dsa?
> 
> Yes