[webauthn] Why is the Token Binding ID a base64url encoded DOMString rather than an ArrayBuffer?

• From: Mike Jones via GitHub <sysbot+gh@w3.org>
• Date: Fri, 16 Feb 2018 22:52:17 +0000
• To: public-webauthn@w3.org
• Message-ID: <issues.opened-297944583-1518821536-sysbot+gh@w3.org>

selfissued has just created a new issue for https://github.com/w3c/webauthn:

== Why is the Token Binding ID a base64url encoded DOMString rather than an ArrayBuffer? ==
Given we're changing the Token Binding representation anyway, is there a reason that the Token Binding ID representation needs to stay a base64url encoded DOMString rather than be changed to an ArrayBuffer containing the raw Token Binding ID bytes?

Please view or discuss this issue at https://github.com/w3c/webauthn/issues/807 using your GitHub account

Received on Friday, 16 February 2018 22:52:19 UTC