Re: [Pqc] [Ext] Mapping the state of PQC and IETF
Behcet Sarikaya <sarikaya2012@gmail.com> Mon, 27 February 2023 16:53 UTC
Return-Path: <sarikaya2012@gmail.com>
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 066A6C14CE45 for <pqc@ietfa.amsl.com>; Mon, 27 Feb 2023 08:53:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.843
X-Spam-Level:
X-Spam-Status: No, score=-1.843 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 DLg6i5m0znUT for <pqc@ietfa.amsl.com>; Mon, 27 Feb 2023 08:53:05 -0800 (PST)
Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3D78C151B07 for <pqc@ietf.org>; Mon, 27 Feb 2023 08:52:46 -0800 (PST)
Received: by mail-vs1-xe2c.google.com with SMTP id m10so12131378vso.4 for <pqc@ietf.org>; Mon, 27 Feb 2023 08:52:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1677516765; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=KA2kIshaYzNAfXoJ5mMO5qBGUw66dZ9bHgZ6Me/33dc=; b=KvLDLxdZiBq3xZPK0QR3GJYv7LzCCuwy/m/lNZzrB+TprBWKtC77cR8sglzzee3Fye a37Vf9fzVlQ5afaLR5eza+NPIJr0XU1t0r5Rxye5YPgRDEqNxWCDEc0ihQm+f0/0lGmV sBVNw/EFrbaU5QlnS2eVUo+nJ8thBmo1bt5vewKfUl3oJpJqtPwfSeBrQcEsJo4r5GQP fbxqpd2iqwdlLeVoaJj9Kz1v39RuHKYhUIpnXXtqctjOaBz8GLU+JuRLKr2VEqz9/JuT +zpadCKUpLLoKRwwFpBLKg6q1K9vzKKkibf3WGKvleOrUTtQYf3WdgRPyFN6mspxYpRv ArcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677516765; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=KA2kIshaYzNAfXoJ5mMO5qBGUw66dZ9bHgZ6Me/33dc=; b=F1qayQyQCH3KcYgL0o+a2DI0GcxQkhDFqh2z4fl/cDH5sY1YRrNql99yrcgVx4/SiY g1cjL9j6amRSNJugsaMDKk9mjAjrqhN3DwiSf6ROFmlvgZnXiwKSgtaz2Av6lQ7hH7nw O2ikwwLBe+RyD59mYqn4Bq+xuHIZaB1TfK4wmnCloGnonWvyOm7UNJaXlOQCzjdvMnIr c+pPW5KyK/BB7RgH50GOuRSPQ0Ef0wqRG7Hf8EveoxMhzI7jqPrTLxpctwhxGbKweZc2 iS7ZKGteAXuCIocnWDmhAUgR+zcVxdeTejKR2AzX1UQ/7z7PGfrfKq621MQmBQ4z8suA EWgg==
X-Gm-Message-State: AO0yUKVckr2weWGF/9TQo5iQ8YOx6ek1wiVe9j7zDTHnKsHvh10Hmsgm YpHaQCNv5TOJIR/wC9BUczMnmziSt4JxHHRLIdBesqbC8/c=
X-Google-Smtp-Source: AK7set+ZDCcBg8pr5vSNqMlRbYLs6HkW9x3ETHb5V4/nS5PHfnFJGP6Bf5PmxXrvm8cIOTkpj/s/lFBG3jHkNwMULbA=
X-Received: by 2002:a05:6102:ed0:b0:412:5424:e58e with SMTP id m16-20020a0561020ed000b004125424e58emr213038vst.0.1677516765641; Mon, 27 Feb 2023 08:52:45 -0800 (PST)
MIME-Version: 1.0
References: <667bd090-1a3e-82d0-f663-8950fcd6dd38@riseup.net> <16A23C37-93BD-4F72-BCF9-3E3C689A0591@icann.org> <6db90caa-44de-c1e6-4676-7ed1a2943503@gmail.com>
In-Reply-To: <6db90caa-44de-c1e6-4676-7ed1a2943503@gmail.com>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Mon, 27 Feb 2023 10:52:34 -0600
Message-ID: <CAC8QAcdFjKCVgKc0V=e89VJ3DuJbVLJTFRZWj1dpm2VyBw_bQg@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: pqc@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ebc06205f5b14e70"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pqc/kyWtLKrDSc8nUCzLYT5fWho0jXY>
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 16:53:09 -0000
On Mon, Feb 27, 2023 at 10:27 AM Alexandre Petrescu < alexandre.petrescu@gmail.com> wrote: > > > Le 27/02/2023 à 16:58, Paul Hoffman a écrit : > > 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! > > Thanks for the list of drafts and RFC about PQC at IETF - impressive, > already 19 documents. > > I am not a crypto expert, sorry if I say naive things. > > One question that comes up in some discussions in other IETF groups is > related to the need (or no need) to upgrade to quantum resistance some > IETF methods that generate parts of an IP address. > > For example, RFC3972 'CGAs' (crypto generated addresses) uses a lengthy > algorithm involving SHA-1; this RFC is then further used by LISP RFC, > among others. > > Would there be any risk in LISP using these CGAs, and thus would there > be a need to migrate to quantum-resistant algorithms? > > The same kind of question applies to other RFCs for other protocols such > as the return routability tests for MIP6, and others, perhaps HIP. > > I am also wondering about the use of algorithms such as MD5 or SHAx to > generate random - probably unique - numbers (e.g. ULA generation method > in RFC4193). Would they be at risk in that randomness (risk of > duplicates), currently, or not. Would they need to be migrated to > quantum resistance; would these new algos be better at generating > uniqueness? > > This question of need - is there any need of quantum-resistance in this > or that particular context - is very important in many places. Without > more definite agreements there would be no migration in the immediate. > > It might that there is no currently perceived need, but would rather > need to move to quantum resistance because all others do, if one wants > to stay interoperable. > > It might be that there is no currently perceived need, and one should > not move to quantum resistance currently because that involves too much > energy and compute consumption. > > +1 Thanks Alex for nicely summing up our discussions on this issue and looking forward PQC expert opinion. Behcet > Alex > > > > > --Paul Hoffman > > > > -- > Pqc mailing list > Pqc@ietf.org > https://www.ietf.org/mailman/listinfo/pqc >
- [Pqc] Mapping the state of PQC and IETF Sofía Celi
- Re: [Pqc] [Ext] Mapping the state of PQC and IETF Paul Hoffman
- Re: [Pqc] [Ext] Mapping the state of PQC and IETF Alexandre Petrescu
- Re: [Pqc] [Ext] Mapping the state of PQC and IETF Behcet Sarikaya
- Re: [Pqc] Mapping the state of PQC and IETF Rebecca Guthrie
- Re: [Pqc] [Ext] Mapping the state of PQC and IETF Paul Hoffman
- Re: [Pqc] Mapping the state of PQC and IETF John Gray
- Re: [Pqc] [EXTERNAL] Mapping the state of PQC and… Mike Ounsworth
- Re: [Pqc] [EXTERNAL] Mapping the state of PQC and… Mike Ounsworth
- Re: [Pqc] [Ext] [EXTERNAL] Mapping the state of P… Paul Hoffman
- Re: [Pqc] [EXTERNAL] Mapping the state of PQC and… Hannes Tschofenig
- Re: [Pqc] Mapping the state of PQC and IETF Kampanakis, Panos
- Re: [Pqc] Mapping the state of PQC and IETF Hannes Tschofenig
- Re: [Pqc] [EXTERNAL] Mapping the state of PQC and… Alexandre Petrescu
- Re: [Pqc] Mapping the state of PQC and IETF - ssh Kampanakis, Panos
- Re: [Pqc] Mapping the state of PQC and IETF - ssh Bas Westerbaan
- Re: [Pqc] Mapping the state of PQC and IETF - ssh Kampanakis, Panos
- Re: [Pqc] Mapping the state of PQC and IETF - ssh Behcet Sarikaya
- Re: [Pqc] Mapping the state of PQC and IETF - ssh Bas Westerbaan
- Re: [Pqc] Mapping the state of PQC and IETF Sofía Celi
- Re: [Pqc] [Ext] [EXTERNAL] Mapping the state of P… Sofía Celi
- Re: [Pqc] Mapping the state of PQC and IETF Sofía Celi
- Re: [Pqc] [Ext] [EXTERNAL] Mapping the state of P… Mike Ounsworth
- Re: [Pqc] Mapping the state of PQC and IETF - ssh D. J. Bernstein
- Re: [Pqc] Mapping the state of PQC and IETF - ssh Eric Rescorla
- Re: [Pqc] Mapping the state of PQC and IETF - ssh Alexandre Petrescu
- Re: [Pqc] Mapping the state of PQC and IETF - ssh D. J. Bernstein
- Re: [Pqc] Mapping the state of PQC and IETF - ssh Alexandre Petrescu
- Re: [Pqc] Mapping the state of PQC and IETF - ssh D. J. Bernstein
- Re: [Pqc] Mapping the state of PQC and IETF - ssh Blumenthal, Uri - 0553 - MITLL
- Re: [Pqc] Mapping the state of PQC and IETF - ssh Alexandre Petrescu
- Re: [Pqc] Mapping the state of PQC and IETF - ssh Thom Wiggers
- Re: [Pqc] Mapping the state of PQC and IETF - ssh Alexandre Petrescu
- Re: [Pqc] Mapping the state of PQC and IETF - ssh Thom Wiggers
- Re: [Pqc] Mapping the state of PQC and IETF - ssh Behcet Sarikaya
- Re: [Pqc] Mapping the state of PQC and IETF - ssh Alexandre Petrescu