Re: [COSE] JOSE & COSE: Registered Curves & Hybrids

Ilari Liusvaara <ilariliusvaara@welho.com> Thu, 28 March 2024 18:57 UTC

Return-Path: <ilariliusvaara@welho.com>
X-Original-To: cose@ietfa.amsl.com
Delivered-To: cose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65691C15106B; Thu, 28 Mar 2024 11:57:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 UcVOdFiXQZis; Thu, 28 Mar 2024 11:57:44 -0700 (PDT)
Received: from welho-filter1.welho.com (welho-filter1b.welho.com [83.102.41.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12E19C14F70E; Thu, 28 Mar 2024 11:57:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by welho-filter1.welho.com (Postfix) with ESMTP id BF674216C5; Thu, 28 Mar 2024 20:57:40 +0200 (EET)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp2.welho.com ([IPv6:::ffff:83.102.41.85]) by localhost (welho-filter1.welho.com [::ffff:83.102.41.23]) (amavisd-new, port 10024) with ESMTP id Eg0-DEIV5Pen; Thu, 28 Mar 2024 20:57:39 +0200 (EET)
Received: from LK-Perkele-VII2 (78-27-96-203.bb.dnainternet.fi [78.27.96.203]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by welho-smtp2.welho.com (Postfix) with ESMTPSA id AB03328C; Thu, 28 Mar 2024 20:57:37 +0200 (EET)
Date: Thu, 28 Mar 2024 20:57:37 +0200
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: JOSE WG <jose@ietf.org>, cose <cose@ietf.org>
Message-ID: <ZgW9oWerS3WTAxQ7@LK-Perkele-VII2.locald>
References: <CAN8C-_+exTjcuxrq2r7FYzTL2-wktv44DPzSg+fkcBag6F=24g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <CAN8C-_+exTjcuxrq2r7FYzTL2-wktv44DPzSg+fkcBag6F=24g@mail.gmail.com>
Sender: ilariliusvaara@welho.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/_Ggma3kKlfIjJHV45XGHSNHXom4>
Subject: Re: [COSE] JOSE & COSE: Registered Curves & Hybrids
X-BeenThere: cose@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: CBOR Object Signing and Encryption <cose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cose>, <mailto:cose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cose/>
List-Post: <mailto:cose@ietf.org>
List-Help: <mailto:cose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cose>, <mailto:cose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Mar 2024 18:57:49 -0000

On Thu, Mar 28, 2024 at 09:11:52AM -0700, Orie Steele wrote:
> See:
> 
> https://mailarchive.ietf.org/arch/msg/tls/QU1kpJdGNPsIFbjTG2KlDLMdcPk/
> 
> We've got similar issues in JOSE and COSE registries.
> 
> I wonder if we ought to consider similar changes to:
> 
> https://www.iana.org/assignments/jose/jose.xhtml#web-key-elliptic-curve
> https://www.iana.org/assignments/cose/cose.xhtml#elliptic-curves
> 
> This issue has come up already in several discussions regarding ML-DSA,
> SLH-DSA, FN-DSA, ML-KEM and hybrids.

As far as I remember, this issue does not come up with how *-DSA is
currently defined, but prehash could change things (unless we just
decide that prehash variants are not supported, like with Ed25519/
Ed448).

It does come up with ML-KEM and anything hybridizing it, since KEMs
are always multi-algorithm. Even just DKA vs KAwKW always gives at least
two algorithms.


> Because JOSE and COSE tend to separate algorithms from keys, we've not seen
> the equivalent of curves created for lattices or hashes or hybrids.

As I see it, the issue is that OKP can throw who knows what into
"elliptic curve" space. EC/EC2 is nicely behaved, those are always
elliptic curves.

Then I note that COSE 1/-1 is described as "EC identifier -- Taken from
the 'COSE Elliptic Curves' registry", which is less than great.

Radical way would be to split the registries (and move the CFRG stuff
to the new registry).


> I personally think this is a good thing, since fully specified algorithms
> attached to a key representation is better than looking at kty -> crv ->
> P-256 and then just trying ES256 or ECDH-ES+A128KW.

I don't see what this has to do with fully-specified algorithms.
Especially for things like P-256, that truly are elliptic curves.

 
> If we don't plan to create new registries for PQC related things, should we
> say anything about future expectations on this?
>
> Or just let curves be the last such registry and rely on tribal knowledge?

I don't see any need to create any new registry for PQC stuff. There
is no PQC stuff yet, but there would be 4 entries for the new registry.

And as far as I see, the track record with tribal knowledge (e.g., about
actual meaning of "crv" in OKP[1] or "kty"[2]) is not exactly great.


[1] "Read the correct mailing list thread and you'll get it right."
[2] Listen the correct comment in session video recording and you'll
    get it right.




-Ilari