<?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: So where are we up to with these new Internet extensions?</title>
	<atom:link href="http://blog.icann.org/2009/05/so-where-are-we-up-to-with-these-new-internet-extensions/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.icann.org/2009/05/so-where-are-we-up-to-with-these-new-internet-extensions/</link>
	<description>Internet Corporation for Assigned Names and Numbers</description>
	<lastBuildDate>Wed, 08 Feb 2012 01:42:27 -0800</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: games</title>
		<link>http://blog.icann.org/2009/05/so-where-are-we-up-to-with-these-new-internet-extensions/comment-page-1/#comment-21184</link>
		<dc:creator>games</dc:creator>
		<pubDate>Wed, 03 Feb 2010 16:06:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=794#comment-21184</guid>
		<description>It is really important that these issues are trashed out at this period in time. We, in Nigeria are currently meeting trying to see how the developing world can take a full advantage of this situation</description>
		<content:encoded><![CDATA[<p>It is really important that these issues are trashed out at this period in time. We, in Nigeria are currently meeting trying to see how the developing world can take a full advantage of this situation</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nils</title>
		<link>http://blog.icann.org/2009/05/so-where-are-we-up-to-with-these-new-internet-extensions/comment-page-1/#comment-18614</link>
		<dc:creator>nils</dc:creator>
		<pubDate>Sat, 08 Aug 2009 21:54:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=794#comment-18614</guid>
		<description>New TLDs  WILL (I think) Cause Internet Land Rush 

Everyone knows that this is the first and maybe the last
chance, they have,to becom the owner of the great new tld.
So i predict that we are going to see.A landrush unlike anything seen befor.With fierce battles between different
Project stakeholders.
Some companies will buy many new TLDs.Better to own to many than to few.
Smart people will investigate the new TLDs potential for earnings and judge if it exceeds the various ICANN fees and Other expenses.
My guess is that most okay-keyword-TLDs will be profitable
and therefor i think we are going to see 1000&#039;s if not 10000&#039;s
of new TLDs.
.stock .oracle .print .company .Airport .BLOG .town .hockey 
.Tobacco .tools .business .brokers .hire .logo .peace .date .pool .Bowling .Dolls .dream .game .Boxing .nutrition .bob</description>
		<content:encoded><![CDATA[<p>New TLDs  WILL (I think) Cause Internet Land Rush </p>
<p>Everyone knows that this is the first and maybe the last<br />
chance, they have,to becom the owner of the great new tld.<br />
So i predict that we are going to see.A landrush unlike anything seen befor.With fierce battles between different<br />
Project stakeholders.<br />
Some companies will buy many new TLDs.Better to own to many than to few.<br />
Smart people will investigate the new TLDs potential for earnings and judge if it exceeds the various ICANN fees and Other expenses.<br />
My guess is that most okay-keyword-TLDs will be profitable<br />
and therefor i think we are going to see 1000&#8242;s if not 10000&#8242;s<br />
of new TLDs.<br />
.stock .oracle .print .company .Airport .BLOG .town .hockey<br />
.Tobacco .tools .business .brokers .hire .logo .peace .date .pool .Bowling .Dolls .dream .game .Boxing .nutrition .bob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vouchers</title>
		<link>http://blog.icann.org/2009/05/so-where-are-we-up-to-with-these-new-internet-extensions/comment-page-1/#comment-18132</link>
		<dc:creator>vouchers</dc:creator>
		<pubDate>Tue, 07 Jul 2009 04:21:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=794#comment-18132</guid>
		<description>Yes, What the announcement last week highlighted was that ICANN actively wasn’t going full speed ahead. In fact, the usual run of events - where documents are revised in full for each new meeting - was purposefully stepped away from.

Signed by &lt;a href=&quot;http://www.vouchersmarter.co.uk/retailer/comet.co.uk&quot; rel=&quot;nofollow&quot;&gt;Comet Vouchers&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Yes, What the announcement last week highlighted was that ICANN actively wasn’t going full speed ahead. In fact, the usual run of events &#8211; where documents are revised in full for each new meeting &#8211; was purposefully stepped away from.</p>
<p>Signed by <a href="http://www.vouchersmarter.co.uk/retailer/comet.co.uk" rel="nofollow">Comet Vouchers</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kieren McCarthy</title>
		<link>http://blog.icann.org/2009/05/so-where-are-we-up-to-with-these-new-internet-extensions/comment-page-1/#comment-17720</link>
		<dc:creator>Kieren McCarthy</dc:creator>
		<pubDate>Mon, 08 Jun 2009 19:30:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=794#comment-17720</guid>
		<description>@ David: Yes, you are right - and that is why ICANN has been working hand-in-hand with the community for nearly two years on a registry continuity program. 

The program is designed to ensure that registrants are not disadvantaged by the possible future collapse of a registry. 

A link to the program is available on the front page of the ICANN website. You can go to it directly at &lt;a href=&quot;http://www.icann.org/en/registries/continuity/&quot; rel=&quot;nofollow&quot;&gt;http://www.icann.org/en/registries/continuity/&lt;/a&gt;.


Kieren</description>
		<content:encoded><![CDATA[<p>@ David: Yes, you are right &#8211; and that is why ICANN has been working hand-in-hand with the community for nearly two years on a registry continuity program. </p>
<p>The program is designed to ensure that registrants are not disadvantaged by the possible future collapse of a registry. </p>
<p>A link to the program is available on the front page of the ICANN website. You can go to it directly at <a href="http://www.icann.org/en/registries/continuity/" rel="nofollow">http://www.icann.org/en/registries/continuity/</a>.</p>
<p>Kieren</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://blog.icann.org/2009/05/so-where-are-we-up-to-with-these-new-internet-extensions/comment-page-1/#comment-17676</link>
		<dc:creator>David</dc:creator>
		<pubDate>Sat, 06 Jun 2009 23:08:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=794#comment-17676</guid>
		<description>Another potential problem:  Say I am starting a business and purchase a domain name on a new extension: mybusiness.wxyz.  So I print letterheads, purchase directory listings, and spend a lot of money advertising my new website with the .wxyz extension. A couple years later, perhaps in a recession, the company owning the .wxyz extension doesn&#039;t sell enough domains and goes bankrupt. No other company wants to take over the extension because it is losing money.  I would have to rebrand my website on another extension, at enormous cost in advertising. Customers would not find me at the URL that they expected and would go to the competition.  I would very nearly have to start over.

“if it works, get it out there and make changes later”     
The problem with this approach is that those who trusted and bought into those extensions that &quot;don&#039;t work&quot; are in deep trouble. There is absolutely no reason to rush and every reason to proceed with caution.</description>
		<content:encoded><![CDATA[<p>Another potential problem:  Say I am starting a business and purchase a domain name on a new extension: mybusiness.wxyz.  So I print letterheads, purchase directory listings, and spend a lot of money advertising my new website with the .wxyz extension. A couple years later, perhaps in a recession, the company owning the .wxyz extension doesn&#8217;t sell enough domains and goes bankrupt. No other company wants to take over the extension because it is losing money.  I would have to rebrand my website on another extension, at enormous cost in advertising. Customers would not find me at the URL that they expected and would go to the competition.  I would very nearly have to start over.</p>
<p>“if it works, get it out there and make changes later”<br />
The problem with this approach is that those who trusted and bought into those extensions that &#8220;don&#8217;t work&#8221; are in deep trouble. There is absolutely no reason to rush and every reason to proceed with caution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete Trent</title>
		<link>http://blog.icann.org/2009/05/so-where-are-we-up-to-with-these-new-internet-extensions/comment-page-1/#comment-17431</link>
		<dc:creator>Pete Trent</dc:creator>
		<pubDate>Fri, 22 May 2009 01:56:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=794#comment-17431</guid>
		<description>My issue is that I launched a .com &lt;a href=&quot;http://xn--12c8d1a4fxc.com&quot; rel=&quot;nofollow&quot;&gt;IDN site&lt;/a&gt;, almost 3 years ago, and was told by many parties &quot;full IDNs are coming soon&quot;. Well,  3 years later we are still being told the same thing. 

From where we stand, the launch of &quot;full IDNs&quot; has been held back precisely because they are tied into this wonderfully all-encompassing ICANN policy of gTLD expansion.

Why not separate them out? Whilst the need for this general rapid expansion is very debatle, there is absolutely no debate the world needs IDNs, and soon.

thanks,</description>
		<content:encoded><![CDATA[<p>My issue is that I launched a .com <a href="http://xn--12c8d1a4fxc.com" rel="nofollow">IDN site</a>, almost 3 years ago, and was told by many parties &#8220;full IDNs are coming soon&#8221;. Well,  3 years later we are still being told the same thing. </p>
<p>From where we stand, the launch of &#8220;full IDNs&#8221; has been held back precisely because they are tied into this wonderfully all-encompassing ICANN policy of gTLD expansion.</p>
<p>Why not separate them out? Whilst the need for this general rapid expansion is very debatle, there is absolutely no debate the world needs IDNs, and soon.</p>
<p>thanks,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SilverPyramid</title>
		<link>http://blog.icann.org/2009/05/so-where-are-we-up-to-with-these-new-internet-extensions/comment-page-1/#comment-17357</link>
		<dc:creator>SilverPyramid</dc:creator>
		<pubDate>Thu, 14 May 2009 21:18:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=794#comment-17357</guid>
		<description>I am about to purchase a website for my company, SilverPyramid designs. I just got out of college a year ago, and after serving a short internship, and a small web design job, Im starting my own buisness. As it is a web design company, it fits to have a site... But my question is, where would I go about purchasing one of these things. Say... dot-sp or something along those lines. Could you clarify?</description>
		<content:encoded><![CDATA[<p>I am about to purchase a website for my company, SilverPyramid designs. I just got out of college a year ago, and after serving a short internship, and a small web design job, Im starting my own buisness. As it is a web design company, it fits to have a site&#8230; But my question is, where would I go about purchasing one of these things. Say&#8230; dot-sp or something along those lines. Could you clarify?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NameTalent.com &#187; Blog Archive &#187; ICANN and the New gTLD&#8217;s</title>
		<link>http://blog.icann.org/2009/05/so-where-are-we-up-to-with-these-new-internet-extensions/comment-page-1/#comment-17323</link>
		<dc:creator>NameTalent.com &#187; Blog Archive &#187; ICANN and the New gTLD&#8217;s</dc:creator>
		<pubDate>Tue, 12 May 2009 20:16:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=794#comment-17323</guid>
		<description>[...] is a quote from the the ICANN blogger Keiran McCarthy from the post titled &#8220;So where are we up to with these new Internet extensions?&#8221; on the official ICANN blog.  The “new gTLD program” envisions a very significant increase in [...]</description>
		<content:encoded><![CDATA[<p>[...] is a quote from the the ICANN blogger Keiran McCarthy from the post titled &#8220;So where are we up to with these new Internet extensions?&#8221; on the official ICANN blog.  The “new gTLD program” envisions a very significant increase in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kieren McCarthy</title>
		<link>http://blog.icann.org/2009/05/so-where-are-we-up-to-with-these-new-internet-extensions/comment-page-1/#comment-17322</link>
		<dc:creator>Kieren McCarthy</dc:creator>
		<pubDate>Tue, 12 May 2009 15:43:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=794#comment-17322</guid>
		<description>&lt;a href=&quot;http://blog.icann.org/2009/05/so-where-are-we-up-to-with-these-new-internet-extensions/#comment-17316&quot; rel=&quot;nofollow&quot;&gt;@ M. Menius&lt;/a&gt;: I agree with you and I think that is what ICANN - both organization and staff - are trying to do as we speak.

Back in February, four specific &quot;overarching issues&quot; that the community had pointed at as real concerns were pulled out and highlighted by staff so that the community could focus on finding solutions to them. Timelines were set back, plans were rearranged and the focus adjusted.

What the announcement last week highlighted was that ICANN actively wasn&#039;t going full speed ahead. In fact, the usual run of events - where documents are revised in full for each new meeting - was purposefully stepped away from. 

Rather than have a third version of the guidebook, the Sydney meeting will focus on the overarching issues and then those solutions will be pulled into a third version.

So, yes, I agree that if there is a large section of the community unhappy with a particular element then we do need to revisit it and come to a solution - and I think events have shown that ICANN as an organization is doing precisely that.

Of course there is a bigger, wider issue of culture here. ICANN was borne out of the technical community - the people that designed and built the Internet. And a core philosophy of that group is the idea of &quot;rough consensus and running code&quot; - which could also be translated as &quot;if it works, get it out there and make changes later&quot;. It is that approach that has made the Internet what it is today.

On the other side is the governmental approach which likes to have everything agreed to, considered, discussed and nailed down before it moves forward. This is a much more formal approach that has its advantages in that it is less messy but on the flipside it takes much, much longer. And with the pace of the Internet as it is, it is not suitable for making policy for the domain name system.

So ICANN is between the two - but with both sides intricately involved in its decision-making processes. So, again, it&#039;s noisy. But it does work.

Kieren</description>
		<content:encoded><![CDATA[<p><a href="http://blog.icann.org/2009/05/so-where-are-we-up-to-with-these-new-internet-extensions/#comment-17316" rel="nofollow">@ M. Menius</a>: I agree with you and I think that is what ICANN &#8211; both organization and staff &#8211; are trying to do as we speak.</p>
<p>Back in February, four specific &#8220;overarching issues&#8221; that the community had pointed at as real concerns were pulled out and highlighted by staff so that the community could focus on finding solutions to them. Timelines were set back, plans were rearranged and the focus adjusted.</p>
<p>What the announcement last week highlighted was that ICANN actively wasn&#8217;t going full speed ahead. In fact, the usual run of events &#8211; where documents are revised in full for each new meeting &#8211; was purposefully stepped away from. </p>
<p>Rather than have a third version of the guidebook, the Sydney meeting will focus on the overarching issues and then those solutions will be pulled into a third version.</p>
<p>So, yes, I agree that if there is a large section of the community unhappy with a particular element then we do need to revisit it and come to a solution &#8211; and I think events have shown that ICANN as an organization is doing precisely that.</p>
<p>Of course there is a bigger, wider issue of culture here. ICANN was borne out of the technical community &#8211; the people that designed and built the Internet. And a core philosophy of that group is the idea of &#8220;rough consensus and running code&#8221; &#8211; which could also be translated as &#8220;if it works, get it out there and make changes later&#8221;. It is that approach that has made the Internet what it is today.</p>
<p>On the other side is the governmental approach which likes to have everything agreed to, considered, discussed and nailed down before it moves forward. This is a much more formal approach that has its advantages in that it is less messy but on the flipside it takes much, much longer. And with the pace of the Internet as it is, it is not suitable for making policy for the domain name system.</p>
<p>So ICANN is between the two &#8211; but with both sides intricately involved in its decision-making processes. So, again, it&#8217;s noisy. But it does work.</p>
<p>Kieren</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ICANN: So Where Are We? -&#62; New TLD Extensions - NamePros.Com</title>
		<link>http://blog.icann.org/2009/05/so-where-are-we-up-to-with-these-new-internet-extensions/comment-page-1/#comment-17317</link>
		<dc:creator>ICANN: So Where Are We? -&#62; New TLD Extensions - NamePros.Com</dc:creator>
		<pubDate>Tue, 12 May 2009 06:11:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=794#comment-17317</guid>
		<description>[...] the link if interested in adding your comments (comments located at bottom of the ICANN post) ...   So where are we up to with these new Internet extensions?   __________________ PremiumDomains.biz -&gt; BLOG &#124; Manhattan.mobi &#124; Tampa.mobi &#124; Cincinnati.mobi [...]</description>
		<content:encoded><![CDATA[<p>[...] the link if interested in adding your comments (comments located at bottom of the ICANN post) &#8230;   So where are we up to with these new Internet extensions?   __________________ PremiumDomains.biz -&gt; BLOG | Manhattan.mobi | Tampa.mobi | Cincinnati.mobi [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

