- From: =JeffH via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Feb 2020 20:20:09 +0000
- To: public-webauthn@w3.org
in 2020-02-26 meeting, feedback is that this needs further Note:/comments targeted at implementers that:
* full JSON parser is preferred impl
* add a validators' algorithm for those who wish to take advantage of the special sauce this limited & deterministic encoding provides
* this alg needs to be crafted such that futue extensions to clientDataJSON client platforms may employ will not break existing
* add further explanation of the "hooks" this provides, eg fixed ordering of the fixed four key-value pairs, etc.
* explicitly state that these four fields are fixed forever, we can never change them in future spec versions
* explain the consequences of any future fifth (or more) key-value pairs added to the spec in terms of new browsers and RPs --- (consideration: overall in webauthn we're commiting to not make bkwards incompatible changes)
* perhaps more to add here....
--
GitHub Notification of comment by equalsJeffH
Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1375#issuecomment-591623323 using your GitHub account
Received on Wednesday, 26 February 2020 20:20:11 UTC