<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Main IDN User Question</title>
	<atom:link href="http://blog.icann.org/2008/06/main-idn-user-question-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.icann.org/2008/06/main-idn-user-question-2/</link>
	<description>Internet Corporation for Assigned Names and Numbers</description>
	<lastBuildDate>Mon, 23 Nov 2009 02:20:28 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: IDN Club</title>
		<link>http://blog.icann.org/2008/06/main-idn-user-question-2/comment-page-1/#comment-14782</link>
		<dc:creator>IDN Club</dc:creator>
		<pubDate>Tue, 19 Aug 2008 07:13:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=334#comment-14782</guid>
		<description>原本 ASCii 域名的後綴也是非常多;
如果 ASCii 域名 的後綴 不會造成 混淆,
理論上 - IDN 域名 的後綴 也不會造成 混淆</description>
		<content:encoded><![CDATA[<p>原本 ASCii 域名的後綴也是非常多;<br />
如果 ASCii 域名 的後綴 不會造成 混淆,<br />
理論上 &#8211; IDN 域名 的後綴 也不會造成 混淆</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IDN Club</title>
		<link>http://blog.icann.org/2008/06/main-idn-user-question-2/comment-page-1/#comment-14781</link>
		<dc:creator>IDN Club</dc:creator>
		<pubDate>Tue, 19 Aug 2008 07:10:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=334#comment-14781</guid>
		<description>[安全认证机制] -
只針對 網站 做 &#039;安全认证&#039;
應該不成為問題;
目前的系統已經在實施中...</description>
		<content:encoded><![CDATA[<p>[安全认证机制] -<br />
只針對 網站 做 &#8216;安全认证&#8217;<br />
應該不成為問題;<br />
目前的系統已經在實施中&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SEO Dubai</title>
		<link>http://blog.icann.org/2008/06/main-idn-user-question-2/comment-page-1/#comment-14767</link>
		<dc:creator>SEO Dubai</dc:creator>
		<pubDate>Sun, 17 Aug 2008 01:22:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=334#comment-14767</guid>
		<description>The sad part is that most of the TLDs are registered and blocked by people who do not intend to promote them. I wish there was a regulation to curb cyber squatting.</description>
		<content:encoded><![CDATA[<p>The sad part is that most of the TLDs are registered and blocked by people who do not intend to promote them. I wish there was a regulation to curb cyber squatting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bergues</title>
		<link>http://blog.icann.org/2008/06/main-idn-user-question-2/comment-page-1/#comment-14675</link>
		<dc:creator>Bergues</dc:creator>
		<pubDate>Wed, 30 Jul 2008 11:47:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=334#comment-14675</guid>
		<description>Mr Anonymous Bis, so first, i m not anonymous (the link pointed to my web cv)

Then, i ve got my one set of IDN, (i would not be there if i hadn&#039;t :) )

i don&#039;t agree with your theory, i don&#039;t think the success of the idn will only rely on the amount of domain sold (and the fee that domainers payed for it). The fact is that many of this domains were sold to domainers, and that people who could be interested by this domain would not find what they want because it was already parked by some people. (note that there is other factors not involving domainers like this domain were used for fishing)

Thus, search engine like google, yahoo and msn doesn&#039;t handle well ( or at least doesn&#039;t given them enough credits to be well indexed in the search result) , if you wan&#039;t a simple sample, i submitted a bug about idn in Google Images, the fact is that this bug is still not taken into account
http://groups.google.fr/group/Google_Webmaster_Help-Indexing/browse_thread/thread/c50aeaada9fa73a8?fwc=1
n, why ... surely because it&#039;s considered as a minor bug as there is not a lot of non parked idn website (at least in europe).

In gwt, when you click on &quot;most current request&quot; (i m not sure of the translation), there is a javascript bugs to display the page ...

Moreover, i m not sure puny code &amp; classical version are well handled by the rankin algorihtm ...

André</description>
		<content:encoded><![CDATA[<p>Mr Anonymous Bis, so first, i m not anonymous (the link pointed to my web cv)</p>
<p>Then, i ve got my one set of IDN, (i would not be there if i hadn&#8217;t <img src='http://blog.icann.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  )</p>
<p>i don&#8217;t agree with your theory, i don&#8217;t think the success of the idn will only rely on the amount of domain sold (and the fee that domainers payed for it). The fact is that many of this domains were sold to domainers, and that people who could be interested by this domain would not find what they want because it was already parked by some people. (note that there is other factors not involving domainers like this domain were used for fishing)</p>
<p>Thus, search engine like google, yahoo and msn doesn&#8217;t handle well ( or at least doesn&#8217;t given them enough credits to be well indexed in the search result) , if you wan&#8217;t a simple sample, i submitted a bug about idn in Google Images, the fact is that this bug is still not taken into account<br />
<a href="http://groups.google.fr/group/Google_Webmaster_Help-Indexing/browse_thread/thread/c50aeaada9fa73a8?fwc=1" rel="nofollow">http://groups.google.fr/group/Google_Webmaster_Help-Indexing/browse_thread/thread/c50aeaada9fa73a8?fwc=1</a><br />
n, why &#8230; surely because it&#8217;s considered as a minor bug as there is not a lot of non parked idn website (at least in europe).</p>
<p>In gwt, when you click on &#8220;most current request&#8221; (i m not sure of the translation), there is a javascript bugs to display the page &#8230;</p>
<p>Moreover, i m not sure puny code &amp; classical version are well handled by the rankin algorihtm &#8230;</p>
<p>André</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 8you8</title>
		<link>http://blog.icann.org/2008/06/main-idn-user-question-2/comment-page-1/#comment-14628</link>
		<dc:creator>8you8</dc:creator>
		<pubDate>Mon, 21 Jul 2008 16:13:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=334#comment-14628</guid>
		<description>域名后缀太多了,很容易混淆的</description>
		<content:encoded><![CDATA[<p>域名后缀太多了,很容易混淆的</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.icann.org/2008/06/main-idn-user-question-2/comment-page-1/#comment-14595</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 04 Jul 2008 20:28:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=334#comment-14595</guid>
		<description>Domainers have been paying for IDN&#039;s since 8 years ago, the bulk of IDN registrations have come from domainers who understood the potential. You were sleeping when it happened and now you&#039;re happy to get a new chance, something like that mr. anonymous?
There is no such thing as a blacklist, especially not if you are a domainer because that would cost them money, money they received in bulk over 8 years from the renewal fees payed by &quot;domainers&quot;. 

New .tld&#039;s for IDN will add to the confusion, aliasing is the only viable option for clearity and marketability and the only fair option for the existing users who (unwittingly) payed for a new idn-tlds that devaluates their domains. The whole point of aliasing is that there will be the least amount of confusion, no parallel existence of extensions, just one functional extension in multiple languages.

Technical problems ?  You can&#039;t on one hand claim that cctld&#039;s will most likely go for aliasing (as is also suggested by the .jp-registry) and on the other hand claim that aliasing .gtld&#039;s is somehow  technically infeasible at the moment. 

Also, if indeed aliasing is possible as it should be then there&#039;s no need to go through a .tld application process since the extension only get&#039;s an extra alias....logically that is.  Is it really necessary to go through the application process again instead of simply attaching the cost of these aliases to the existing contracts ?</description>
		<content:encoded><![CDATA[<p>Domainers have been paying for IDN&#8217;s since 8 years ago, the bulk of IDN registrations have come from domainers who understood the potential. You were sleeping when it happened and now you&#8217;re happy to get a new chance, something like that mr. anonymous?<br />
There is no such thing as a blacklist, especially not if you are a domainer because that would cost them money, money they received in bulk over 8 years from the renewal fees payed by &#8220;domainers&#8221;. </p>
<p>New .tld&#8217;s for IDN will add to the confusion, aliasing is the only viable option for clearity and marketability and the only fair option for the existing users who (unwittingly) payed for a new idn-tlds that devaluates their domains. The whole point of aliasing is that there will be the least amount of confusion, no parallel existence of extensions, just one functional extension in multiple languages.</p>
<p>Technical problems ?  You can&#8217;t on one hand claim that cctld&#8217;s will most likely go for aliasing (as is also suggested by the .jp-registry) and on the other hand claim that aliasing .gtld&#8217;s is somehow  technically infeasible at the moment. </p>
<p>Also, if indeed aliasing is possible as it should be then there&#8217;s no need to go through a .tld application process since the extension only get&#8217;s an extra alias&#8230;.logically that is.  Is it really necessary to go through the application process again instead of simply attaching the cost of these aliases to the existing contracts ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.icann.org/2008/06/main-idn-user-question-2/comment-page-1/#comment-14591</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 04 Jul 2008 07:42:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=334#comment-14591</guid>
		<description>there will be no confusion because this time, the domain buyer will be checked ... perhaps you can even imagine that kown domainers willl be blacklisted, and not able to register domains in mass</description>
		<content:encoded><![CDATA[<p>there will be no confusion because this time, the domain buyer will be checked &#8230; perhaps you can even imagine that kown domainers willl be blacklisted, and not able to register domains in mass</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kuxun.biz</title>
		<link>http://blog.icann.org/2008/06/main-idn-user-question-2/comment-page-1/#comment-14582</link>
		<dc:creator>kuxun.biz</dc:creator>
		<pubDate>Sat, 28 Jun 2008 23:10:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=334#comment-14582</guid>
		<description>过多的语言支持，新的域名后缀出现，域名市场将会出现前所未有的互联，必将引发新的安全认证机制。</description>
		<content:encoded><![CDATA[<p>过多的语言支持，新的域名后缀出现，域名市场将会出现前所未有的互联，必将引发新的安全认证机制。</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: I Can</title>
		<link>http://blog.icann.org/2008/06/main-idn-user-question-2/comment-page-1/#comment-14581</link>
		<dc:creator>I Can</dc:creator>
		<pubDate>Sat, 28 Jun 2008 11:57:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=334#comment-14581</guid>
		<description>I think the addition to new tld will just ad to the confusion.

It was a bad idea - maybe you can stop it early enough!

:(</description>
		<content:encoded><![CDATA[<p>I think the addition to new tld will just ad to the confusion.</p>
<p>It was a bad idea &#8211; maybe you can stop it early enough!</p>
<p> <img src='http://blog.icann.org/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: МАРНИЧ</title>
		<link>http://blog.icann.org/2008/06/main-idn-user-question-2/comment-page-1/#comment-14580</link>
		<dc:creator>МАРНИЧ</dc:creator>
		<pubDate>Sat, 28 Jun 2008 06:50:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=334#comment-14580</guid>
		<description>ИГРАЕМ ПО НОВЫМ ПРАВИЛАМ ICANN?

ЕСЛИ ТЫ НОСИТЕЛЬ СТОЯЩЕЙ ИДЕИ


Я предлагаю обсудить концепцию доменного пространства в очень  специфическом срезе. Это предложение в первую очередь для тех, кто считает себя носителем необходимых обществу идей. 

Не имея средств на покупку доменного имени верхнего уровня, носитель идеи заинтересован ассоциироваться в первую очередь с теми владельцами средств (потенциальными вкладчиками), которые не скомпрометируют  выношенную автором ИДЕЮ сомнительными способами извлечения выгоды. 

Чтобы выделить свой (или НАШ) вариант оформления заявочного приоритета - через публичное обсуждение мотивов и претензий - на фоне любых других вариантов, я ввожу  в оборот сегодняшним днём (28.06.08.) отдельное название для застолблённого таким образом домена – АБАЛОНКАВЫ ДОМЕН. Имея в виду сравнение (на языке оригинала)  процесса заполнения оболочки растущим числом «приталкиваемых интеграционно» субъектов с созреванием граната или  бластулы.

История этого названия начинается здесь
http://forums.tut.by/showflat.php?Board=socleader&amp;Number=6081818&amp;page=0&amp;view=collapsed&amp;sb=5&amp;o=&amp;fpart=#Post6081818&amp;ccache=583793c583de7179c33cf5df16c0c589 

А обсуждение вариантов регистрации  записанного в общем виде имени (VVWW+АДРАC+СРА+ЗУ) предлагаю обсудить в одном из моих блогов, например здесь
http://maphi4.livejournal.com/2614.html</description>
		<content:encoded><![CDATA[<p>ИГРАЕМ ПО НОВЫМ ПРАВИЛАМ ICANN?</p>
<p>ЕСЛИ ТЫ НОСИТЕЛЬ СТОЯЩЕЙ ИДЕИ</p>
<p>Я предлагаю обсудить концепцию доменного пространства в очень  специфическом срезе. Это предложение в первую очередь для тех, кто считает себя носителем необходимых обществу идей. </p>
<p>Не имея средств на покупку доменного имени верхнего уровня, носитель идеи заинтересован ассоциироваться в первую очередь с теми владельцами средств (потенциальными вкладчиками), которые не скомпрометируют  выношенную автором ИДЕЮ сомнительными способами извлечения выгоды. </p>
<p>Чтобы выделить свой (или НАШ) вариант оформления заявочного приоритета &#8211; через публичное обсуждение мотивов и претензий &#8211; на фоне любых других вариантов, я ввожу  в оборот сегодняшним днём (28.06.08.) отдельное название для застолблённого таким образом домена – АБАЛОНКАВЫ ДОМЕН. Имея в виду сравнение (на языке оригинала)  процесса заполнения оболочки растущим числом «приталкиваемых интеграционно» субъектов с созреванием граната или  бластулы.</p>
<p>История этого названия начинается здесь<br />
<a href="http://forums.tut.by/showflat.php?Board=socleader&amp;Number=6081818&amp;page=0&amp;view=collapsed&amp;sb=5&amp;o=&amp;fpart=#Post6081818&amp;ccache=583793c583de7179c33cf5df16c0c589" rel="nofollow">http://forums.tut.by/showflat.php?Board=socleader&amp;Number=6081818&amp;page=0&amp;view=collapsed&amp;sb=5&amp;o=&amp;fpart=#Post6081818&amp;ccache=583793c583de7179c33cf5df16c0c589</a> </p>
<p>А обсуждение вариантов регистрации  записанного в общем виде имени (VVWW+АДРАC+СРА+ЗУ) предлагаю обсудить в одном из моих блогов, например здесь<br />
<a href="http://maphi4.livejournal.com/2614.html" rel="nofollow">http://maphi4.livejournal.com/2614.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
