Re: [Suit] NIST selected PQM algorithms

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 09 July 2022 20:14 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: suit@ietfa.amsl.com
Delivered-To: suit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65462C15949B for <suit@ietfa.amsl.com>; Sat, 9 Jul 2022 13:14:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.706
X-Spam-Level:
X-Spam-Status: No, score=-1.706 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=sandelman.ca
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 eQDR9_GqRBhJ for <suit@ietfa.amsl.com>; Sat, 9 Jul 2022 13:14:40 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49B81C14F73B for <suit@ietf.org>; Sat, 9 Jul 2022 13:14:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 4144138C58; Sat, 9 Jul 2022 16:31:53 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id nFbFsgqFbmcU; Sat, 9 Jul 2022 16:31:49 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 70A3C389CA; Sat, 9 Jul 2022 16:31:49 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1657398709; bh=+alL40ZPKolfyTJLDpwiMN0GxN7OV8GfZNYTpCeaZqc=; h=From:To:Subject:In-Reply-To:References:Date:From; b=rVixdP3sVFhmxT2FW9ioEtqLM3mfvcBz2UnPMWXMuQiYteOn5ODy9vkcAAgLrW2QH akeSmdI05PAlvhTJ5mWmHD8hwZCUQ9bBDE3FetLG3OYgZEi2Xsl8i86K7QcjTW1LsZ /1shMK750MkTDAarU1Awkdmd9nuGonSKYl2hjpE7MNigZ0pWRzA5WBQuD1VQn1FbN4 6msCURJxw4PZ15h+9XNxKXdLZrKsP9070aPH6b5rpbLNiYTKgiNbQMaL8tIrqZilao vh7Dyqk/Vyhr7HAWSqmEZo28mg8/+QWvJaG1YHktBp7CC2ikqtI3AmcN7/bKGbTFlf M5TFODZ/HvX9A==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 75A0ADF6; Sat, 9 Jul 2022 16:14:34 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Russ Housley <housley@vigilsec.com>, Koen Zandberg <koen.zandberg@inria.fr>, suit@ietf.org
In-Reply-To: <9EBE36DB-4E12-4849-ABA1-538330A778B2@vigilsec.com>
References: <5ccdaef9-1e28-9d4e-8ab5-28179454b09f@inria.fr> <9EBE36DB-4E12-4849-ABA1-538330A778B2@vigilsec.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sat, 09 Jul 2022 16:14:34 -0400
Message-ID: <12898.1657397674@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/dQrmEDOn9UZVCAcYzQAyaaXJhL4>
Subject: Re: [Suit] NIST selected PQM algorithms
X-BeenThere: suit@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Software Updates for Internet of Things <suit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/suit>, <mailto:suit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/suit/>
List-Post: <mailto:suit@ietf.org>
List-Help: <mailto:suit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/suit>, <mailto:suit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jul 2022 20:14:44 -0000

Russ Housley <housley@vigilsec.com> wrote:
    > I think SUIT needs to look at SPHINCS+ as an alternative to HSS/LMS for
    > the hash-based signature algorithm, but the NIST standard for SPHINCS+
    > will probably not be available for a year.

please expand: "not be available"

Is it the same, in IETF terms as, "will not have passed AUTH48", or
does it mean, "will not have passed WGLC"?

I guess what I am asking is: will there be bits-on-the-wire changes?

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide