Re: New Version Notification for draft-obispo-epp-idn-00.txt
Klaus Malorny <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <[email protected]> |
On 22/12/11 18:11, Keith Gaughan wrote: > On 22/12/11 16:41, Francisco Obispo wrote: > > > Though more specifically, the point of even asking for the language in the > first place is to prevent homograph attacks. The use of languages rather than > scripts leads to slightly odd situations where a person wouldn't be able to > register a domain like æçöÿ.info (a silly example, I know, but valid), as > though there's no language that uses all those characters in their alphabet, > it's in no way a vector for homograph attacks. > Hi, I agree to you, but the language tag(s) could be helpful in the coice of possible IDN variants. Take the letter "ö". In German, it is legal to write "oe" instead of "ö", so "götter" and "goetter" are considered equal and thus a registry could reserve the other variant for the registrant of the first. For a different language (maybe Swedish?), the "ö" may exist as well, but there is no such rule, the two words are considered different and there is no reason to block the other. I am in no way a language expert, but I guess there is a similar game with accents and esp. with ideographs in other languages. Regarding multiple tags: I personally think it should be legal to mix languages and scripts under certain (narrow) conditions. Why should a domain like "café-mосква.ru" not be possible? I don't know whether such a domain name make sense regarding usability, but from a registry viewpoint it shouldn't matter. At the end the basic question is what needs the extension shall cover. As far as I can see, the existing and future gTLDs seem to be mostly bound to the visions of ICANN (and this is the "one language" approach), whereas existing ccTLDs seem to be rather free in their IDN implementations. So the latter could have the need of a different approach, but are they interested in such an extension at all? Regards, Klaus _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg