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

"Kampanakis, Panos" <kpanos@amazon.com> Wed, 26 January 2022 04:08 UTC

Return-Path: <prvs=018a68fdd=kpanos@amazon.com>
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 351573A2072 for <saag@ietfa.amsl.com>; Tue, 25 Jan 2022 20:08:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.172
X-Spam-Level:
X-Spam-Status: No, score=-10.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.576, 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazon.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 67ardtj73Nam for <saag@ietfa.amsl.com>; Tue, 25 Jan 2022 20:08:11 -0800 (PST)
Received: from smtp-fw-9102.amazon.com (smtp-fw-9102.amazon.com [207.171.184.29]) (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 613083A2070 for <saag@ietf.org>; Tue, 25 Jan 2022 20:08:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1643170091; x=1674706091; h=from:to:cc:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=4huqVvumLOCzMi/44m+N53An8CGguuMTF/KVpnV43Jc=; b=it/7OhdsGaiDvWIux9GVTozaTtoagM32XjFRYaJu+eGT/gOPjLu4GALn hl6x+V8NRIfcJ9Lbv6AK9XMElO0GyjMwljYM+G6FRZLU69Hu40Xnaf8vU lf5c5GfTVQLJ5KJxhDXrkQ6H2K3bQ0m9A16p3L9LrqEyj4TC9rM5AaVbt 0=;
X-IronPort-AV: E=Sophos;i="5.88,316,1635206400"; d="scan'208";a="189957048"
Thread-Topic: [saag] Re: About the "Draft text for a PQ Maintenance WG"
Received: from pdx4-co-svc-p1-lb2-vlan3.amazon.com (HELO email-inbound-relay-iad-1a-8691d7ea.us-east-1.amazon.com) ([10.25.36.214]) by smtp-border-fw-9102.sea19.amazon.com with ESMTP; 26 Jan 2022 04:07:55 +0000
Received: from EX13MTAUWB001.ant.amazon.com (iad12-ws-svc-p26-lb9-vlan2.iad.amazon.com [10.40.163.34]) by email-inbound-relay-iad-1a-8691d7ea.us-east-1.amazon.com (Postfix) with ESMTPS id AB897C0858; Wed, 26 Jan 2022 04:07:54 +0000 (UTC)
Received: from EX13D01ANC002.ant.amazon.com (10.43.157.162) by EX13MTAUWB001.ant.amazon.com (10.43.161.249) with Microsoft SMTP Server (TLS) id 15.0.1497.28; Wed, 26 Jan 2022 04:07:53 +0000
Received: from EX13D01ANC003.ant.amazon.com (10.43.157.68) by EX13D01ANC002.ant.amazon.com (10.43.157.162) with Microsoft SMTP Server (TLS) id 15.0.1497.28; Wed, 26 Jan 2022 04:07:52 +0000
Received: from EX13D01ANC003.ant.amazon.com ([10.43.157.68]) by EX13D01ANC003.ant.amazon.com ([10.43.157.68]) with mapi id 15.00.1497.028; Wed, 26 Jan 2022 04:07:52 +0000
From: "Kampanakis, Panos" <kpanos@amazon.com>
To: "saag@ietf.org" <saag@ietf.org>
Thread-Index: AQHXwPXf2jpbTzyDl0SdoYdNJz+2Fax1Ug9A
Date: Wed, 26 Jan 2022 04:07:52 +0000
Message-ID: <16dae1e5137a48079d976bcb93185925@EX13D01ANC003.ant.amazon.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>
In-Reply-To: <SA0PR09MB6524C8D19FE6FC543D420981A9B89@SA0PR09MB6524.namprd09.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.43.157.202]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/wQ5aAzKvmXt3n8oOet3wDelbN-Q>
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, 26 Jan 2022 04:08:16 -0000

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%7Cd092f22f99ec48fe1a1a08d983764e40%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637685366837666194%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=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