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

Paul Hoffman <paul.hoffman@icann.org> Mon, 15 May 2023 18:53 UTC

Return-Path: <paul.hoffman@icann.org>
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 843A1C1E8BB3 for <pqc@ietfa.amsl.com>; Mon, 15 May 2023 11:53:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 M5ki_u34vUts for <pqc@ietfa.amsl.com>; Mon, 15 May 2023 11:53:33 -0700 (PDT)
Received: from ppa5.dc.icann.org (ppa5.dc.icann.org [192.0.46.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BFBEC1DF995 for <pqc@ietf.org>; Mon, 15 May 2023 11:53:33 -0700 (PDT)
Received: from MBX112-W2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.5]) by ppa5.dc.icann.org (8.17.1.19/8.17.1.19) with ESMTPS id 34FIrUiG026661 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 15 May 2023 18:53:30 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.26; Mon, 15 May 2023 11:53:29 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) by MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) with mapi id 15.02.1118.026; Mon, 15 May 2023 11:53:29 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: "D. J. Bernstein" <djb@cr.yp.to>
CC: "pqc@ietf.org" <pqc@ietf.org>
Thread-Topic: [Ext] [Pqc] Listing pointers to not-yet-standardized PQC algorithms
Thread-Index: AQHZh16J/g+0lHQpgE+moPzlNVg28A==
Date: Mon, 15 May 2023 18:53:29 +0000
Message-ID: <F5B34B1D-0FBD-4A8D-8999-1CA999F399E5@icann.org>
References: <20230515183021.276157.qmail@cr.yp.to>
In-Reply-To: <20230515183021.276157.qmail@cr.yp.to>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FF5AAE67A0E7FA469036CA55C61CFD80@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.957,Hydra:6.0.573,FMLib:17.11.170.22 definitions=2023-05-15_17,2023-05-05_01,2023-02-09_01
Archived-At: <https://mailarchive.ietf.org/arch/msg/pqc/j-EszsKVV0W9ZV8sty2oFydJA3I>
Subject: Re: [Pqc] [Ext] 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 18:53:37 -0000

On May 15, 2023, at 11:30 AM, D. J. Bernstein <djb@cr.yp.to> wrote:
> 
>>> 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?

I'll respond as one of the co-chairs. Anyone can contribute opinions to the list. If the ensuing discussion goes far afield from the charter, then it is the chair's responsibility to try to gently rein it back in.

There is a large difference between the WG making choices for other WGs and us discussing how the other WGs make their choices. That was part of my motivation for starting this thread. If one WG wants to wait for NIST to standardize its first KEM before standardizing that WG's protocol, and another WG wants to wait for NIST to standardize additional KEMs because that WG knows now that it won't like the first KEM (even though that means delaying and thus more traffic will be captured), and yet another WG wants to standardize a non-NIST KEM for some reason (which might make finishing the protocol go faster or slower): all of that is reasonable to discuss in the PQUIP charter. In particular, discussing how delaying standardization affects the amount of traffic captured is in scope.

> 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).

I hope the above helps. I also hope that your inability is due truly on lack of clarity in the charter that can be corrected if others agree, and not due to your desire that the charter says something different. If the latter is more true than the former, please craft a new charter (taking as much of the current charter as you can), and submit it as a personal Internet Draft for the WG to consider.

--Paul Hoffman