[TLS] Re: Fwd: New Version Notification for draft-yusef-tls-pqt-dual-certs-02.txt

Ilari Liusvaara <ilariliusvaara@welho.com> Tue, 14 July 2026 17:44 UTC

Return-Path: <ilariliusvaara@welho.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 E5D45116B6F15 for <tls@mail2.ietf.org>; Tue, 14 Jul 2026 10:44:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784051098; bh=Gfne2vr4hZRqdR2cdFSZmiLfmqszAAS0pnJ6nrI08Po=; h=Date:From:To:Subject:References:In-Reply-To; b=C83hn7MnlXoFsbeID8U2FMZ+Q/rm/sP33R9zfpU5hbYNdnNzbr7S1dmphtNW+warj Tmk8hB1xa0s5zVGKIv3H3G8phXfTF1U11TdOzhUmb07VeisAXOpbjiUTwfDhkkN1jP p8tqhkyxyZ1q0GYg4PgxMvKMpp9386J2IlzUlHnQ=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=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=welho.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 VQXYprdrQpDz for <tls@mail2.ietf.org>; Tue, 14 Jul 2026 10:44:58 -0700 (PDT)
Received: from smtp.dnamail.fi (sender001.dnamail.fi [83.102.40.178]) (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 1A5CC116B6F0B for <tls@ietf.org>; Tue, 14 Jul 2026 10:44:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.dnamail.fi (Postfix) with ESMTP id 48E862113E11 for <tls@ietf.org>; Tue, 14 Jul 2026 20:44:51 +0300 (EEST)
X-Virus-Scanned: X-Virus-Scanned: amavis at smtp.dnamail.fi
Received: from smtp.dnamail.fi ([83.102.40.178]) by localhost (dmail-psmtp01.s.dnaip.fi [127.0.0.1]) (amavis, port 10024) with ESMTP id ttmStb92BC7u for <tls@ietf.org>; Tue, 14 Jul 2026 20:44:50 +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 B1E162113E00 for <tls@ietf.org>; Tue, 14 Jul 2026 20:44:50 +0300 (EEST)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.dnamail.fi B1E162113E00
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=welho.com; s=2025-03; t=1784051090; bh=l0VoK9LTyhDkJvjVGK28z6Bk7tyTAsJ5QdksxhcMJlk=; h=Date:From:To:Subject:References:In-Reply-To:From; b=XKbHq/AyHNL41MdHwwHgZQrcR4IZyWsu2nKJh99g3hKaBH6WOS/NdDXrYNP1lKXBn K2kTWvp5qnBaUICr6AVC8X4JgtUSog5fa90kXv1VT2X71QN80W0uWUAYnHkIO/fsNY 1tScNANcdDc0O2Bvopqzu8ukf5F+a5h/HgUdnGr9GYtcNPY33um4vw0UGimcTBw52b 9FEPL3TM9Pvu/+uUEV4bQ//vZL1xuJMyBvUoqvjtquXczsWSAacxMjphMst+5P8OH3 GmTmtCAbhbGh9SLeMyMf9ujxVZN//z7uRplvm/El11B0+tB0dVCIMPuDPQEkq2ib2I D8IU9gkRKyRFw==
Date: Tue, 14 Jul 2026 20:44:46 +0300
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: "<tls@ietf.org>" <tls@ietf.org>
Message-ID: <alZ1jj4wZbP_bL2v@LK-Perkele-VII2.locald>
References: <178228974031.1336043.8757141113647810543@dt-datatracker-f9b87776f-xzl65> <CAFpG3gcOChbpjRMAJhwErFRoFcJgtf=C9d0KLeAoQGxG+OxFgA@mail.gmail.com> <CABcZeBPo0Z4YFAR7Gmeo0xWpEscEXt+Do25n7Pxga5zOwULf0A@mail.gmail.com> <CADNypP-8c1+Zqo1SVjyz1MHWeAWzd7keX-W2tjz-vFj6JnZ8wA@mail.gmail.com> <CABcZeBOu5HU-Mcrepz-VzOuuBCP=chhPZFbGLwT9XQeAi91QyA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CABcZeBOu5HU-Mcrepz-VzOuuBCP=chhPZFbGLwT9XQeAi91QyA@mail.gmail.com>
Sender: ilariliusvaara@welho.com
Message-ID-Hash: ADF6VAM55V2YKOYR45WHFET7XJSWFXUR
X-Message-ID-Hash: ADF6VAM55V2YKOYR45WHFET7XJSWFXUR
X-MailFrom: ilariliusvaara@welho.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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Fwd: New Version Notification for draft-yusef-tls-pqt-dual-certs-02.txt
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/ztwq-z7vFG10JKprvaROa_cHZu8>
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 Tue, Jul 14, 2026 at 07:41:16AM -0700, Eric Rescorla wrote:
> On Tue, Jul 14, 2026 at 5:10 AM Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com>
> wrote:
> >
> > Can you elaborate on what you mean by "superior" in this case?
> >
> 
> Yes, I think the complexity of this approach outweighs the alleged
> benefits.

I do not think this is complex (after some simplification). I think the
main drawback is the hell this plays with TLS client APIs. Yes, I used
to think this would be far too complex to feasibly implement.

With regards to benefits (after simplification), I think the main one
is avoiding a combinatorial explosion in an exceptionally nasty place.
 
I consider both pretty major. So one has annoying high benefit, high
cost situation.


> > Given modern automation (ACME) and shortened certificate
> >> lifetimes, it's hard to believe just issuing the certificates is a big
> >> deal, though perhaps technically being able to make the composites is?
> >>
> >
> > I am not sure I understand this comment. Can elaborate on this?
> >
> 
> You're going to need to issue a lot of certificates anyway, I don't see why
> issuing the composite certificate is a big deal.

As an operator, I can say that issuing composite certificate is a big
deal, even with automation like ACME. Because it involves actions that
can not be feasibly automated.




-Ilari