- From: =JeffH via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Nov 2016 16:56:28 +0000
- To: public-webauthn@w3.org
+1 to Adam. This spec is more than just an API, it also defines a (cryptographic) protocol between a "challenger/verifier" and a "signer".. https://docs.google.com/presentation/d/1om__oSew4n48MK_Qcc8deq6hCZ6720-Zvv1PdK0CrjA ..which happen to be a server and a client, respectively. As is commonly done in protocol specs, this spec (at least) needs to provide "implementation considerations" describing the ramifications of various implementation choices on the part of both servers and clients. -- GitHub Notification of comment by equalsJeffH Please view or discuss this issue at https://github.com/w3c/webauthn/issues/88#issuecomment-259465264 using your GitHub account
Received on Wednesday, 9 November 2016 16:56:34 UTC