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

Mike Prorock <mprorock@mesur.io> Fri, 25 March 2022 13:07 UTC

Return-Path: <mprorock@mesur.io>
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 DFDFA3A1138 for <saag@ietfa.amsl.com>; Fri, 25 Mar 2022 06:07:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.908
X-Spam-Level:
X-Spam-Status: No, score=-6.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=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 (2048-bit key) header.d=mesur-io.20210112.gappssmtp.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 PVlbjmwb8O2W for <saag@ietfa.amsl.com>; Fri, 25 Mar 2022 06:07:14 -0700 (PDT)
Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A2DF3A0B72 for <saag@ietf.org>; Fri, 25 Mar 2022 06:07:14 -0700 (PDT)
Received: by mail-vs1-xe34.google.com with SMTP id k15so5948014vsr.11 for <saag@ietf.org>; Fri, 25 Mar 2022 06:07:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mesur-io.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SMRJiXKuxl2UyN1Fldadkvw0xMl955QaWjfSItpDPUY=; b=b10pnFRVS+6OsV9HUopO0Cir+yAxKC2PDuW00+cx7MKXl0Liitf/klHjXx0IDwIw/V 3aMbGTCjU/OIOVU2WGFQKle5qF/kawEBYFHGzLD3/lwhGvXNCBFduQmv+ZJf4He9U3Nk LEh5c8rPYA7BpYrEqR1ctlzL9VHFVls+ZH/fGX6O68yTZgXjPRZKuTqKGffj2sUwHXNX 1G/6ONYRWwzyXgStMCUjeC5ljvlp9nDCiF5bt1Zh0vmyV978JxDP0Ndq1pw8wRjV+1Qq n4A6xq2vuWZnze4drM2Mc0W7C0U0rXYr1QKSTONsreg7MPKk9ZmgUuTmdUzci3o1kPzx +4qA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SMRJiXKuxl2UyN1Fldadkvw0xMl955QaWjfSItpDPUY=; b=tJdHQ23lK3skRVmhHnVL4BIKvCGltnwCV8yEFuaIWyonr6xvwzHA7RdQnSNVFbYM9P P011XyIfZbrdeejJiB+DddMvOQuzyYWWsMyjIfxgB0bHSpkq/aImwpds0+5N5B8mUn+u G1BfkkewmOOsgILuKzoGAIbqXZDhQFfH8B101v5kakfXnoF+lUjPdj12VZaioVEd+jep Bu1sDXXyM7lK16LUzNc60fmDzj+2X2uRRV7e6cfUwn8HFtG2uvl7eaiiisH27FOsHNi7 NCvP0q5RB681gms42/lrfGPWQemsoFY4V6kd7eEB5WEzEGAZT5LMDqTLw1TG4RA5zrK5 J7UQ==
X-Gm-Message-State: AOAM531p6QzCENU7w7ADe+5yJQT8x9vXdYfA1JUtw+Lp2Y2laJR696RX cPM7MlYXf9TBmIgaviVyILQRIXzugU4o1EFXkVBT4PF68EKH
X-Google-Smtp-Source: ABdhPJz0iND2ILnYIqo23b8VnWLiQuUYtkIOfjxsttlR/0v3IMJzqyWN5oBDvGHVbZ4g1p+plqfp6wPl8oJN9Smzp/s=
X-Received: by 2002:a05:6102:c52:b0:322:82fd:1926 with SMTP id y18-20020a0561020c5200b0032282fd1926mr5083609vss.80.1648213632073; Fri, 25 Mar 2022 06:07:12 -0700 (PDT)
MIME-Version: 1.0
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>
From: Mike Prorock <mprorock@mesur.io>
Date: Fri, 25 Mar 2022 09:07:01 -0400
Message-ID: <CAGJKSNSyOnW+ziEB0XZ5q50DntEgGa6WV8yiVC7dHO2T72czgg@mail.gmail.com>
To: Roman Danyliw <rdd@cert.org>
Cc: "Kampanakis, Panos" <kpanos@amazon.com>, "saag@ietf.org" <saag@ietf.org>, Orie <orie@transmute.industries>
Content-Type: multipart/alternative; boundary="0000000000000dd5d205db0aa432"
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/uPd_Tz8oVY5jRo8yKKJ0_Lpl7sA>
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: Fri, 25 Mar 2022 13:07:20 -0000

Two items moving forward on this area that I am aware of are:
https://www.ietf.org/id/draft-uni-qsckeys-00.html
and
https://www.ietf.org/id/draft-prorock-cose-post-quantum-signatures-00.html

As I am working directly on the latter - I can note that we have been
receiving good engagement on the topic in the COSE WG, but due to the
current stage of NIST review we could see some slowdowns as a result.

Mike Prorock
CTO, Founder
https://mesur.io/



On Wed, Mar 23, 2022 at 8:03 AM Roman Danyliw <rdd@cert.org> wrote:

> 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
>
> _______________________________________________
> saag mailing list
> saag@ietf.org
> https://www.ietf.org/mailman/listinfo/saag
>