Re: [saag] About the "Draft text for a PQ Maintenance WG"

Roman Danyliw <rdd@cert.org> Wed, 23 March 2022 12:02 UTC

Return-Path: <rdd@cert.org>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB0E03A0CA9 for <saag@ietfa.amsl.com>; Wed, 23 Mar 2022 05:02:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=seicmu.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 45KliSrWbit1 for <saag@ietfa.amsl.com>; Wed, 23 Mar 2022 05:02:31 -0700 (PDT)
Received: from USG02-CY1-obe.outbound.protection.office365.us (mail-cy1usg02on0139.outbound.protection.office365.us [23.103.209.139]) (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 173723A0C88 for <saag@ietf.org>; Wed, 23 Mar 2022 05:02:30 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector5401; d=microsoft.com; cv=none; b=jDEBkyoHN0aUm2qIeSTglYvHetNQqeNsT/MKmy6qFjKwvaPfH8iUkzuSYtrsUsG6ntFfXl3tVj67b2nYBgVhjGWIHeOrvtHu8oJ8rvG90CjYqXrU05zpqCUK4mZoaERLyCHkg7VDK3H8YT+yN3A93Q9g/r4z7IdpdJ8ptKlhmUTy2Tmea34BL/DBEmmMQ4BczWvasRxcsxUfktDOfdSEFwsWxbjF1rdis56IbVbPLrifGDp6Yx9XiDgL5Wt0mqsALmCYciEZ+hLJSSFo0eCFWJPiafATK7jJYgGn9mS0cCJLns/xcO/IkHUK6OYWZcRNvXp3nAqAS6tACo75e0Rd3g==
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=zw23QZHOtPNzT2kmhcVdUGOtIu6BdUA4/i+qEMlFTvk=; b=pdUWMhYqm25kM9OtnPeBwOdHzqtMgM0nj7uBQeTuGc/k/zGTzUSlf91eJeQj343MlKNoE9/0HVKPrf3rIXsSicKf3UBmBDZxVz+8srHvx95K9Eon9502XdcRoQ12AdIa4i07eDfJh60vGLZTF9Hn35GC9Q4kfQB67NnhbwVjbfavgQicGnuk7eY0/mH4jp282n45qYdtnzKZSqbdyNSjUsbUAxJrogNPKsB8k89FS47pTbEGenxAzwsYU+4ptQs9+j+sVVsrfDr/sB5tINZQop1b9rNlwLWZkSdEilHJ/AljsG4OtCvrK9FRfX9HW5BUXTQbeLFMugLSIpTSq4makA==
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=seicmu.onmicrosoft.com; s=selector1-seicmu-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=zw23QZHOtPNzT2kmhcVdUGOtIu6BdUA4/i+qEMlFTvk=; b=B5GdR0O7FD6OsvNVbSH4T0pN1QSui+/YNPyVM/Dbn0jocb1b9r+nH+EkSG9rLuyKTrpkAp7W0pV0cinLQS+OPLvo/tzxXXFSZ8WVV7MGBBwH8ENcD4i5Zl+qXzY/69S0RIuuVp3lwLYBFy6O3huXudVBQi1nSIcv6Uf2KlW4blk=
Received: from BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:168::11) by BN2P110MB1544.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:17e::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5061.13; Wed, 23 Mar 2022 12:02:26 +0000
Received: from BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM ([fe80::3525:e765:3ea4:f086]) by BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM ([fe80::3525:e765:3ea4:f086%5]) with mapi id 15.20.5061.024; Wed, 23 Mar 2022 12:02:26 +0000
From: Roman Danyliw <rdd@cert.org>
To: "Kampanakis, Panos" <kpanos@amazon.com>, "saag@ietf.org" <saag@ietf.org>
Thread-Topic: [saag] Re: About the "Draft text for a PQ Maintenance WG"
Thread-Index: AQHYEmpeHPUpowV2TESswMETYZMsdKzNIFQQ
Date: Wed, 23 Mar 2022 12:02:25 +0000
Message-ID: <BN2P110MB1107657E8951BFA1DC129E15DC189@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
References: <66A20135-5437-43E4-9F74-AE1D1FDB3A59@gmail.com> <DM3P110MB053881D653F826CE81524E8BDCF29@dm3p110mb0538.namp110.prod.outlook.com> <02E8D61E-D96B-4520-A781-4EB43014BFB8@gmail.com> <DM3P110MB053869F08FD5E90EF139E564DCF29@dm3p110mb0538.namp110.prod.outlook.com> <b85947cd235d4cfc802f6a3ef4ef5cac@ex13d01anc003.ant.amazon.com> <b22f2d2780844ef8bc422be316eecbdf@ex13d01anc003.ant.amazon.com> <emc6e5db6a-3afb-455b-ab43-6759d1adb936@desktop-8g465ua> <66F981E1-05BB-4B4D-8DE4-006023094F15@akamai.com> <24a7328bd1814769a6f47ae00f682be3@EX13D01ANC003.ant.amazon.com> <BN1P110MB093995115D31A8FD3ECBFC72DCA99@BN1P110MB0939.NAMP110.PROD.OUTLOOK.COM> <SA0PR09MB6524C8D19FE6FC543D420981A9B89@SA0PR09MB6524.namprd09.prod.outlook.com> <16dae1e5137a48079d976bcb93185925@EX13D01ANC003.ant.amazon.com>
In-Reply-To: <16dae1e5137a48079d976bcb93185925@EX13D01ANC003.ant.amazon.com>
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-office365-filtering-correlation-id: 27f51c88-bcb3-4c50-34ec-08da0cc4ff2c
x-ms-traffictypediagnostic: BN2P110MB1544:EE_
x-microsoft-antispam-prvs: <BN2P110MB15447CBA4442D7EB189A3BD5DC189@BN2P110MB1544.NAMP110.PROD.OUTLOOK.COM>
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 68cil3KdbhiPQnd4/Z6ogbSAjrCCM/3nLP3rIMMcSCrzD+dXCypMRtqtrguoMQBcF+nAmW90quwnoRQuIW3rBWHfZBidvuLKlkmHhcazBT4tc50pTCEDE7lGJZWBm5f5JFL2wt4R/AQDC5LFCBz9BfVTZHNpPgNyFUtmdlBOw3pKfn1Zm1iYo0exgzcDI1jRf3PUN/X2XJVm0LG6tnjpKknFBLIVqoU/osrhjIL3FUTtIxxuHc8lQJvv1EKwhUdXan2Zwk/77xFXCXGgy5WOhR3hlGUMzRTgCc2lM+kyneJtFPy74GXQKJDxmuh+6QE1TsRCoUVtBGmHM4aUpMbeQ5ZBdmh3BEOeNh0zFx6se5hpM1v/9WI/7LnPv3DbH2PH3F4wv113Sig4lvqpyUni7Syo4frLmvoCp9t9okqdG6RsDfVTHE7J6oWNfsd5UZMw2nwvwRySGpXCNTUNoGRly4E1oA+/KFKaHCqWMPwiCuZH15xuGb9GAduJynMG+S3cwIYdCLC7xM/iQXFIFF+O5CzCLOOIVeIgSd5cTt1CCIDk2d8Mm7Ecs7L5FQuAr7mleqIQIVuw7vFY8qqtp6k/iC45nQdykfIgVFycXDduSMsxNrJolDlItO8TEJBRcLaaBnAqght6lEK3E3TrkY+Qcy8UvCpWrZS5N2WzOjoNSbRUI/qF+X79fFO0yHYmdyHvNQE2h3Bd1OygIY/MMKUhdQ==
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:(13230001)(366004)(66446008)(82960400001)(66476007)(66556008)(66946007)(64756008)(55016003)(76116006)(4326008)(498600001)(8676002)(122000001)(26005)(186003)(83380400001)(38070700005)(5660300002)(38100700002)(2906002)(8936002)(9686003)(86362001)(7696005)(6506007)(52536014)(53546011)(33656002)(110136005)(40140700001)(966005)(71200400001); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: LSsG6KtXQQS17Cczyxm52mQVxJeLd6MR2pV5QvqLZpUb+WnhUVaVTHcL1RY63nJxqgmX0jefMspzYWIeRlZ9MWaiN+6g/38hdKr+sl6rKOkZRZF9WMjbjrdA62h7UUq3y9tWgmOdLGVtj//6+w5wqg==
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: 27f51c88-bcb3-4c50-34ec-08da0cc4ff2c
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Mar 2022 12:02:25.9932 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 95a9dce2-04f2-4043-995d-1ec3861911c6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN2P110MB1544
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/X6MPk-KXlKWyop_A4isAmD9YVFI>
Subject: Re: [saag] About the "Draft text for a PQ Maintenance WG"
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2022 12:02:37 -0000

Hi Panos!

No updates.  While there is concrete charter text describing the mechanics of how such a hypothetical WG would operate, it doesn't describe what protocols would be in scope for the initial body of work.  Progress is blocked pending identification of such initial milestones (i.e., what protocols need a PQC re-design but don't have an existing WG to address it).

Feedback continues to be welcome on this list (saag@ietf).  I've been trying to keep a running summary of the PQC work in the IETF at https://trac.ietf.org/trac/sec/wiki/PQCAgility.

Regards,
Roman

> -----Original Message-----
> From: Kampanakis, Panos <kpanos@amazon.com>
> Sent: Tuesday, January 25, 2022 11:08 PM
> To: saag@ietf.org
> Cc: Roman Danyliw <rdd@cert.org>; Benjamin Kaduk <kaduk@mit.edu>
> Subject: RE: [saag] Re: About the "Draft text for a PQ Maintenance WG"
> 
> Hi Roman, Ben,
> 
> Just resurrecting this thread from a few months back.
> 
> Do you know if there will be any updates or progress on this new WG by IETF-
> 113?
> 
> Thanks,
> Panos
> 
> 
> -----Original Message-----
> From: saag <saag-bounces@ietf.org> On Behalf Of Sheehe, Charles J. (GRC-
> LCN0)
> Sent: Thursday, October 14, 2021 8:19 AM
> To: saag@ietf.org
> Subject: RE: [EXTERNAL] [saag] [EXTERNAL] Re: About the "Draft text for a PQ
> Maintenance WG"
> 
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you can confirm the sender and know the
> content is safe.
> 
> 
> 
> Hi
> 
> I think the charter looks fine.
> 
> Thanks
> Chuck
> 
> Charles J. Sheehe III
> Computer Engineer
> Secure Networks, System
> Integration and Test Branch (LCN)
> Glenn Research Center
> 21000 Brookpark Rd
> Cleveland, OH 44135
> Charles.J.Sheehe@NASA.GOV Email
> Charles.J.Sheehe@NSS.SGov.Gov SIPRmail
> Office: 216-433-5179
>      It is not the critic who counts; not the man who points out how the strong
> man stumbles, or where the doer of deeds could have done them better.
> 
>     The credit belongs to the man who is actually in the arena, whose face is
> marred by dust and sweat and blood; who strives valiantly; who errs, who
> comes short again and again, because there is no effort without error and
> shortcoming; but who does actually strive to do the deeds; who knows great
> enthusiasms, the great devotions; who spends himself in a worthy cause; who
> at the best knows in the end the triumph of high achievement, and who at the
> worst, if he fails, at least fails while daring greatly, so that his place shall never
> be with those cold and timid souls who neither know victory nor defeat.
> Theodore Roosevelt
> 
> -----Original Message-----
> From: saag <saag-bounces@ietf.org> On Behalf Of Roman Danyliw
> Sent: Wednesday, September 29, 2021 2:23 PM
> To: Kampanakis, Panos <kpanos@amazon.com>; Salz, Rich
> <rsalz=40akamai.com@dmarc.ietf.org>; Benjamin Kaduk <kaduk@mit.edu>;
> saag@ietf.org
> Subject: [EXTERNAL] Re: [saag] About the "Draft text for a PQ Maintenance
> WG"
> 
> Hi!
> 
> 
> 
> We've heard this confusion on using the "maintenance" short hand to
> characterize this potential body of work.  The intent was what Panos described
> - a short hand where the "maintenance" was on existing IETF protocol to allow
> it to benefit from PQC mechanisms.
> 
> 
> 
> The proposed, templated charter language more precisely captures the intent --
> "The [Planned WG Name] working group ([Planned WG Acronym]) is chartered
> as a WG to analyze, adapt or update IETF protocols, registries, and associated
> code points with PQ cryptographic mechanisms."
> (https://github.com/rdanyliw/ietf-pq-maintenance/blob/main/pqm-charter.md
> <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.
> com%2Frdanyliw%2Fietf-pq-maintenance%2Fblob%2Fmain%2Fpqm-
> charter.md&data=04%7C01%7CCharles.J.Sheehe%40nasa.gov%7Cd092f22f99e
> c48fe1a1a08d983764e40%7C7005d45845be48ae8140d43da96dd17b%7C0%7
> C0%7C637685366837666194%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4w
> LjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdat
> a=mJG8R%2FPW8OcWxEdkDGyJ1P0DxvUhWd2XODuf55oYDSM%3D&reserved
> =0> ).  I've removed "PQ maintenance" from the header of the templated
> charter.  It now reads "PQC Agility WG".  The term didn't appear in the charter
> text itself.  However, to eliminate all possible c  onfusion I also the one instance
> of maintenance by s/protocol maintenance/protocol changes/.
> 
> 
> 
> Roman
> 
> 
> 
> From: Kampanakis, Panos <kpanos@amazon.com>
> Sent: Wednesday, September 29, 2021 12:53 PM
> To: Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org>; Roman Danyliw
> <rdd@cert.org>; Benjamin Kaduk <kaduk@mit.edu>; saag@ietf.org
> Subject: RE: [saag] About the "Draft text for a PQ Maintenance WG"
> 
> 
> 
> Maybe maintenance is the wrong word, but the point is to have a WG for
> orphaned (without a WG) protocols like CURDLE was for Curve25519/448.
> 
> 
> 
> From: saag <saag-bounces@ietf.org <mailto:saag-bounces@ietf.org> > On
> Behalf Of Salz, Rich
> Sent: Wednesday, September 29, 2021 12:41 PM
> To: Ludovic Perret <ludovic.perret@cryptonext-security.com
> <mailto:ludovic.perret@cryptonext-security.com> >; Roman Danyliw
> <rdd@cert.org <mailto:rdd@cert.org> >; Benjamin Kaduk <kaduk@mit.edu
> <mailto:kaduk@mit.edu> >; saag@ietf.org <mailto:saag@ietf.org>
> Cc: Kampanakis, Panos <kpanos=40amazon.com@dmarc.ietf.org
> <mailto:kpanos=40amazon.com@dmarc.ietf.org> >
> Subject: RE: [EXTERNAL] [saag] About the "Draft text for a PQ Maintenance
> WG"
> 
> 
> 
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you can confirm the sender and know the
> content is safe.
> 
> 
> 
> I find the concept of post-quantum *maintenance* very strange.
> 
> 
> 
> 
> 
> _______________________________________________
> saag mailing list
> saag@ietf.org
> https://www.ietf.org/mailman/listinfo/saag