- From: Mike Jones <Michael.Jones@microsoft.com>
- Date: Mon, 13 Aug 2012 21:01:45 +0000
- To: Harry Halpin <hhalpin@w3.org>
- CC: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
- Message-ID: <4E1F6AAD24975D4BA5B168042967394366773D30@TK5EX14MBXC283.redmond.corp.microsoft.>
I intend to discuss this with the JOSE WG once I'm back from vacation tomorrow. Best wishes, -- Mike ________________________________ From: Harry Halpin Sent: 8/6/2012 3:56 PM To: Mike Jones Cc: public-webcrypto@w3.org Subject: JOSE WG request Mike, The Web Cryptography Working group has noted that the API requires some access to raw key material, and the issue of whether or not to use JWK or ASN.1 as the default format came up. Two issues have come out that we'd like to know the answer to: 1) JWK does not define a private key format. Does the JOSE WG plan to support a JOSE-format for private keys? If so, when? 2) While we'd like encourage the use of JOSE over ASN.1, it seems like for backwards compatibility having some level of ASN.1 support would be useful and we *need* a format that allows key material (both private and public) to be exported. Folks seem to leaning towards ASN.1 as a default format in the low-level API, and having JWK as a format that can be built on top of that in a possible high-level API. Would that be OK? 3) How stable do you believe the JOSE formats are right now? Do you think they are stable enough now we can reference them in our API draft? If not, when? Feel free to forward this by JOSE WG, or just answer from your personal knowledge. cheers, harry
Received on Monday, 13 August 2012 21:02:37 UTC