<div> </div>
<div>Great...we are making the technical difference and that they can be separate .foo and .com and that they can be owned by two differ registrars and that could be competing with each other. That point made, what I am trying to address is 2 business issues:
</div>
<div> </div>
<div>1- if 'mybrand' is to be protected i.e trademark in every country...it is a matter of purchasing all the 'mybrand' TDLs...</div>
<div>2-on the other hand, if mybarnd .com is to be protected 'in every language' under gTLD, then 'com' in every language over 200 translation need to be protected and approved by ICANN. So the guardians of this names i.e
Verisign etc.. will be translating and registering them. ARe they passing the cost to the customer? Are we going to approve over 200 maybe thousands of translations? </div>
<div> </div>
<div>What are the implications above?</div>
<div> S</div>
<div><br> </div>
<div><span class="gmail_quote">On 05/02/06, <b class="gmail_sendername">Patrik Fältström</b> <<a href="mailto:paf@cisco.com">paf@cisco.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>On 6 feb 2006, at 08.23, Sophia B wrote:<br><br>> *Ok, pls correct me if I am wrong when I am trying to speak DNAME
<br>> implementation approach:* eg. CEO of <a href="http://mybrand.com">mybrand.com</a> has to be<br>> protected in<br>> every language under a gTLD that means "com" in every language, right<br>> ? meaning they have to come up with 200 language translations of
<br>> ".com" and<br>> ICANN can approve DNAMES. Then these companies, like Versign, can<br>> go and<br>> get everyone of <a href="http://their.com">their.com</a> name holders (40 million in this case) names
<br>> translated / transliterated into 200 languages to everyone's<br>> satisfaction<br>> and register them all to get 200 x 45 million DNAMES.<br><br>First of all, you have to differ between the translation of the TLD
<br>itself and the translation of the mybrand string.<br><br>DNAME for .foo (that we say is a translation of .com to some<br>language) refering to .com make it possible to create only<br><a href="http://mybrand.com">mybrand.com
</a> and immediately have also mybrand.foo. <a href="http://mybrand.com">mybrand.com</a> and<br>mybrand.foo will be the same thing in DNS. bar.mybrand.foo and<br><a href="http://bar.mybrand.com">bar.mybrand.com</a> are also the same thing.
<br><br>If instead you create a new TLD for .foo, then both mybrand.foo and<br><a href="http://mybrand.com">mybrand.com</a> have to be explicitly delegated, with the risk the two<br>domains are owned by different registrants etc. On the other hand,
<br>there might be competition between the registry owning .foo and the<br>registry owning .com.<br><br>Similar comparison can be made inside the domain .com. One can have a<br>DNAME for .fratz as a translation of mybrand so that
<a href="http://www.fratz.com">www.fratz.com</a> is<br>the same as www.fratz.foo which is the same as www.mybrand.foo and<br><a href="http://www.mybrand.com">www.mybrand.com</a>.<br><br>So, if one only use DNAME, one will have for N language versions in
<br>the TLD and M langauge versions inside the TLD (N-1)+(M-1) DNAME<br>records and 2 delegations (one for com and one for <a href="http://mybrand.com">mybrand.com</a>).<br><br>If one have separate delegations, you will have N*M zones for the
<br>permutations of the language versions. All possible to be owned by<br>different registrants.<br><br><br> paf<br></blockquote></div><br><br clear="all"><br>-- <br>Sophia Bekele<br>Voice/Fax: 925-935-1598<br>Mob:925-818-0948
<br><a href="mailto:sophiabekele@gmail.com">sophiabekele@gmail.com</a><br><a href="mailto:sbekele@cbsintl.com">sbekele@cbsintl.com</a><br>SKYPE: skypesoph<br><a href="http://www.cbsintl.com">www.cbsintl.com</a><br>