- From: <bugzilla@jessica.w3.org>
- Date: Wed, 11 Jun 2014 09:11:22 +0000
- To: public-webcrypto@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25985 --- Comment #31 from Ryan Sleevi <sleevi@google.com> --- (In reply to Web Cryptography Working Group from comment #27) > The NIST curves are widely deployed. Nonetheless, there is also demand for > Curve25519. Ultimately, while browsers often do have local policy they have > to deal with, the W3C needs to have an test-suite to prove interoperability > over the API. We should test every algorithm that is listed as registered. > I see no reason why not to register Curve25519 given the demand and given > that it can be specified, and if browsers don't implement it, that will show > up in the CR test-suite report. The CR test-suite report for browsers, which > will depend on underlying libraries, will then demonstrate from the > interopeability that developers can expect and rely on. The support for Curve25519 is a separate bug. Let's keep it that way. If you want to talk about lack of interoperability, specification, or maturity, that's a great one to focus on exactly why we should not be including it in Web Crypto. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Wednesday, 11 June 2014 09:11:24 UTC