- From: Emil Lundberg via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Jul 2022 10:46:20 +0000
- To: public-webauthn@w3.org
This seems like a fair change. [ยง9. WebAuthn Extensions](https://w3c.github.io/webauthn/#sctn-extensions) does set up the difference as one of the defining properties of an extension: >Every extension is a **client extension**, meaning that the extension involves communication with and processing by the client. >[...] >An extension can also be an **authenticator extension**, meaning that the extension involves communication with and processing by the authenticator. It's not a dichotomy of separate categories, rather a subcategory and its supercategory, but it still seems fair to place the authenticator extensions separate from those that are purely client extensions. Especially since only authenticator extensions are signed. -- GitHub Notification of comment by emlun Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1760#issuecomment-1174914498 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 5 July 2022 10:46:22 UTC