IETF Logo Mail Archive

Re: [Pqc] Listing pointers to not-yet-standardized PQC algorithms

Christopher Wood <caw@heapingbits.net> Mon, 15 May 2023 19:06 UTC

Return-Path: <caw@heapingbits.net>
X-Original-To: pqc@ietfa.amsl.com
Delivered-To: pqc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7EBC13AE25 for <pqc@ietfa.amsl.com>; Mon, 15 May 2023 12:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=heapingbits.net header.b="s8SjFLwZ"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="KnG3mmWX"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ZEFa4YKfwwV for <pqc@ietfa.amsl.com>; Mon, 15 May 2023 12:06:33 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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) by ietfa.amsl.com (Postfix) with ESMTPS id C49A7C1BFEE4 for <pqc@ietf.org>; Mon, 15 May 2023 12:06:33 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 221E05C01A2; Mon, 15 May 2023 15:06:33 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 15 May 2023 15:06:33 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heapingbits.net; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to; s=fm1; t=1684177593; x=1684263993; bh=eeygYZbYJ0iNaCgd3r/y5kfIK b+qbF8HFljZKbB8HeE=; b=s8SjFLwZa0kiN/l966i/vqLoHvPoM3tk6PgmN19Vx 95c8smt25g20wDbE9Ac1bJ7J76cBIVrKFVT5As2BtoQleWIaYQnd7LfY6W+mmmJU KKz0p9UrjnE+Lf6IXG21aP+ZT25eGqVkvQz36UNLP+driq4TQ+rcqZBQi3JbP1Ul ILnVaaIAuNJlRRkk2O/+jlJMePDbt+KfWugMoZdh1yxPDYTiQ5tfXfkzuIBkIe8P dhNijrl8gk/z48F39n42frNvtNW31gqb/8KD8H/LW409mgiAiRFkczWD8vJyeJ/s L5zovq+rfdZUKL3rxSPbKoCyFBKncgypQ6K2r9PAUUh8A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1684177593; x=1684263993; bh=eeygYZbYJ0iNaCgd3r/y5kfIKb+qbF8HFlj ZKbB8HeE=; b=KnG3mmWXPeAAmP4RGhKzzJsJdOJ3EIQ+KA0lntA4eJgg7OQh10O nvKYPqGFMFKMgL/II9gQ0qk4kXpJ6G8J9tsQqm1hyT8nAgybYz2recvFavvvVkbi evMc/GiW3gqFPVarFcsRI65uflvhCjRt8IeniaTCT4OS9bdUZtDs/Tncu8mxbBgP 7prrraQWj+ZFrGUBcbkN+X9bQGdH/LHzGiwg5NMoTQ2YFSmOGtYEpml5QgpJ7Ktl WHdIp+of6hObmqoh6nxFs86l/s2l1ViRmyaaP+5zTZDQFelPHYw92dAlcWKILuaq Qt9WtCUZKzx0GcIVZ27rnxmmOBqxoezXwuQ==
X-ME-Sender: <xms:uIJiZMy_Nffi_r2TGSgkpNuDCWdSd5_0K53QPdFqJuusGoorr2iTcA> <xme:uIJiZAQOOowuR_bGtZqcz6FralFbVhi8WAygsqnQvPloXvrYMZqqXky-Grt6B0PIG DI9qA7LCu5grel9SZY>
X-ME-Received: <xmr:uIJiZOXnXzh-qtHUNi2QGwdkHyqG8nA9zTAD4iq5mHhOg_CGvxEIMLkNTeGxjz7-tKIT9xI0Be-5qXA3Rz8i1Jde-n6YZjE1X2I-c4hbRZlktIF1pTmyVA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeehjedgudefhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurheptggguffhjgffvefgkfhfvffose htqhhmtdhhtddvnecuhfhrohhmpeevhhhrihhsthhophhhvghrucghohhougcuoegtrgif sehhvggrphhinhhgsghithhsrdhnvghtqeenucggtffrrghtthgvrhhnpefhjedtleektd duhfeihfethfekvddthedtgfekieejheffhedvieefveeugfetueenucffohhmrghinhep ihgvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomheptggrfieshhgvrghpihhnghgsihhtshdrnhgvth
X-ME-Proxy: <xmx:uYJiZKjmLM3TEVGcOrelOuZ-nWkTL6MwTNHuBsZ4RTRDS9HA12dMqA> <xmx:uYJiZODpfEKxuNmz8vDKgTGnEiQcLGM13eh6K3R7SrYhC0jAlJnh4Q> <xmx:uYJiZLJwteTq2U99DXlZCgMxt0BH7L2rbEX15zAQyWeIKuUGWquM9A> <xmx:uYJiZP4eqx9_Ih_6N17P4OLpB602HW1XXH2b4xRknuNVkK73O8zYbQ>
Feedback-ID: i2f494406:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 15 May 2023 15:06:32 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Christopher Wood <caw@heapingbits.net>
In-Reply-To: <bb1d8e9f553c41d6a922f80801508945@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
Date: Mon, 15 May 2023 15:06:31 -0400
Cc: "D. J. Bernstein" <djb@cr.yp.to>, "pqc@ietf.org" <pqc@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5CB7B673-4F55-434C-B900-E0B7FB55885F@heapingbits.net>
References: <ea9c9716-cc17-8958-292e-e0e12aff1741@nohats.ca> <20230515183021.276157.qmail@cr.yp.to> <bb1d8e9f553c41d6a922f80801508945@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
To: Roman Danyliw <rdd@cert.org>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pqc/xRrJTw51eSC0ayxHLoSCnl4Gcro>
Subject: Re: [Pqc] Listing pointers to not-yet-standardized PQC algorithms
X-BeenThere: pqc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Post Quantum Cryptography discussion list <pqc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pqc>, <mailto:pqc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pqc/>
List-Post: <mailto:pqc@ietf.org>
List-Help: <mailto:pqc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pqc>, <mailto:pqc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 May 2023 19:06:38 -0000

> On May 15, 2023, at 3:01 PM, Roman Danyliw <rdd@cert.org> wrote:
> 
> Hi!
> 
>> -----Original Message-----
>> From: Pqc <pqc-bounces@ietf.org> On Behalf Of D. J. Bernstein
>> Sent: Monday, May 15, 2023 2:30 PM
>> To: pqc@ietf.org
>> Subject: Re: [Pqc] Listing pointers to not-yet-standardized PQC algorithms
>> 
>>>> Also, to clarify, are you saying it was out of PQUIP's scope for the
>>>> UK NCSC to write "I think we should focus on the NIST algorithms"?
>>> People can choose what to focus their time and energy on within the WG
>>> on things that are in scope.
>> 
>> Please clarify. If making "any choices of PQ algorithms" is supposed to be out of
>> scope then how can "focus on the NIST algorithms" be in scope?
> 
> PQUIP's charter doesn't constrain the behavior of the UK NCSC.
> 
>> Right now I'm unable to figure out concretely what's being claimed about the
>> PQUIP scope, never mind the question of how this claim is supposed to follow
>> from the PQUIP charter (and the meta-question of how my quotes from the
>> charter were supposed to be missing something relevant).
> 
> The PQUIP WG is not focused on (or chartered) to standardizing anything.  It won't choose any algorithm because such design choices will be left to WGs which are standardizing protocol behavior. The primary focus of PQUIP can be best summarized from this charter text: "[t]he WG will provide a standing venue to discuss PQC (operational and engineering) transition issues and experiences to date relevant to work in the IETF."
> 
> PQUIP is relatively new class of WG, patterned after "IOT Operations" (IOTOPS, https://datatracker.ietf.org/wg/iotops/about/) and "Media Operations (MOPS, https://datatracker.ietf.org/wg/mops/about/), to provide the IETF a standing venue to discuss topics that might need cross-WG consideration.

This cross-WG point seems really important here. Up til now, I was wondering why, e.g., TLS would not be the venue to discuss PQ variants of TLS (AuthKEM and the like). I can see the value in having a venue for discussing cross-WG issues, should those arise. 

Best,
Chris

v2.23.0 | Report a Bug | By Email