- From: <bugzilla@jessica.w3.org>
- Date: Wed, 16 Jul 2014 03:56:18 +0000
- To: public-webcrypto@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26348 --- Comment #1 from Ryan Sleevi <sleevi@google.com> --- >From the point of view of a "JOSE" JWK, I don't think this is a good idea. JOSE intentionally doesn't provide PBKDF2 as a valid kty; the key algorithm is only used with the CEK, and associated by alg, not kty. Additionally, rather than store the security parameters on the JWK, they're part of the JWE's header parameters. It's not "unnecessarily restrictive", it's "not defined because it's undefined for JWK". If you feel strongly about this, then I think you'll need to propose text to the WG for adoption. It certainly seems like it involves new registrations with JWA. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Wednesday, 16 July 2014 03:56:19 UTC