W3C home > Mailing lists > Public > public-webcrypto@w3.org > July 2016

Call for consensus: Marking spki and pkcs8 key format support as non-normative

From: Harry Halpin <hhalpin@w3.org>
Date: Thu, 14 Jul 2016 17:01:32 +0200
To: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
Message-ID: <5787A94C.3030008@w3.org>
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.


Received on Thursday, 14 July 2016 15:01:40 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 14 July 2016 15:01:40 UTC