Re: [Bug 26123] New: Key ID definition should be aligned with JWK kid definition from Ryan Sleevi on 2014-06-17 (public-webcrypto@w3.org from June 2014)

From: Ryan Sleevi <sleevi@google.com>
Date: Tue, 17 Jun 2014 15:27:55 -0700
To: bugzilla@jessica.w3.org
Cc: public-webcrypto@w3.org, Mike Jones <Michael.Jones@microsoft.com>
Message-ID: <CACvaWvZ8qtr88W8b+GjzuAidHf+tyb_rMhSyqzGND7ZRvvvaUA@mail.gmail.com>

Mike,

Can you explain why they should be aligned?

Named Key and kid have no relationship. Deserializing a JWK with a kid does
not yield a NamedKey, and serializing a NamedKey doesn't result in a JWK
with kid set.

Further, their use of id concepts are for separate purposes.

While I have little personal interest in NamedKey, this seems like an
unnecessary/unwarranted change.

If kid is going to be handled, you'd do it at the application layer - named
key or not - and it would not work with wrap/unwrap.

Note that CryptoKey (not NamedKey) are equally not meant to be 1:1
relationships with JWK. They are independent.

Received on Tuesday, 17 June 2014 22:28:23 UTC