Re: [whatwg/url] Hoist "forbidden domain code point" check into "domain to ASCII" (Issue #818)

For reference, I sent this feedback:

> When implementing UTS 46, the most time-consuming wrong path was trying to design data structures for UTS 46 data assuming that the data needs to have distinct data entries for disallowed_STD3_valid and disallowed_STD3_mapped before discovering that these can be handled as valid and mapped with an ASCII deny list applied afterwards.
>
> I suggest refactoring the spec so that:
>
> 1) disallowed_STD3_valid and disallowed_STD3_mapped become simply valid and mapped in the data and the spec says when to apply an ASCII deny list
> 2) instead of a boolean UseSTD3ASCIIRules the algorithm would take an ASCII deny list.
>
> UTS 46 itself could define an STD3 ASCII deny list and the WHATWG URL Standard could use forbidden domain code point https://url.spec.whatwg.org/#forbidden-domain-code-point as an ASCII deny list parameter to UTS 46.
>
> It would probably appropriate to make informative remarks that a) putting ASCII letters, digits, or hyphen on the deny list would break things and b) in the validation phase, the ASCII period can be put on the deny list to handle that validity constraint as part of the ASCII deny list check.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/818#issuecomment-2036987272
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/818/2036987272@github.com>