ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

[council] Re: Regarding issues report on IDNs

  • To: GNSO Council <council@xxxxxxxxxxxxxx>
  • Subject: [council] Re: Regarding issues report on IDNs
  • From: Cary Karp <ck@nic.museum>
  • Date: Mon, 06 Feb 2006 08:42:29 +0100
  • Sender: owner-council@xxxxxxxxxxxxxx
  • User-agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)

Forwarded on Patrik's behalf. Please quote him (not me) as its author
in any response, which should also be cc'd to both John and Patrik.

-------- Original Message --------
Subject: Re: [council] Re: Regarding issues report on IDNs
Date: Mon, 6 Feb 2006 08:39:24 +0100
From: Patrik Fältström <paf@xxxxxxxxx>
To: Sophia B <sophiabekele@xxxxxxxxx>
CC: John C Klensin <klensin@xxxxxxx>, Marilyn Cade
<marilynscade@xxxxxxxxxxx>,        Cary Karp <ck@nic.museum>, Tina Dam
<dam@xxxxxxxxx>,        GNSO Council <council@xxxxxxxxxxxxxx>

On 6 feb 2006, at 08.23, Sophia B wrote:

> *Ok, pls correct me if I am wrong when I am trying to speak DNAME 
> implementation approach:*  eg. CEO of mybrand.com has to be 
> protected in every language under a gTLD that means "com" in every
> language, right ?  meaning they have to come up with 200 language
> translations of ".com" and ICANN can approve DNAMES.  Then these
> companies, like Versign, can go and get everyone of their.com name
> holders (40 million in this case) names translated / transliterated
> into 200 languages to everyone's satisfaction and register them all
> to get 200 x 45 million DNAMES.

First of all, you have to differ between the translation of the TLD
itself and the translation of the mybrand string.

DNAME for .foo (that we say is a translation of .com to some
language) refering to .com make it possible to create only
mybrand.com and immediately have also mybrand.foo. mybrand.com and
mybrand.foo will be the same thing in DNS. bar.mybrand.foo and
bar.mybrand.com are also the same thing.

If instead you create a new TLD for .foo, then both mybrand.foo and
mybrand.com have to be explicitly delegated, with the risk the two
domains are owned by different registrants etc. On the other hand,
there might be competition between the registry owning .foo and the
registry owning .com.

Similar comparison can be made inside the domain .com. One can have a
DNAME for .fratz as a translation of mybrand so that www.fratz.com is
the same as www.fratz.foo which is the same as www.mybrand.foo and
www.mybrand.com.

So, if one only use DNAME, one will have for N language versions in
the TLD and M langauge versions inside the TLD (N-1)+(M-1) DNAME
records and 2 delegations (one for com and one for mybrand.com).

If one have separate delegations, you will have N*M zones for the
permutations of the language versions. All possible to be owned by
different registrants.


     paf




<<< Chronological Index >>>    <<< Thread Index >>>