- From: Samuel Weiler via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Mar 2018 19:17:17 +0000
- To: public-webauthn@w3.org
here's an example: https://www.w3.org/TR/2014/CR-WebCryptoAPI-20141211/ For this specification to be advanced to Proposed Recommendation, there must be at least two independent, interoperable implementations of each feature. Each cryptographic algorithm listed in the specification is currently an "at risk" feature. In particular, we are expecting a "browser profile" to be created of interoperable algorithms for Web browsers. To exit to Proposed Recommendation, each algorithm listed in the specification should have two interoperable implementations. Furthermore, there is an open dependency on the IRTF CFRG in terms of algorithm(s). These issues should be resolved by the interoperability testing necessary to exit CR. -- GitHub Notification of comment by samuelweiler Please view or discuss this issue at https://github.com/w3c/webauthn/issues/837#issuecomment-372786271 using your GitHub account
Received on Tuesday, 13 March 2018 19:17:19 UTC