- From: Adam Langley via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Jan 2018 19:00:34 +0000
- To: public-webauthn@w3.org
>From the discussion today: Mike envisions that browsers will do generic transcoding of unknown extensions, but that extensions may also define a specific transcoding function for browsers that understand it. Thus tokens have to be able to handle either and the specific function must be careful not to be ambiguous with the generic output. I think the generic transcoding needs to be more precisely defined. (For example, I assume that floats are banned and that ArrayBuffer turns into `bytes`, but I'm not sure.) -- GitHub Notification of comment by agl Please view or discuss this issue at https://github.com/w3c/webauthn/issues/738#issuecomment-356702396 using your GitHub account
Received on Wednesday, 10 January 2018 19:00:42 UTC