3 ms·
uh, surely all this involves is extending DNS to be unicode compliant? not really a big deal is it?
by etherealG 17y ago
uh, surely all this involves is extending DNS to be unicode compliant? not really a big deal is it?
- sp332 17y agoFor current latin-alphabet DNS, domains are case-insensitive. Will that still be true? Will Google have to buy gooGle.com separately? How do you do "case-insensitive" Japanese - don't they have 3 separate character sets for different situations? How do you distinguish among identical-looking characters? It's technologically simple, but there's more than technology involved.
- yannis 17y agoDomain spoofing will be one major issue you can for example have 'google' with the two 'o' being greek omicrons, interesting times are coming:)
- deleted 17y ago[deleted]
- deleted 17y ago[deleted]
- barryrandall 17y agoI haven't seen the implementation plan, but it shouldn't require unicode. Current IDNs (currently available below the ccTLD and gTLD level) are implemented with Punycode, and the rollout was mostly a non-issue. We've got fraud working just fine with ASCII--non-latin character sets don't really change that. For the latin-keyboard crowd, imagine having to type in an umlaut every time you wanted to go to Google.