Some ambiguity in what is or isn’t allowed seems to be a problem for Universal Acceptance, no? From: Anne van Kesteren <notifications@github.com> Sent: Friday, March 27, 2020 7:30 AM To: whatwg/url <url@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: Re: [whatwg/url] DNS (and other naming systems) vs the host parser (#397) A way out here mentioned in https://bugzilla.mozilla.org/show_bug.cgi?id=1184059#c29 might be that we have a separate "DNS domain" definition which is effectively a further validation on the output of the host parser (if it is a domain) that allows * what https://tools.ietf.org/html/rfc1034 as modified by https://tools.ietf.org/html/rfc1123#section-2 allows * underscores * hyphens in more places? As this definition is mainly needed by various networking standards, it doesn't necessarily have to live in the URL Standard. Fetch could be a place, but perhaps filing some issues against the relevant standards that have a dependency on the "broken" concept could also result in some action. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <https://github.com/whatwg/url/issues/397#issuecomment-605031328> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIQTK6DCK7SHV2YX5RMSX3RJS...> . <https://github.com/notifications/beacon/AAIQTK4SSJA27VS3OCLKJ3DRJSZ5BA5CNFSM...>