This field ends up transmitted to the security key hardware, which is fixed-function, practically un-updatable, and which only accepts a single field. So, while changes in future devices could be imagined, any solution that adds fields will not function with any of the millions of devices already in existance. Thus, while they are discouraged in the document, the systems for embedding this information in the string ([1](https://www.w3.org/TR/string-meta/#rlm) [2](https://www.w3.org/TR/string-meta/#unicodeTags)) seem the most promising. Their downside here is the encoding size: 24 bytes for many languages. -- GitHub Notification of comment by agl Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1526#issuecomment-736015319 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Monday, 30 November 2020 20:10:50 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 07:26:42 UTC