Re: [webauthn] Add clearer definition of API use cases to the spec

Seems to be 3 canonical characteristics:
1) Positively Identify the user
2) Roaming vs Bound authenticator
3) Being able to produce an assertion without receiving a credentialID
 from the RP

for 1 only a limited memory space is required (e.g. store a PIN).  For
 3 the authenticator needs such.

-- 
GitHub Notification of comment by rlin1
Please view or discuss this issue at 
https://github.com/w3c/webauthn/issues/334#issuecomment-279487354 
using your GitHub account

Received on Monday, 13 February 2017 18:59:10 UTC