[saag] Re: post quantum guidance draft

Nico Williams <nico@cryptonector.com> Mon, 01 December 2025 16:49 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: saag@mail2.ietf.org
Delivered-To: saag@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id BF7E99356D5C for <saag@mail2.ietf.org>; Mon, 1 Dec 2025 08:49:51 -0800 (PST)
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_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=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 LEGXYysvqEc1 for <saag@mail2.ietf.org>; Mon, 1 Dec 2025 08:49:50 -0800 (PST)
Received: from gerbil.ash.relay.mailchannels.net (gerbil.ash.relay.mailchannels.net [23.83.222.67]) (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 6DE179355D67 for <saag@ietf.org>; Mon, 1 Dec 2025 08:46:55 -0800 (PST)
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 9596E80262C; Mon, 01 Dec 2025 16:46:48 +0000 (UTC)
Received: from pdx1-sub0-mail-a239.dreamhost.com (100-98-121-71.trex-nlb.outbound.svc.cluster.local [100.98.121.71]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 42DE7802256; Mon, 01 Dec 2025 16:46:48 +0000 (UTC)
ARC-Seal: i=1; a=rsa-sha256; d=mailchannels.net; s=arc-2022; cv=none; t=1764607608; b=JtOE3TT4tIvXGa1bBC0snc/ttH6aQ/JTiFT33hPA9FjK/zW1fK91hhkULc4PMQGmNEX4eH /HCrQFxIffu11MYe387M7JcAzD/MlUtK+7Egx9t4TX0ji9GX4IL/63ulVWSWohMmQwjeZ3 vzRiS+gCb5MTb9lwZH0Kc1mZ0AV3ax061/g/2S65hH3fKWEwHKC3g0rjGvoKvRl2lHNPRC xBfTUR2MIz0VAQOa8iIxCIerCQxQjl0Cbqy89prj0gS/hIl4+OrAJ8Fi5qVLKx3xEYgCUY yKhdpJmI6fD4hXxd6lrMNmffLZ3lELx6D6Lvo+6WzqHKN9gfyARRmsNhX7UR0Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1764607608; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references:dkim-signature; bh=5SVBnCiWwwPYnYLwsQB3OY02Trl1zU1n8ZUPzGl7+uc=; b=F5wCkCFEe0Q47fItFALbN2soksAN0anEQyWvtmlWyrGn7kVAu/YtDbN4mayjhuWhCq5v9Q MgAEnBW4D5I+lUP/EzAEG89PFUbFLqvbAwBL0YGZxHIpxa8hM15tsyCsU0OLdh0mkcUOwV SVyYs3wwZ8Yvd0tsRmYuRDWaYpBBVC/LC8azRTEdAEe9aWcFpHZgoDix1yz/wukVdLhizw ZKpLNd3Zhm7MC5Fw4PRF5BkhA3HhMAGzJXYhuHzf+du4+qDuAyvDKZ3xWay+tlpF9X4+St d5ADMX9RUzEkLTFN6QpVCtiL0rJF7BR5aPRh3wSZGKWU1gkHf3a/0tOXQ4VRmA==
ARC-Authentication-Results: i=1; rspamd-545f6844bd-nlp9s; auth=pass smtp.auth=dreamhost smtp.mailfrom=nico@cryptonector.com
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-Shelf-Rock: 336ba5d22ac553f8_1764607608506_3523259678
X-MC-Loop-Signature: 1764607608506:3130414500
X-MC-Ingress-Time: 1764607608506
Received: from pdx1-sub0-mail-a239.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.98.121.71 (trex/7.1.3); Mon, 01 Dec 2025 16:46:48 +0000
Received: from ubby (unknown [75.81.95.64]) (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-a239.dreamhost.com (Postfix) with ESMTPSA id 4dKqYg4t92z107P; Mon, 1 Dec 2025 08:46:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptonector.com; s=dreamhost; t=1764607608; bh=5SVBnCiWwwPYnYLwsQB3OY02Trl1zU1n8ZUPzGl7+uc=; h=Date:From:To:Cc:Subject:Content-Type; b=PIC2KD8MrPt+1O2iJP2cHJwHm7TOAn5fw4r/8gtmzVh0+R0fz63G3GUw3nAd3cBRa Gtf55AI4MK2ylJEZBHWLVD5CBy5+vMkqrTQPfYO5DqfoGvM241sKo2iE+78ZOpvYIj ilbITJz0/x7ih2Cd5lO9o372nqE/p0uSKea4ClZTuZsZYMnGqJ77H7xsj9wQwKLsNw h2ryJfabB1yUIHPfswtAnyigaWsAkBm6owsI0bCA5kNioxHVP6sG/H57aqw3aiLHxk 3YnKJU28lSUj8VcO8K1DZ+V+1m1ybBWCwjVraCBNbDyHISAL7LqE8FYPQS3Pda1jPa gu4WbYH3G7qkg==
Date: Mon, 01 Dec 2025 10:46:45 -0600
From: Nico Williams <nico@cryptonector.com>
To: Eric Rescorla <ekr@rtfm.com>
Message-ID: <aS3GdVE8H5rrcmdn@ubby>
References: <5f1f3a9e-21d0-4ded-bdc0-b70ee431f68e@cs.tcd.ie> <CABcZeBNMT2Osr4wMTX4Zv+MP-ojVcY2Wr3ux=kM-ZcuvKFKXGg@mail.gmail.com> <98e5269b-1f63-4f80-8fc5-98e490eaba56@cs.tcd.ie> <CABcZeBPt267XOj395wjbOTZxp+ME6EKiaqmRjRaoGWGUC7-3xQ@mail.gmail.com> <d0e03c79-3caa-491c-9d94-41d3a284883d@cs.tcd.ie> <CABcZeBOhMKySDQVZ22auVD2DbsyLCQXpqdb0xDEc4NrDtB1V3A@mail.gmail.com> <4aa704b4-026c-4378-8f2f-64f7a549d082@cs.tcd.ie> <CABcZeBMHO2rcw6k7g9n6C1mTOG0CdO4Q4DPXPvKq+H2QSsNLgw@mail.gmail.com> <56e8b252-a1e9-42e0-a8d7-e97b289b89ee@cs.tcd.ie> <CABcZeBOvQSCxYJ0o9MzEfCWQaruur_k-e4CErZXohvvSiuF2fA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CABcZeBOvQSCxYJ0o9MzEfCWQaruur_k-e4CErZXohvvSiuF2fA@mail.gmail.com>
Message-ID-Hash: SLUVAWEPHFQS7CM4ZFMIM7G5GYALN524
X-Message-ID-Hash: SLUVAWEPHFQS7CM4ZFMIM7G5GYALN524
X-MailFrom: nico@cryptonector.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-saag.ietf.org-0; header-match-saag.ietf.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "saag@ietf.org" <saag@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [saag] Re: post quantum guidance draft
List-Id: Security Area Advisory Group <saag.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/ZfqiOOI71nOhiFjUqZn3wp0Gbw8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Owner: <mailto:saag-owner@ietf.org>
List-Post: <mailto:saag@ietf.org>
List-Subscribe: <mailto:saag-join@ietf.org>
List-Unsubscribe: <mailto:saag-leave@ietf.org>

On Mon, Dec 01, 2025 at 08:16:41AM -0800, Eric Rescorla wrote:
> To the extent to which you just want to address the problem of lack of
> guidance about PQ algorithms, I would suggest that a better way to do
> that would be to try to get to some consensus about whether there
> is in fact a problem that needs to be solved and what that problem is,
> separate from the merits of this particular draft.

We probably could not achieve IETF rough consensus on any proposition
regarding non-hybrid PQ algorithms (whether to work on them, whether to
make them recommended/MIT, have a moratorium on them, etc.).

This is why doing things at the WG level is the only way to make
progress, except then we have the same problem: that we might not be
able to reach WG rough consensus either.  And so here we are, with
constant appeals of WG consensus calls.

TBF I no longer think that an I-D like Stephen's can help for this
reason, that we would be deadlocked.  Except maybe that we could get
consensus on a _short_ moratorium, like say one year, but probably not
either (one author wrote to me bitterly off-list about this being
his/her long-time work we're talking about [as if hybrids would somehow
cause their work to not be used!]).  I expect that those who wouldn't
agree to stick to hybrids for now wouldn't agree to any specific length
of time for a non-hybrid PQ moratorium out of fear that one year will
turn to five, and then five into even longer, thus I figure no consensus
can be achieved on any proposition.  And with controversial calls of WG
consensus are more easily defended than controversial calls of IETF
consensus, I understand why we'll end up w/o a cross-area advice
document here -- but ideally we'd seek IETF consensus because DJB's
concerns might really not be remote.

Nico
--