[Plants] Re: Scope and charter

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 13 August 2025 17:19 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: plants@mail2.ietf.org
Delivered-To: plants@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 151CC53A9775 for <plants@mail2.ietf.org>; Wed, 13 Aug 2025 10:19:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_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=sandelman.ca
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 evfXxWSC3SS7 for <plants@mail2.ietf.org>; Wed, 13 Aug 2025 10:19:00 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (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 9FB5A53A9767 for <plants@ietf.org>; Wed, 13 Aug 2025 10:19:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id C34C11800D; Wed, 13 Aug 2025 13:18:59 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id pESIHWTUt7xx; Wed, 13 Aug 2025 13:18:59 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1755105539; bh=5V4xxJfUXppQA89MhlHvwUY0lNcb5dwlcDE9lZtDeYI=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=rNco0HzN2MoNCZx8W7BgbNyzsOlHVMrOi0RNm95r9KCjhr9FgZc6ILUNghHpZu552 SK7GDrqhKSJR1H1MvuPOTLIy17+/8CGbRiNi3oQnY7j2r4WRxaEJXnaKnINqTotgZY /q6DrHYu/nyopVuUssRCt6WAatSTnNo+3UQWd07QlmWHQHEqVs4BIfuEnwFC8lP5Zg 7B3x+/79BCePUfdf1FmSeXDt1kMAXi/07kF1ekvtlAi/Wk0TnMlIolLUS6ewkTwXx8 6XkiZH7EbFyp+Nvy1gibbC99AJYnR+3bor02xf8cJ0UOl+P/ZbMk8Ygw4ood/zWucl 9kH3AmkzLFtcA==
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:b241:6fff:fe09:a92b]) by tuna.sandelman.ca (Postfix) with ESMTP id 003D11800C; Wed, 13 Aug 2025 13:18:58 -0400 (EDT)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id EE11E1AE; Wed, 13 Aug 2025 13:18:58 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Felix Linker <linkerfelix@gmail.com>
In-Reply-To: <CAPeSrypwQvJkx6cR3vZ2ZzA7mYggfVRFuy7nPXJKWpgJN915pg@mail.gmail.com>
References: <CAMjbhoWghiphLsq8OS-hOiYTPDSkO-_o9JYq2Wbtey4oBW6eyA@mail.gmail.com> <97AE4984-E6B4-4C3C-9A7B-7A0900110FDF@thomwiggers.nl> <CAFR824w+pzfyKDXWWJ0uytFLKF3id9uL_JY2Du9458YxXZzG2w@mail.gmail.com> <PH3PPFA3FE8A23F1AB56FA437BE4CA8C418C12DA@PH3PPFA3FE8A23F.namprd11.prod.outlook.com> <CAFR824wUSFNTDzFn2hMbaa+3Jpe2apa82x74D3zp5NrZBgquWQ@mail.gmail.com> <CAF8qwaC+_R6qAQiEmHbg+s4zoOEvOiTS8CYB8CMwyrQsAM=84g@mail.gmail.com> <CAPeSrypwQvJkx6cR3vZ2ZzA7mYggfVRFuy7nPXJKWpgJN915pg@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 13 Aug 2025 13:18:58 -0400
Message-ID: <10353.1755105538@obiwan.sandelman.ca>
Message-ID-Hash: UENWBCK46XPRFBQLNW2LR7YDABWYIOUR
X-Message-ID-Hash: UENWBCK46XPRFBQLNW2LR7YDABWYIOUR
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: David Benjamin <davidben@chromium.org>, Deirdre Connolly <durumcrustulum@gmail.com>, "Scott Fluhrer (sfluhrer)" <sfluhrer@cisco.com>, Thom Wiggers <thom@thomwiggers.nl>, Bas Westerbaan <bas=40cloudflare.com@dmarc.ietf.org>, plants@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Plants] Re: Scope and charter
List-Id: "PKI, Logs, And Tree Signatures" <plants.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/plants/ax5AkPzHaLChexlAldc8bqMhQJA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/plants>
List-Help: <mailto:plants-request@ietf.org?subject=help>
List-Owner: <mailto:plants-owner@ietf.org>
List-Post: <mailto:plants@ietf.org>
List-Subscribe: <mailto:plants-join@ietf.org>
List-Unsubscribe: <mailto:plants-leave@ietf.org>

Felix Linker <linkerfelix@gmail.com> wrote:
    > I wonder, though, whether the initial charter is too constrained. The first
    > sentence says: "The goal of the PLANTS Working Group is to trim the costs
    > of large post-quantum signatures on PKIs with Certificate Transparency
    > [...]." Why the focus on PQ-signatures? Would this forbid any improvements
    > to the ecosystem that do not relate to PQ-signatures? It seems better to me
    > if the charter just said: "The goal of the PLANTS Working Group is to trim
    > the costs of PKIs with Certificate Transparency [...]."

    > I also find it odd to already constrain the WG by which mechanism it will
    > use to trim those costs (be they due to PQ-signatures or not). Looking at
    > the entire certificate issuance and CT system more broadly seems like the
    > better approach to me.

I suggested:
https://github.com/davidben/merkle-tree-certs/pull/123
   The goal of the PLANTS Working Group is to rethink the tradeoffs between
   certificate signatures and Transparency Logs.  This is driven the size and
   performance of quantum-safe algorithms.  The initial focus of the WG is on
   PKIs that use Certificate Transparency (CT; RFC 6962 and RFC 9162), with
   interactive protocols like TLS (RFC 8446) and IKEv2 (RFC7296)

Bas complained that maybe I'm missing some words after tradeoffs.
But, I think this is the higher-level thinking that you are interested in.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide