- From: Harry Halpin <hhalpin@w3.org>
- Date: Mon, 1 Aug 2016 20:49:47 +0200
- To: Ryan Sleevi <sleevi@google.com>
- Cc: Charles Engelke <w3c@engelke.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>
Received on Monday, 1 August 2016 18:49:59 UTC
On 08/01/2016 08:33 PM, Ryan Sleevi wrote: > > > On Mon, Aug 1, 2016 at 11:20 AM, Harry Halpin <hhalpin@w3.org > <mailto:hhalpin@w3.org>> wrote: > > Note that pkcs8 and spki support will remain in the spec, but it > will just be explicitly marked as non-normative, so I don't think > this is a problem. Taking them out will be difficult, and some > developers rely on them for legacy reasons so not having them in > the spec may confuse developers, but we should clearly recommend > JWKs for future WebApps. So I think I agree with your general > analysis! > > Harry, > > I don't think "we should clearly recommend JWKs for future WebApps" is > necessarily a good thing. So let's be careful when making such claims. > JWK equally has interoperability issues, like ASN.1, but you don't > seem to be proposing to move that to non-normative. > What would you recommend as normative in terms of key formats? Just raw keys?
Received on Monday, 1 August 2016 18:49:59 UTC