IETF Logo Mail Archive

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

Roman Danyliw <rdd@cert.org> Mon, 15 May 2023 19:02 UTC

Return-Path: <rdd@cert.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 7F4B3C0DA97B for <pqc@ietfa.amsl.com>; Mon, 15 May 2023 12:02:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-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 (1024-bit key) header.d=cert.org
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 iDPgPVux9fd3 for <pqc@ietfa.amsl.com>; Mon, 15 May 2023 12:02:36 -0700 (PDT)
Received: from USG02-BN3-obe.outbound.protection.office365.us (mail-bn3usg02on0718.outbound.protection.office365.us [IPv6:2001:489a:2202:c::718]) (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 331E3C06F25A for <pqc@ietf.org>; Mon, 15 May 2023 12:01:31 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector5401; d=microsoft.com; cv=none; b=GeDN7y4RZppmBKgZipkzo8lNtkYOYPspeWPg6GydEBu/4O7plc3Ghd2DsZSb1R1UVljnzCSZzcWnBToaThQFZYKKAPyFT2P4hMkXJMQuiGIDUt/0bm/rWB2cTNtwlCxfC5UxIKTRX3epbbfpiQYv2WJAo/10bq2CIErkyG6B05fdUdT65nzc0tjeSitRHrY4EMAbbsME8FHXxaWlMb+MJqevJVbwJxV2IgxlVj65QVk6Ni/HFilEXpUq6AMv5A4rzxWGwbm7soWa/Tj72W/U/Dp7iP4j9hXGs4X+JsIYAiFiy4hzF9p+zKLlu4ehUp0OnldbkMVWcCu28KmAR1inVg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector5401; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=HPXfsQINYCc5B76YpV2yi/ojT5yyQVEn+fME8m9KY4E=; b=QKcc1qDauLXzVYg6oDDFHMFdY5FFe6deNWHnKcuuR244cF//k6YZOBmmMe5+qK7Ln3kSHOI6arES9mb34EU4883rCAdDJ/SAG+HA0C4eiKIE52GreORuNSVJQLCdJiTj2vT+Gqin626bL+xp1nzs9fa+Sxb/jQWvQ7s5uzMBoIy3fpw6aNf1Fkblt5VIUqYd4I0Ks59zOuqS/8fBYABj47PmVQZC0W4YSYo5g+9jdcB7qhi7HabrIXf3ury2XVivfi4ui1oG5fl5w/sfIAgM/H+/oxbnsP6hC5pk4guxRSP5hTdiLonKocRZSq8nK0kqDn6zyl1HUXT/QDyOVLh8zg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cert.org; dmarc=pass action=none header.from=cert.org; dkim=pass header.d=cert.org; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HPXfsQINYCc5B76YpV2yi/ojT5yyQVEn+fME8m9KY4E=; b=F7e6dmkCWHuf36XX5ZMtftHWJhRq+4RdlME3MASIWo7fuX/Jr5fxAOOMfZODFydsEcUOA+uQ0xSF83Lt9nBHN5bEQbcy8YxI03ThRT1TcCvI6H5j/04iadCZOAVS1rRk1P7k8qIsDCErNR8oIM17SzAi0L5t3KlleYszlwAlbzQ=
Received: from BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:168::11) by BN2P110MB1732.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:169::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6387.30; Mon, 15 May 2023 19:01:26 +0000
Received: from BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM ([fe80::29b2:8307:6a90:c79f]) by BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM ([fe80::29b2:8307:6a90:c79f%7]) with mapi id 15.20.6387.030; Mon, 15 May 2023 19:01:26 +0000
From: Roman Danyliw <rdd@cert.org>
To: "D. J. Bernstein" <djb@cr.yp.to>, "pqc@ietf.org" <pqc@ietf.org>
Thread-Topic: [Pqc] Listing pointers to not-yet-standardized PQC algorithms
Thread-Index: AQHZhbnRih1MssNROEe40ZAqgSGv369bdWsAgAANV4CAAB+DAIAACOSAgAADaSA=
Date: Mon, 15 May 2023 19:01:26 +0000
Message-ID: <bb1d8e9f553c41d6a922f80801508945@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
References: <ea9c9716-cc17-8958-292e-e0e12aff1741@nohats.ca> <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:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=cert.org;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: BN2P110MB1107:EE_|BN2P110MB1732:EE_
x-ms-office365-filtering-correlation-id: 57ffd0c1-e0f2-45e8-fd30-08db5576c8dc
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: LD4cEhvm55tHa3YFO0CRAagv5xR5Z2bkiFeKKEvusPXoNwmqLc6mDFvPs/j73TFeuVr1pJSQniBXlz7q+aBYQxTI44CmX2nXWuGcKhnndExlOmnSP60mzGSY4HlEqdFAoZffcthiPYm1wtv8+ivVT+fO/W3J+6XfzTOqUs2uDGEUVwU7KeLwVBUuCd8JsvKMI/7efDLTjmiNI9OmdhElQE/4vQXO3oHZaKzZ4nrd+TQnTcfSKa3pLhrs0zXwxB92yfmXZgUDCe52SCzPpUxLJ6zubQ2wgNs0Y2Rl4XJfQAkMOhh4OSHKe1WcX3aFHHt+8QRAJBy+Ewq7LqU0gGWf2w3dib+SCpnf8WRudysCBYrSJt9FQADcMMegqychnYHrtw+DAp39OlKt2OgZ6kuGflBN6jOieGYN8B/XY8SMemA3b4cRLDAw61XoYqed/TUMtnr1PcKdnosC3wnDYxp63hU3J6U9vxtrfQxHH2Lc4CAwIu1w5ccxlMyjN8Hyurh7otkqA/InKUX6S+2/XzT5wD5VlzeWvcbSE+d4Lh0nMC/shvEhjRSlNRDuo4M4x0zu
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFS:(13230028)(136003)(396003)(39830400003)(366004)(451199021)(6506007)(26005)(186003)(53546011)(9686003)(8936002)(8676002)(55016003)(38070700005)(41320700001)(2906002)(82960400001)(83380400001)(38100700002)(64756008)(66446008)(66946007)(76116006)(66476007)(66556008)(108616005)(966005)(7696005)(24736004)(110136005)(508600001)(41300700001)(122000001)(5660300002)(71200400001)(86362001); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: qzCYfgf37pS+8IeZ39efM33WATCsyldHDoNVs99NaGLFHNFIpCNtu2LZWtvmdWBGbIKHnakuZbJZyBuNYUPcuGQywPo3vlYL3JV/ohPm+8lIecS1sJDwCBpUgPFi+DJbF9GwNoovhA8vJw+q5TFZISWQ1UlOfUxEQINnhdVUVDpU41sPacksaFqd78GIiWu+x5OUP2gGZXecvHjLKZDOxuFXxzd21xnvlFD4pLEZ+Qehkbo3cxRDRJrK55VnTkwbIktxwLVsqVfLIh8vsNzMY9A6YPhIwA53wzjov0wMpM2oy2JWO1pX+QEfZi52vB/ciG6zTUqoads6x8c/pRTQhe63cuskTOpjKJiNPer1gS/r6/rH+CS3XbyDqbrug8pNcYhFTBXMgAxo9vT2ox9WzTgUqQaNCrxyzKkulEY+Rww=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: cert.org
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 57ffd0c1-e0f2-45e8-fd30-08db5576c8dc
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 May 2023 19:01:26.7315 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 95a9dce2-04f2-4043-995d-1ec3861911c6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN2P110MB1732
Archived-At: <https://mailarchive.ietf.org/arch/msg/pqc/GTKIw06PBQWSfZysXuru7hyJa0A>
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:02:40 -0000

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.

Roman

v2.23.0 | Report a Bug | By Email