- From: Harry Halpin <hhalpin@w3.org>
- Date: Mon, 06 Aug 2012 20:56:52 +0200
- To: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
Here's some draft text for the editors of the API as promised at the
F2F, I'd like to test for formal consensus on this:
"As the API is meant to be extensible in order to keep up with future
developments within cryptography and to provide flexibility, there are
no strictly required algorithms. Thus users of this algorithm should
check to see what algorithms are currently recommended and supported by
implementations.
However, in order to promote interoperability for developers, there are
a number of recommended algorithms. The recommended algorithms are: HMAC
using SHA-256, RSASSA using SHA-256 hash, and ECDSA using P-256 curve
and we expect implementations at the time of publication of this
Recommendation to support these algorithms. To see the results of
test-cases between implementations, please see the [@@Upcoming] Web
Cryptography Test Cases Working Group."
I think that's quite short and clear. I do expect word-smithing from the
editors of course. I do think a table for how to do common ciphersuites
would be useful, but that can wait till after FPWD.
cheers,
harry
Received on Monday, 6 August 2012 18:57:03 UTC