4 ms·

Perhaps good trade-off would have been that non-ASCII is allowed only in country code TLDs, with these country operators limiting to only characters in their ow

by dezgeg 4y ago

Perhaps good trade-off would have been that non-ASCII is allowed only in country code TLDs, with these country operators limiting to only characters in their own alphabet. E.g. for Finland .fi could do fine with just allowing ASCII + ä, ö, å.

burnished 4y ago
How would that be represented on the wire? I don’t think restricting it in that way makes sense.
- dezgeg 4y ago
  Wire format could be the same. But to prevent eg. homoglyph attacks the principle on what non-Unicode characters are allowed would be 'default deny'.
  - burnished 4y ago
    Oh, of course. I retract my previous objection, brain fart on my part.
Symbiote 4y ago
That is exactly what .FI and many other CCTLD registrars do: https://www.traficom.fi/en/communications/fi-domains/native-language-characters-domain-names https://www.traficom.fi/en/communications/fi-domains/native-...
- josephcsible 4y ago
  But I don't think all of them do that. What if browsers, etc. were updated so that IDNs under TLDs where that rule isn't strictly enforced were always rendered in punycode?
  - Symbiote 4y ago
    Firefox already does this, with some improvements. https://wiki.mozilla.org/IDN_Display_Algorithm https://wiki.mozilla.org/IDN_Display_Algorithm
    - josephcsible 4y ago
      That's a good start, but IMO it's still too lax.
cryptonector 4y ago
DNS registries are free to come up with rules like that, FYI. (And they should.)