Re: [Pqc] [Ext] Mapping the state of PQC and IETF

Paul Hoffman <paul.hoffman@icann.org> Mon, 27 February 2023 15:58 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 C430BC151B04 for <pqc@ietfa.amsl.com>; Mon, 27 Feb 2023 07:58:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, 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 J2vwaTjG695A for <pqc@ietfa.amsl.com>; Mon, 27 Feb 2023 07:58:35 -0800 (PST)
Received: from ppa3.lax.icann.org (ppa3.lax.icann.org [192.0.33.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 C7418C1516E0 for <pqc@ietf.org>; Mon, 27 Feb 2023 07:58:35 -0800 (PST)
Received: from MBX112-W2-CO-2.pexch112.icann.org (out.mail.icann.org [64.78.33.6]) by ppa3.lax.icann.org (8.17.1.19/8.17.1.19) with ESMTPS id 31RFwYTM024630 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 27 Feb 2023 15:58:34 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.21; Mon, 27 Feb 2023 07:58:33 -0800
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.021; Mon, 27 Feb 2023 07:58:33 -0800
From: Paul Hoffman <paul.hoffman@icann.org>
To: Sofía Celi <cherenkov@riseup.net>
CC: "pqc@ietf.org" <pqc@ietf.org>
Thread-Topic: [Ext] [Pqc] Mapping the state of PQC and IETF
Thread-Index: AQHZSsK2d1sByujDbUaxOd2XhN1ubq7jeUaA
Date: Mon, 27 Feb 2023 15:58:33 +0000
Message-ID: <16A23C37-93BD-4F72-BCF9-3E3C689A0591@icann.org>
References: <667bd090-1a3e-82d0-f663-8950fcd6dd38@riseup.net>
In-Reply-To: <667bd090-1a3e-82d0-f663-8950fcd6dd38@riseup.net>
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="utf-8"
Content-ID: <8AE99599CC0CB24881F636AECACA5C26@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.219,Aquarius:18.0.930,Hydra:6.0.562,FMLib:17.11.170.22 definitions=2023-02-27_12,2023-02-27_01,2023-02-09_01
Archived-At: <https://mailarchive.ietf.org/arch/msg/pqc/vC7sAzSg0Zfw0y5ARAD11_KVhy0>
Subject: Re: [Pqc] [Ext] Mapping the state of PQC and IETF
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, 27 Feb 2023 15:58:36 -0000

On Feb 27, 2023, at 7:46 AM, Sofía Celi <cherenkov@riseup.net> wrote:
> We have started work on mapping the state of PQC (if any draft or RFC exists) in the different IETF protocols/WG and IRTF groups: https://github.com/ietf-wg-pquip/state-of-protocols-and-pqc to keep track of where everything is at. Feel free to contribute by sending a PR. We hope this list is useful to many.

Or, if you're not comfortable with opening GitHub pull requests, feel free to open an issue on the tracker or just post something here on the list!

--Paul Hoffman