<?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: Here&#8217;s how we enter the .future</title>
	<atom:link href="http://blog.icann.org/2008/10/heres-how-we-enter-the-future/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.icann.org/2008/10/heres-how-we-enter-the-future/</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: Kieren McCarthy</title>
		<link>http://blog.icann.org/2008/10/heres-how-we-enter-the-future/comment-page-1/#comment-15598</link>
		<dc:creator>Kieren McCarthy</dc:creator>
		<pubDate>Mon, 05 Jan 2009 17:35:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=380#comment-15598</guid>
		<description>&lt;strong&gt;&lt;a href=&quot;http://blog.icann.org/2008/10/heres-how-we-enter-the-future/#comment-15019&quot; rel=&quot;nofollow&quot;&gt;@ Dirk:&lt;/a&gt;&lt;/strong&gt; I&#039;m afraid we will not be translating the Applicant Guidebook into German - but we will have it in Arabic, Chinese (simplified), French, Spanish and Russian. 

If there is significant demand for the documents in German however, we would certainly review the request. As you know, Dirk, German is one of the 10 languages that ICANN supports (although not one of the five that we typically translate into).

Kieren</description>
		<content:encoded><![CDATA[<p><strong><a href="http://blog.icann.org/2008/10/heres-how-we-enter-the-future/#comment-15019" rel="nofollow">@ Dirk:</a></strong> I&#8217;m afraid we will not be translating the Applicant Guidebook into German &#8211; but we will have it in Arabic, Chinese (simplified), French, Spanish and Russian. </p>
<p>If there is significant demand for the documents in German however, we would certainly review the request. As you know, Dirk, German is one of the 10 languages that ICANN supports (although not one of the five that we typically translate into).</p>
<p>Kieren</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New domain extensions - gTLDs - how they'll work &#124; Inside 123-reg</title>
		<link>http://blog.icann.org/2008/10/heres-how-we-enter-the-future/comment-page-1/#comment-15051</link>
		<dc:creator>New domain extensions - gTLDs - how they'll work &#124; Inside 123-reg</dc:creator>
		<pubDate>Tue, 11 Nov 2008 13:32:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=380#comment-15051</guid>
		<description>[...] background on the draft guidebook from the ICANN [...]</description>
		<content:encoded><![CDATA[<p>[...] background on the draft guidebook from the ICANN [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dirk Krischenowski</title>
		<link>http://blog.icann.org/2008/10/heres-how-we-enter-the-future/comment-page-1/#comment-15019</link>
		<dc:creator>Dirk Krischenowski</dc:creator>
		<pubDate>Thu, 30 Oct 2008 08:21:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=380#comment-15019</guid>
		<description>Will the Draft Applicant Guidebook also available in German language one day?

For any interested party we made a German summary at:

http://www.citytld.com/pdf/Fakten-zu-den-neuen-Top-Level-Domains.pdf</description>
		<content:encoded><![CDATA[<p>Will the Draft Applicant Guidebook also available in German language one day?</p>
<p>For any interested party we made a German summary at:</p>
<p><a href="http://www.citytld.com/pdf/Fakten-zu-den-neuen-Top-Level-Domains.pdf" rel="nofollow">http://www.citytld.com/pdf/Fakten-zu-den-neuen-Top-Level-Domains.pdf</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Southland.LA</title>
		<link>http://blog.icann.org/2008/10/heres-how-we-enter-the-future/comment-page-1/#comment-15018</link>
		<dc:creator>Southland.LA</dc:creator>
		<pubDate>Thu, 30 Oct 2008 07:24:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=380#comment-15018</guid>
		<description>We  at Southland.LA welcome the addition of Dot-City GeoTLDs.  Finally, Dot-LA is going to have some company throughout the world.  Go Dot-City GeoTLDs.  ICANN&#039;s latest decisions certainly vindicate LA Names Corporation&#039;s vision on Dot-City GeoTLDs.  Visit http://www.www.la/ for more information on Dot-LA.</description>
		<content:encoded><![CDATA[<p>We  at Southland.LA welcome the addition of Dot-City GeoTLDs.  Finally, Dot-LA is going to have some company throughout the world.  Go Dot-City GeoTLDs.  ICANN&#8217;s latest decisions certainly vindicate LA Names Corporation&#8217;s vision on Dot-City GeoTLDs.  Visit <a href="http://www.www.la/" rel="nofollow">http://www.www.la/</a> for more information on Dot-LA.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kieren McCarthy</title>
		<link>http://blog.icann.org/2008/10/heres-how-we-enter-the-future/comment-page-1/#comment-15015</link>
		<dc:creator>Kieren McCarthy</dc:creator>
		<pubDate>Tue, 28 Oct 2008 21:53:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=380#comment-15015</guid>
		<description>Well, yes, if someone considers that &quot;.future&quot; is a serious enough prospect to put forward $180,000 for the application, invest hundreds of thousands more in building a robust infrastructure and deal with all the issues that arise from running a core piece of the Internet&#039;s naming system.

If they do that, then you as a consumer may be able to register the domain &quot;startrek.future&quot; for roughly $6. The name &quot;future&quot; might just be exciting enough for someone to put in the time and resources needed to get it and run it,  but I fear that even if &quot;.future&quot; is created, you are going to have a very hard time getting hold of &quot;startrek.future&quot;. 

As for &quot;rushlimbaugh.ignoramus&quot;, I am afraid you are going to have to let this particular dream go. Not that there aren&#039;t enough ignoramuses in the world for it to herald enough demand, but I just have the feeling no one is going to be in a rush to go through the application process for a word whose meaning can be much more effectively portrayed with a shorter, punchier piece of English.

As for &quot;joemescher.genius&quot;. Well, that&#039;s a 50-50. There may well be enough people willing to have their statuses immortalised online that this is viable. If it ends up a community top-level domain, if you want &quot;joemescher.genius&quot; you may need to prove your super-high intelligence in order to be allowed it - but I have no doubt being a genius that you have already got that covered.

The serious point of course is that this process is not just a matter of typing a domain into a box and clicking &quot;register&quot; if it&#039;s available.

In many ways, the simplicity of registering a domain these days makes it all look too easy. (That simplicity, incidentally, comes a result of the competitive market measures that ICANN introduced and has overseen for a decade.) But there are enormously complex systems and thousands of highly-trained personnel at work behind the scenes.

Running a part of the Internet addressing system is not for the faint-hearted. It is a serious and complex endeavour. But, hopefully, there are some people out there who think it is worth it. People who understand that with the responsibility and complexity comes the opportunity to help define the next revolution of the Internet and with it, define our future as a race on this planet.


Kieren</description>
		<content:encoded><![CDATA[<p>Well, yes, if someone considers that &#8220;.future&#8221; is a serious enough prospect to put forward $180,000 for the application, invest hundreds of thousands more in building a robust infrastructure and deal with all the issues that arise from running a core piece of the Internet&#8217;s naming system.</p>
<p>If they do that, then you as a consumer may be able to register the domain &#8220;startrek.future&#8221; for roughly $6. The name &#8220;future&#8221; might just be exciting enough for someone to put in the time and resources needed to get it and run it,  but I fear that even if &#8220;.future&#8221; is created, you are going to have a very hard time getting hold of &#8220;startrek.future&#8221;. </p>
<p>As for &#8220;rushlimbaugh.ignoramus&#8221;, I am afraid you are going to have to let this particular dream go. Not that there aren&#8217;t enough ignoramuses in the world for it to herald enough demand, but I just have the feeling no one is going to be in a rush to go through the application process for a word whose meaning can be much more effectively portrayed with a shorter, punchier piece of English.</p>
<p>As for &#8220;joemescher.genius&#8221;. Well, that&#8217;s a 50-50. There may well be enough people willing to have their statuses immortalised online that this is viable. If it ends up a community top-level domain, if you want &#8220;joemescher.genius&#8221; you may need to prove your super-high intelligence in order to be allowed it &#8211; but I have no doubt being a genius that you have already got that covered.</p>
<p>The serious point of course is that this process is not just a matter of typing a domain into a box and clicking &#8220;register&#8221; if it&#8217;s available.</p>
<p>In many ways, the simplicity of registering a domain these days makes it all look too easy. (That simplicity, incidentally, comes a result of the competitive market measures that ICANN introduced and has overseen for a decade.) But there are enormously complex systems and thousands of highly-trained personnel at work behind the scenes.</p>
<p>Running a part of the Internet addressing system is not for the faint-hearted. It is a serious and complex endeavour. But, hopefully, there are some people out there who think it is worth it. People who understand that with the responsibility and complexity comes the opportunity to help define the next revolution of the Internet and with it, define our future as a race on this planet.</p>
<p>Kieren</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Mescher</title>
		<link>http://blog.icann.org/2008/10/heres-how-we-enter-the-future/comment-page-1/#comment-15008</link>
		<dc:creator>Joe Mescher</dc:creator>
		<pubDate>Mon, 27 Oct 2008 17:56:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=380#comment-15008</guid>
		<description>Amazing.  So now we&#039;ll be seeing &#039;www.startrek.future&#039; or &#039;www.rushlimbaugh.ignormaus&#039;?

Can&#039;t wait to register &#039;www.joemescher.genius&#039;.</description>
		<content:encoded><![CDATA[<p>Amazing.  So now we&#8217;ll be seeing &#8216;www.startrek.future&#8217; or &#8216;www.rushlimbaugh.ignormaus&#8217;?</p>
<p>Can&#8217;t wait to register &#8216;www.joemescher.genius&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Is this the .future you were expecting? - PrimeDigit - A Design Blog by Will Shaver</title>
		<link>http://blog.icann.org/2008/10/heres-how-we-enter-the-future/comment-page-1/#comment-15007</link>
		<dc:creator>Is this the .future you were expecting? - PrimeDigit - A Design Blog by Will Shaver</dc:creator>
		<pubDate>Mon, 27 Oct 2008 17:07:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=380#comment-15007</guid>
		<description>[...] ICANN RFP for anything.* domain names. Might want to take a look. Most of you readers play in this here internets thing, this could effect you or the company you work for. :) [...]</description>
		<content:encoded><![CDATA[<p>[...] ICANN RFP for anything.* domain names. Might want to take a look. Most of you readers play in this here internets thing, this could effect you or the company you work for. <img src='http://blog.icann.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ICANN-Guidebook für neue Top-Level-Domains. &#124; blog@netplanet</title>
		<link>http://blog.icann.org/2008/10/heres-how-we-enter-the-future/comment-page-1/#comment-14997</link>
		<dc:creator>ICANN-Guidebook für neue Top-Level-Domains. &#124; blog@netplanet</dc:creator>
		<pubDate>Sat, 25 Oct 2008 21:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=380#comment-14997</guid>
		<description>[...] ICANN Blog]   Bookmarken:  sociallist_90deb1bf_url = [...]</description>
		<content:encoded><![CDATA[<p>[...] ICANN Blog]   Bookmarken:  sociallist_90deb1bf_url = [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Waterproof Gem -red</title>
		<link>http://blog.icann.org/2008/10/heres-how-we-enter-the-future/comment-page-1/#comment-14995</link>
		<dc:creator>Waterproof Gem -red</dc:creator>
		<pubDate>Sat, 25 Oct 2008 05:30:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=380#comment-14995</guid>
		<description>[...] Here&#8217;s how we enter the .future(25 October 2008) So, after years of policy and development work, yesterday ICANN released a draft version of the Applicant Guidebook for those interested in applying f... [...]</description>
		<content:encoded><![CDATA[<p>[...] Here&#8217;s how we enter the .future(25 October 2008) So, after years of policy and development work, yesterday ICANN released a draft version of the Applicant Guidebook for those interested in applying f&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kieren McCarthy</title>
		<link>http://blog.icann.org/2008/10/heres-how-we-enter-the-future/comment-page-1/#comment-14994</link>
		<dc:creator>Kieren McCarthy</dc:creator>
		<pubDate>Fri, 24 Oct 2008 21:08:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=380#comment-14994</guid>
		<description>Hi George, 

This is in reference to a posting and comment on Circle ID (http://www.circleid.com/posts/20081024_verisign_tiered_domain_pricing_soon/)

I&#039;ll post the same comment here as there: my response to you was only with regard to your specific comment about price controls on sponsored and unsponsored TLDs. 

As to your wider question about whether the wording could in future allow for existing registries to ask for changes in their contracts, well that&#039;s what this public comment period is for. 

You are raising a theoretical future possibility based on draft documents. The answer to that is always going to be: raise it as part of the public comment process and the community can discuss it.

As you know, since I can see you have already posted your point there (thank you btw), as your point concerns the draft base agreement, the best email address for sending a public comment is gtld-transition@icann.org and you an view all comments on this issue at http://forum.icann.org/lists/gtld-transition/.

Thanks again George, this sort of review where not only the documents themselves but also the potential future impacts of what they contain are discussed is exactly the sort of thing that this public comment period hopes to elicit.


Kieren</description>
		<content:encoded><![CDATA[<p>Hi George, </p>
<p>This is in reference to a posting and comment on Circle ID (<a href="http://www.circleid.com/posts/20081024_verisign_tiered_domain_pricing_soon/" rel="nofollow">http://www.circleid.com/posts/20081024_verisign_tiered_domain_pricing_soon/</a>)</p>
<p>I&#8217;ll post the same comment here as there: my response to you was only with regard to your specific comment about price controls on sponsored and unsponsored TLDs. </p>
<p>As to your wider question about whether the wording could in future allow for existing registries to ask for changes in their contracts, well that&#8217;s what this public comment period is for. </p>
<p>You are raising a theoretical future possibility based on draft documents. The answer to that is always going to be: raise it as part of the public comment process and the community can discuss it.</p>
<p>As you know, since I can see you have already posted your point there (thank you btw), as your point concerns the draft base agreement, the best email address for sending a public comment is <a href="mailto:gtld-transition@icann.org">gtld-transition@icann.org</a> and you an view all comments on this issue at <a href="http://forum.icann.org/lists/gtld-transition/" rel="nofollow">http://forum.icann.org/lists/gtld-transition/</a>.</p>
<p>Thanks again George, this sort of review where not only the documents themselves but also the potential future impacts of what they contain are discussed is exactly the sort of thing that this public comment period hopes to elicit.</p>
<p>Kieren</p>
]]></content:encoded>
	</item>
</channel>
</rss>
