- From: =JeffH via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 May 2019 19:55:39 +0000
- To: public-webauthn@w3.org
We discussed this on the 1-May-2019 webauthn call. We noted that this would not be a simple change since the RP ID is defined in terms of [valid domain string](https://url.spec.whatwg.org/#valid-domain-string), [effective domain](https://html.spec.whatwg.org/multipage/origin.html#concept-origin-effective-domain), and being a [registrable domain suffix](https://html.spec.whatwg.org/multipage/origin.html#is-a-registrable-domain-suffix-of-or-is-equal-to) of the origin's effective domain (the latter alg specifically excludes hostnames that are an IPv4 address or an IPv6 address). Additionally there are various issues with [using identifiers other than fully qualified DNS domain names in TLS server certificates](https://tools.ietf.org/html/rfc6125#section-1.7.2). The consensus on the call was to not address this Issue and close it with no action. -- GitHub Notification of comment by equalsJeffH Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1204#issuecomment-488809694 using your GitHub account
Received on Thursday, 2 May 2019 19:55:43 UTC