- From: Jiewen Tan via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Sep 2019 01:18:34 +0000
- To: public-webauthn@w3.org
The transport values, in my opinion, is only useful to reduce the burden of a user agent to search a credential over multiple transports if the credential can only be reached via a limited number of transports that is lower than the maximum number of transports the user agent supports. Given most of the user agents will not be able to communicate via the Lightning port, I don't see the value of having it in the AuthenticatorTransport enum. It might be useful if a credential can be searched via Lightning only but not USB, then it could help user agents that don't support Lightning to either skip searching or removing it from the allow list. However, I don't see this as a trend. Also, WebKit has landed support for NFC authenticators on iOS, see [Bug 188624](https://bugs.webkit.org/show_bug.cgi?id=188624). Comparing to Lightning dongles, NFC dongles, in my opinion, will be more common to be used with iPhones in the future. -- GitHub Notification of comment by alanwaketan Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1294#issuecomment-528154490 using your GitHub account
Received on Thursday, 5 September 2019 01:18:35 UTC