Comments on: Clearing the Confusion (Fast Track) http://blog.icann.org/2010/03/clearing-the-confusion-fast-track/ Internet Corporation for Assigned Names and Numbers Wed, 08 Feb 2012 01:42:27 -0800 hourly 1 http://wordpress.org/?v=3.3.1 By: Vassil Petev http://blog.icann.org/2010/03/clearing-the-confusion-fast-track/comment-page-1/#comment-23354 Vassil Petev Tue, 24 Aug 2010 15:28:58 +0000 http://blog.icann.org/?p=1385#comment-23354 [This information has already been submitted to ICANN through the regular feedback channels] I do believe that there is a shortcoming in the way the Fast Track Process determines a confusingly similar string, which I have analyzed in detail in a blog: <a href="http://www.circleid.com/posts/string_similarity_case_of_the_bulgarian_cyrillic_idn_vs_brazil_cctld/" title="Putting String Similarity into Context: Bulgaria's IDN (.бг) vs. Brazil's ccTLD (.br)" rel="nofollow">Putting String Similarity into Context: Bulgaria's IDN (.бг) vs. Brazil's ccTLD (.br)</a> Everyone's comments will be greatly appreciated! [This information has already been submitted to ICANN through the regular feedback channels]

I do believe that there is a shortcoming in the way the Fast Track Process determines a confusingly similar string, which I have analyzed in detail in a blog:
Putting String Similarity into Context: Bulgaria’s IDN (.бг) vs. Brazil’s ccTLD (.br)

Everyone’s comments will be greatly appreciated!

]]> By: Tina Dam http://blog.icann.org/2010/03/clearing-the-confusion-fast-track/comment-page-1/#comment-22538 Tina Dam Wed, 02 Jun 2010 22:57:41 +0000 http://blog.icann.org/?p=1385#comment-22538 @Николай Филипов / Nikolay Filipov : I am sorry for the late reply to you. Unfortunately I wont be able to help you much. The requests in the IDN ccTLD fast Track Process are confidential and I am unable to discuss any of them in any detail. In general, the confusingly similar verification or assesment is done by a panel of experts that is external to ICANN staff - as such this is not me or my collegueas that are making these types of decisions, but experts in the field. I do want to note that the subject of confusingly similar is very important and adding these IDNs means a much bigger risk for domain names to be confusingly similar. The uniqueness principle is one of the main reasons that the Internet, or the domain name part of it, works so well. As such we are very careful about introduction of new TLDs, of any kind. Tina @Николай Филипов / Nikolay Filipov : I am sorry for the late reply to you. Unfortunately I wont be able to help you much. The requests in the IDN ccTLD fast Track Process are confidential and I am unable to discuss any of them in any detail.

In general, the confusingly similar verification or assesment is done by a panel of experts that is external to ICANN staff – as such this is not me or my collegueas that are making these types of decisions, but experts in the field. I do want to note that the subject of confusingly similar is very important and adding these IDNs means a much bigger risk for domain names to be confusingly similar. The uniqueness principle is one of the main reasons that the Internet, or the domain name part of it, works so well. As such we are very careful about introduction of new TLDs, of any kind.

Tina

]]> By: araba kiralama http://blog.icann.org/2010/03/clearing-the-confusion-fast-track/comment-page-1/#comment-22320 araba kiralama Fri, 07 May 2010 10:09:32 +0000 http://blog.icann.org/?p=1385#comment-22320 Hi all; NİCES VERY GOOD You could dial the number of a cell phone or other phone with caller ID that you could check… Hi all; NİCES VERY GOOD
You could dial the number of a cell phone or other phone with caller ID that you could check…

]]> By: 007 Casus http://blog.icann.org/2010/03/clearing-the-confusion-fast-track/comment-page-1/#comment-22266 007 Casus Tue, 04 May 2010 19:03:23 +0000 http://blog.icann.org/?p=1385#comment-22266 Thanks Thanks

]]> By: uberVU - social comments http://blog.icann.org/2010/03/clearing-the-confusion-fast-track/comment-page-1/#comment-21810 uberVU - social comments Sun, 28 Mar 2010 03:45:46 +0000 http://blog.icann.org/?p=1385#comment-21810 <strong>Social comments and analytics for this post...</strong> This post was mentioned on Twitter by DomainHunter: ICANN blog: Clearing the Confusion (Fast Track): Since the launch of the Fast Track Process, ICANN has received ma... http://bit.ly/9Qz5bm... Social comments and analytics for this post…

This post was mentioned on Twitter by DomainHunter: ICANN blog: Clearing the Confusion (Fast Track): Since the launch of the Fast Track Process, ICANN has received ma… http://bit.ly/9Qz5bm...

]]> By: Leontinka http://blog.icann.org/2010/03/clearing-the-confusion-fast-track/comment-page-1/#comment-21782 Leontinka Wed, 24 Mar 2010 10:29:53 +0000 http://blog.icann.org/?p=1385#comment-21782 which would confuse potential Russian users who have no command in English. which would confuse potential Russian users who have no command in English.

]]> By: Nilya http://blog.icann.org/2010/03/clearing-the-confusion-fast-track/comment-page-1/#comment-21781 Nilya Wed, 24 Mar 2010 08:08:00 +0000 http://blog.icann.org/?p=1385#comment-21781 for Russian Federation for Russian Federation

]]> By: Tina Dam http://blog.icann.org/2010/03/clearing-the-confusion-fast-track/comment-page-1/#comment-21681 Tina Dam Fri, 12 Mar 2010 01:48:05 +0000 http://blog.icann.org/?p=1385#comment-21681 @ Leonid, thanks for providing a real example. I think the explanations around rationales for the РФ extension is very useful and probably can be helpful for other countries and territories considering participation in the Fast Track Process. Tina @ Leonid, thanks for providing a real example. I think the explanations around rationales for the РФ extension is very useful and probably can be helpful for other countries and territories considering participation in the Fast Track Process.

Tina

]]> By: Leonid Todorov http://blog.icann.org/2010/03/clearing-the-confusion-fast-track/comment-page-1/#comment-21617 Leonid Todorov Wed, 10 Mar 2010 05:37:15 +0000 http://blog.icann.org/?p=1385#comment-21617 Fr0m what I can see, there clearly is some confusion with respect to a new IDN TLD\'s name selection procedure. So, why Russia has embarked for .РФ? The reason is two-fold. First, while choosing between РУ (\" RU \" transliterated in Russian) and РФ, clearly, the PУ looks pretty much similar to the combination of Latin characters P and Y, which would confuse potential Russian users who have no command in English. Plus, such a combination bears no sense in Russian. In contrast, \"РФ\" contains a unique non-lating character \"Ф\" (pronounced as [ef]), which will undisputably distinguish it from any other TLD, no matter it is based on the Latin or Cyrillic script; furthermore РФ is an informal common acronym for Russian Federation (Российская Федерация) and as such is broadly recognized and actively used by Russian-laanguage speakers. The selection of the РФ was made by means of online poll ccTLD .RU has been running for a few weeks back in 2008. The overwhelming majority of Internet users voted nearly unanimously for .РФ - vox populi, vox dei, and since then on the acronym \"РФ\" has become an \"official\" name of the soon-t0-unfold (touch wood!) IDN TLD for Russia. Hope it will help Fr0m what I can see, there clearly is some confusion with respect to a new IDN TLD\’s name selection procedure. So, why Russia has embarked for .РФ?
The reason is two-fold.
First, while choosing between РУ (\” RU \” transliterated in Russian) and РФ, clearly, the PУ looks pretty much similar to the combination of Latin characters P and Y, which would confuse potential Russian users who have no command in English. Plus, such a combination bears no sense in Russian.
In contrast, \”РФ\” contains a unique non-lating character \”Ф\” (pronounced as [ef]), which will undisputably distinguish it from any other TLD, no matter it is based on the Latin or Cyrillic script; furthermore РФ is an informal common acronym for Russian Federation (Российская Федерация) and as such is broadly recognized and actively used by Russian-laanguage speakers.
The selection of the РФ was made by means of online poll ccTLD .RU has been running for a few weeks back in 2008. The overwhelming majority of Internet users voted nearly unanimously for .РФ – vox populi, vox dei, and since then on the acronym \”РФ\” has become an \”official\” name of the soon-t0-unfold (touch wood!) IDN TLD for Russia.
Hope it will help

]]> By: Tina Dam http://blog.icann.org/2010/03/clearing-the-confusion-fast-track/comment-page-1/#comment-21609 Tina Dam Tue, 09 Mar 2010 21:16:35 +0000 http://blog.icann.org/?p=1385#comment-21609 @Taran, good point. I will try to see if we can have a couple of examples that will not be seen as problematic from the corresponding country or territory. Hopefully you can imagien that several characters in for example Cyrillic and Greek look a lot like the basic Latin characters (a,b,c...) and hence IDN ccTLD strings can look like exisiting ccTLDs (.gr, .cn, .br, .py, .kr, etc...) Tina @Taran, good point. I will try to see if we can have a couple of examples that will not be seen as problematic from the corresponding country or territory.

Hopefully you can imagien that several characters in for example Cyrillic and Greek look a lot like the basic Latin characters (a,b,c…) and hence IDN ccTLD strings can look like exisiting ccTLDs (.gr, .cn, .br, .py, .kr, etc…)

Tina

]]>