- From: Harry Halpin <hhalpin@w3.org>
- Date: Mon, 1 Aug 2016 12:50:25 +0200
- To: public-webcrypto@w3.org
Since there's been no objections on the list or github and two weeks
have passed - also with no news from Ryan Hurst and Jim Schaad re the
DER/BER encoding issues - we'll simply mark all uses of SPKI and PKCS#8
as non-normative in the spec but not remove them.
We'll discuss how to phrase this during the telecon today.
cheers,
harry
On 07/14/2016 05:01 PM, Harry Halpin wrote:
> We've been waiting to get a 'consensus' position on spki and pkcs#8 from
> Ryan Hurst and Jim Schaad. We still hope that position comes and, in
> which case, we will offter a 'Call for Consensus' for that position.
>
> However, if we do not have any alternatives, we need a back-up plan, as
> noted in our last meeting.
>
> The proposal here is, barring any new consensus from implementers, we
> will *not* remove the references to pkcs#8 and "spki' key formats from
> the spec. Instead, we will add an explicit informative note that these
> key formats are non-normative and that for interoperability developers
> should use JWKs. JWK and raw will be specified as the normative key
> formats for usage in the WebCrypto API.
>
> We will still try to include both spki and pkcs#8 in the test-suite if
> possible in order to give feedback to implementers over lack of interop.
> In the test-suite, they will also be explicitly marked as non-normative.
>
> If there are any particular problems with SPKI and PKCS#8 that should be
> included, such as the issue of algorithm names with key export, please
> note them either in response to this CfC or in Github, and we'll can
> warnings to developers explicitly about these problems to the spec.
>
> https://github.com/w3c/webcrypto/issues/26
>
> cheers,
> harry
>
>
>
Received on Monday, 1 August 2016 10:50:31 UTC