Re: [webauthn] Processing model for extensions is very underdefined

Recording another couple missing bits in the extension processing model:

* https://w3c.github.io/webauthn/#makeCredential doesn't look up the extension's key in the registry.
* https://w3c.github.io/webauthn/#client-processing doesn't yet say what type a client-processing algorithm returns.
* https://w3c.github.io/webauthn/#extension-txauth-simple talks about "default forwarding", for which I can't find a definition.

This is *not* a complete list of places where the input, output, and important utility operations are underdefined for extension algorithms. Someone who cares about extensions should re-read their use and definitions and file bugs for problems similar to the above.

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

Received on Wednesday, 22 March 2017 20:06:19 UTC