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

"Kampanakis, Panos" <kpanos@amazon.com> Sat, 26 March 2022 03:37 UTC

Return-Path: <prvs=0775f2578=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 3631A3A0E77 for <saag@ietfa.amsl.com>; Fri, 25 Mar 2022 20:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.608
X-Spam-Level:
X-Spam-Status: No, score=-9.608 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 34Pj6GIuDAfU for <saag@ietfa.amsl.com>; Fri, 25 Mar 2022 20:37:04 -0700 (PDT)
Received: from smtp-fw-33001.amazon.com (smtp-fw-33001.amazon.com [207.171.190.10]) (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 4725F3A0E8F for <saag@ietf.org>; Fri, 25 Mar 2022 20:37:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1648265825; x=1679801825; h=from:to:cc:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=XcD1y7dEaq1Vw0peNNyf4QGSCsOokrq11zB1kHcZfKk=; b=syA7peat89C8nf/lhFAIMT3UxeeKqTFjTtU/Fl0ovgqyk7DIJy0F9Bni qKUSRGbvwjp9rg7+Z+ipO+MV3xhG966xiDq32zcUZ5MnrAIInSdUMOtGr LuKZatskAYXlwB2/5RW0o2YCKL/7UP9aa/+DsvrZBNICZ8k+5WDjOdUEc Q=;
X-IronPort-AV: E=Sophos;i="5.90,211,1643673600"; d="scan'208";a="184527334"
Thread-Topic: [saag] Re: About the "Draft text for a PQ Maintenance WG"
Received: from iad12-co-svc-p1-lb1-vlan2.amazon.com (HELO email-inbound-relay-pdx-2a-2dbf0206.us-west-2.amazon.com) ([10.43.8.2]) by smtp-border-fw-33001.sea14.amazon.com with ESMTP; 26 Mar 2022 03:37:03 +0000
Received: from EX13MTAUWB001.ant.amazon.com (pdx1-ws-svc-p6-lb9-vlan2.pdx.amazon.com [10.236.137.194]) by email-inbound-relay-pdx-2a-2dbf0206.us-west-2.amazon.com (Postfix) with ESMTPS id DE10EA2829; Sat, 26 Mar 2022 03:37:01 +0000 (UTC)
Received: from EX13D01ANC001.ant.amazon.com (10.43.157.154) by EX13MTAUWB001.ant.amazon.com (10.43.161.249) with Microsoft SMTP Server (TLS) id 15.0.1497.32; Sat, 26 Mar 2022 03:37:00 +0000
Received: from EX13D01ANC003.ant.amazon.com (10.43.157.68) by EX13D01ANC001.ant.amazon.com (10.43.157.154) with Microsoft SMTP Server (TLS) id 15.0.1497.32; Sat, 26 Mar 2022 03:36:59 +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.033; Sat, 26 Mar 2022 03:36:59 +0000
From: "Kampanakis, Panos" <kpanos@amazon.com>
To: Roman Danyliw <rdd@cert.org>, "saag@ietf.org" <saag@ietf.org>
Thread-Index: AQHYPq39VvAL5YSDoU2i6d3O5RK6V6zRBjhQ
Date: Sat, 26 Mar 2022 03:36:59 +0000
Message-ID: <ad2f1e4cd3f04dd4aa48faa9426cce52@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> <16dae1e5137a48079d976bcb93185925@EX13D01ANC003.ant.amazon.com> <BN2P110MB1107657E8951BFA1DC129E15DC189@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
In-Reply-To: <BN2P110MB1107657E8951BFA1DC129E15DC189@BN2P110MB1107.NAMP110.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.156.80]
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/eKn_Rr4gkDFgFyqe8OjO0ehEVpA>
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: Sat, 26 Mar 2022 03:37:10 -0000

Thanks for the update Roman.

FWIW, I will repeat that imo the new WG's charter should include SSH initially. CURDLE ended up focusing on SSH as well. If participants want to focus on more orphaned protocols for PQ migration then we could add DNSSEC, JSON Signatures, Kerberos or more. CURDLE initially wanted to focus one some of those as well, but it ended up working only on SSH. So, the new WG could start small and update the charter as necessary. SSH is a good chunk of work in itself. 

Please note that NIST Round 3 will pick its first KEM in the next couple of weeks and it would benefit the community to bring PQ-hybrid and auth to SSH like other WGs are doing for IKEv2 and (D)TLS already.

Rgs,
Panos


-----Original Message-----
From: Roman Danyliw <rdd@cert.org> 
Sent: Wednesday, March 23, 2022 8:02 AM
To: Kampanakis, Panos <kpanos@amazon.com>om>; saag@ietf.org
Cc: Benjamin Kaduk <kaduk@mit.edu>
Subject: RE: [EXTERNAL] [saag] 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 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>rg>; 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>om>; Salz, Rich 
> <rsalz=40akamai.com@dmarc.ietf.org>rg>; Benjamin Kaduk <kaduk@mit.edu>du>; 
> 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>rg>; Roman Danyliw 
> <rdd@cert.org>rg>; Benjamin Kaduk <kaduk@mit.edu>du>; 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