Orie, you wrote "In JOSE can we use pub and priv instead of x and d?". That's
fine by me.
And you wrote "We need to assign a number to public and private components."
You could either follow OKP and use -2 and -4 or choose values you like better,
such as -1 and -2. It's up to you. It's all key-type specific.
-- Mike
-----Original Message-----
From: COSE <[email protected]> On Behalf Of Ilari Liusvaara
Sent: Monday, October 23, 2023 12:43 AM
To: cose <[email protected]>
Subject: Re: [COSE] Updates on Dilithium for JOSE and COSE
On Sun, Oct 22, 2023 at 08:39:04PM -0500, Orie Steele wrote:
> Sorry I meant reuse -1 for pub.
>
> In JOSE can we use pub and priv instead of x and d?
>
> I don't understand what the convention is for choosing integer value
> for COSE Key.
>
> it seems like each kty value, can decide how to map each key parameter...
>
> But this means that key type parameters are not globally unique, and
> -4 could be mapped to "pub" for some future key type 7 or 8...
Right. Note that the registry entries are on tuple (kty, param), not on param
itself. Similar thing is also in case with JOSE.
(I still got a "are you sure?" mail from IANA...)
> It seems like it would have been logical for each new key type, to
> just start counting from -1 down, for each new parameter required
>
> But instead EC2 and OKP share -2 as x, -4 as d...
>
> -1 is crv for EC2, but -1 is pub for LMS.
>
> So which convention should we use to select the integer for kty: 7?
I think currently the only one that skips a number is OKP (which skips -3).
And note that -3 is public parameter for EC2, but private parameter for RSA.
> We need to assign a number to public and private components.
>
> -1 and -2?
>
> Or
>
> -2 and -4?
>
> Seems like -1 for pub and -2 for priv is the way to go for 1:7.
Right (I don't like the name for 1:7, but that is a different matter).
-Ilari
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
