Re: [webauthn] Unspecified CBOR encoding of high-valued integer numbers due to unspecified threshold (#1044) from Peter Occil via GitHub on 2019-08-10 (public-webauthn@w3.org from August 2019)

From: Peter Occil via GitHub <sysbot+gh@w3.org>
Date: Sat, 10 Aug 2019 00:55:07 +0000
To: public-webauthn@w3.org
Message-ID: <issue_comment.created-520104468-1565398506-sysbot+gh@w3.org>

I see that currently, of the defined WebAuthn extensions, only `biometricPerfBounds` includes number types, namely `float` in client extension inputs.  This suggests to me that&mdash;

- section 9 can simply say "When the JavaScript value is a `float`..." rather than "When the JavaScript value is a non-integer number", and
- WebAuthn should discourage new extensions that use any number type other than `float` in their client extension inputs.

With these changes, this issue becomes resolved as moot.

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

Received on Saturday, 10 August 2019 00:55:09 UTC