- From: Ki-Eun Shin via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jun 2019 04:10:59 +0000
- To: public-webauthn@w3.org
> Do you mean to say that during the discussions of the resident key feature (PR #1191), we did consider assigning one of the "Reserved for Future Use (RFU)" flags, and in that discussion we were unsure how to go about about assigning one of the RFU flags for that purpose? Yes. I think we don't have any feasible way to consume the RFU bits. > I am unsure what you mean here -- perhaps you could provide a worked-out example? In current WebAuthn spec, we don't have any version information. So, from the RP perspective, new flags in Authenticator Data cannot be distinguishable from the old one. For doing this, we should have some distinguishable information like version. E.g., authenticator can return the version information within the authenticator extension that it supports. -- GitHub Notification of comment by Kieun Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1220#issuecomment-501113316 using your GitHub account
Received on Wednesday, 12 June 2019 04:11:01 UTC