From the call of 2021-01-06: We are considering what issues might be addressed in WebAuthn Level Three and feel that this is premature. While it might be the case that wide-spread use of software authenticators motivate some WebAuthn-level changes, WebAuthn itself doesn't define how authenticators are discovered. That's a platform concern. Since WebAuthn is a Web API, it's not the place to define other authenticator transports. (For example, the transport for physical authenticators is defined by FIDO, a separate body from the W3C.) As such, the group doesn't feel that it wants to take on non-Web work in L3. -- GitHub Notification of comment by agl Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1175#issuecomment-755744748 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Wednesday, 6 January 2021 22:11:37 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 07:26:42 UTC