Comments on: Will IDN Top Level Domains Kill Existing IDN Domain Names? http://domainnamewire.com/2009/10/02/will-idn-top-level-domains-kill-existing-idn-domain-names/ Domain Name Industry News and Views Sat, 26 May 2012 20:25:03 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Reading blogs #21 : ::: Think Macro ::: http://domainnamewire.com/2009/10/02/will-idn-top-level-domains-kill-existing-idn-domain-names/comment-page-1/#comment-497335 Reading blogs #21 : ::: Think Macro ::: Thu, 22 Oct 2009 03:25:21 +0000 http://domainnamewire.com/?p=8497#comment-497335 [...] names (domain names in non-Latin characters).  Here is one response to these developments and here is another really interesting conversation (you have to read the comments to get the full value out [...]

[...] names (domain names in non-Latin characters).  Here is one response to these developments and here is another really interesting conversation (you have to read the comments to get the full value out [...]

]]> By: Andrew Allemann http://domainnamewire.com/2009/10/02/will-idn-top-level-domains-kill-existing-idn-domain-names/comment-page-1/#comment-492986 Andrew Allemann Tue, 13 Oct 2009 16:14:31 +0000 http://domainnamewire.com/?p=8497#comment-492986 @ Rob - IDN ccTLDs can be part of a "fast track" process, which should be generally approved at the next ICANN meeting later this month. gTLD IDNs aren't scheduled to come out until the general release of new gTLDs such as .eco, and who knows when that will happen. @ Rob – IDN ccTLDs can be part of a “fast track” process, which should be generally approved at the next ICANN meeting later this month. gTLD IDNs aren’t scheduled to come out until the general release of new gTLDs such as .eco, and who knows when that will happen.

]]> By: rob http://domainnamewire.com/2009/10/02/will-idn-top-level-domains-kill-existing-idn-domain-names/comment-page-1/#comment-492908 rob Tue, 13 Oct 2009 12:02:45 +0000 http://domainnamewire.com/?p=8497#comment-492908 I'm confused when is the gTLD IDN's scheduled for?? I thought that they are only comin out wiht the ccTLD IDN'S? I’m confused
when is the gTLD IDN’s scheduled for??
I thought that they are only comin out wiht the ccTLD IDN’S?

]]> By: Andrew Allemann http://domainnamewire.com/2009/10/02/will-idn-top-level-domains-kill-existing-idn-domain-names/comment-page-1/#comment-489751 Andrew Allemann Wed, 07 Oct 2009 01:50:22 +0000 http://domainnamewire.com/?p=8497#comment-489751 @ Confusingly similar - now that I see your other post, I understand what you're saying. We're talking about IDN ccTLDs here, which is completely different from IDN gTLDs. @ Confusingly similar – now that I see your other post, I understand what you’re saying. We’re talking about IDN ccTLDs here, which is completely different from IDN gTLDs.

]]> By: Andrew Allemann http://domainnamewire.com/2009/10/02/will-idn-top-level-domains-kill-existing-idn-domain-names/comment-page-1/#comment-489725 Andrew Allemann Wed, 07 Oct 2009 00:32:44 +0000 http://domainnamewire.com/?p=8497#comment-489725 @ Confusingly similar - I don't know what you're getting at here. I assume you're talking about IDN gTLDs, not ccTLDs? @ Confusingly similar – I don’t know what you’re getting at here. I assume you’re talking about IDN gTLDs, not ccTLDs?

]]> By: Confusingly similar http://domainnamewire.com/2009/10/02/will-idn-top-level-domains-kill-existing-idn-domain-names/comment-page-1/#comment-489707 Confusingly similar Tue, 06 Oct 2009 23:36:46 +0000 http://domainnamewire.com/?p=8497#comment-489707 Page 55 - Applicant guidebook V3: http://www.icann.org/en/topics/new-gtlds/draft-rfp-redline-04oct09-en.pdf An application that fails the string similarity review and is found too similar to an existing TLD will not pass the Initial Evaluation, and no further reviews will be available. An application found at risk for string confusion with another applied-for gTLD string will be placed in a contention set. An application that passes the string similarity review is still subject to challenge by an existing TLD operator or by another gTLD applicant in the current application round. That process requires that a string confusion objection be filed by an objector having the standing to make such an objection. <b>Such category of objection is not limited to visual similarity. Rather, confusion based on any type of similarity (including visual, aural, or similarity of meaning) may be claimed by an objector.</b> Refer to Module 3, Dispute Resolution Procedures, for more information about the objection process. An applicant may file a formal objection against another gTLD application on string confusion grounds (see Module 3). Such an objection may, if successful, change the configuration of the preliminary contention sets in that the two applied-for gTLD strings will be considered in direct contention with one another (see Module 4, String Contention Procedures). The objection process when initiated by an applicant cannot result in removal of an application from a contention set. Page 55 – Applicant guidebook V3: http://www.icann.org/en/topics/new-gtlds/draft-rfp-redline-04oct09-en.pdf

An application that fails the string similarity review and is
found too similar to an existing TLD will not pass the Initial
Evaluation, and no further reviews will be available.
An application found at risk for string confusion with
another applied-for gTLD string will be placed in a
contention set.
An application that passes the string similarity review is still
subject to challenge by an existing TLD operator or by
another gTLD applicant in the current application round.
That process requires that a string confusion objection be
filed by an objector having the standing to make such an
objection. Such category of objection is not limited to
visual similarity. Rather, confusion based on any type of
similarity (including visual, aural, or similarity of meaning)
may be claimed by an objector. Refer to Module 3,
Dispute Resolution Procedures, for more information about
the objection process.
An applicant may file a formal objection against another
gTLD application on string confusion grounds (see Module
3). Such an objection may, if successful, change the
configuration of the preliminary contention sets in that the
two applied-for gTLD strings will be considered in direct
contention with one another (see Module 4, String
Contention Procedures). The objection process when
initiated by an applicant cannot result in removal of an
application from a contention set.

]]> By: Confusingly similar http://domainnamewire.com/2009/10/02/will-idn-top-level-domains-kill-existing-idn-domain-names/comment-page-1/#comment-489660 Confusingly similar Tue, 06 Oct 2009 20:49:37 +0000 http://domainnamewire.com/?p=8497#comment-489660 If 2 different registrants own a variation of the same name (i.e one owns пример.com and the other owns пример.ком gTLD domain or i.e one owns 人の仲.jp and another has the 人の仲.日本 ccTLD variant, ), That is going to cause user confusion where ICANN in multiple documents clearly stated it will not allow any type of confusion (visual,aural etc) for obvious reasons which is why regardless of the specific TLD manager to a variant, they all will have to be in control of the same registrant which possibly will have to pay each (same or separated) registry for each of the variants to the domain but that is where the separation ends. From MarkMonitor: Although a formal commitment has not yet been made by Verisign to support this approach, this may now be the time to begin evaluating the registration of brands in .com and .net using native character sets to support important markets. In particular, companies should consider registering translations, transliterations, and transcriptions of their famous marks now to support current and planned global marketing efforts. By doing so, owners of these domains could potentially have <b>exclusive rights</b> to register in matching .com and .net IDN TLDs, when they become available. http://www.markmonitor.com/mmblog/consider-planning-now-for-internationalized-top-level-domains/ If 2 different registrants own a variation of the same name (i.e one owns пример.com and the other owns пример.ком gTLD domain or i.e one owns 人の仲.jp and another has the 人の仲.日本 ccTLD variant, ), That is going to cause user confusion where ICANN in multiple documents clearly stated it will not allow any type of confusion (visual,aural etc) for obvious reasons which is why regardless of the specific TLD manager to a variant, they all will have to be in control of the same registrant which possibly will have to pay each (same or separated) registry for each of the variants to the domain but that is where the separation ends.

From MarkMonitor:

Although a formal commitment has not yet been made by Verisign to support this approach, this may now be the time to begin evaluating the registration of brands in .com and .net using native character sets to support important markets. In particular, companies should consider registering translations, transliterations, and transcriptions of their famous marks now to support current and planned global marketing efforts. By doing so, owners of these domains could potentially have exclusive rights to register in matching .com and .net IDN TLDs, when they become available.

http://www.markmonitor.com/mmblog/consider-planning-now-for-internationalized-top-level-domains/

]]>