<?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: New Life for .XXX &#8212; but Hurdles Remain</title>
	<atom:link href="http://domainnamewire.com/2008/10/29/new-life-for-xxx-but-hurdles-remain/feed/" rel="self" type="application/rss+xml" />
	<link>http://domainnamewire.com/2008/10/29/new-life-for-xxx-but-hurdles-remain/</link>
	<description>News and Views for the Domain Name Industry</description>
	<lastBuildDate>Sat, 21 Nov 2009 04:58:31 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Matthew Diehl</title>
		<link>http://domainnamewire.com/2008/10/29/new-life-for-xxx-but-hurdles-remain/comment-page-1/#comment-270214</link>
		<dc:creator>Matthew Diehl</dc:creator>
		<pubDate>Thu, 30 Oct 2008 14:35:12 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=2942#comment-270214</guid>
		<description>Andrew - good point on the bottleneck that could be created by the registrars boycotting or having a reservation in offering domains on adult or &quot;bad&quot; TLDs. It is also beneficial to point out that similar bottlenecks could be implemented by ISPs or browser companies. ISPs could choose not to update their DNS systems to resolve domains that end in .killthepresident (for example) or non-open source browsers can reject that as a valid domain.</description>
		<content:encoded><![CDATA[<p>Andrew &#8211; good point on the bottleneck that could be created by the registrars boycotting or having a reservation in offering domains on adult or &#8220;bad&#8221; TLDs. It is also beneficial to point out that similar bottlenecks could be implemented by ISPs or browser companies. ISPs could choose not to update their DNS systems to resolve domains that end in .killthepresident (for example) or non-open source browsers can reject that as a valid domain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://domainnamewire.com/2008/10/29/new-life-for-xxx-but-hurdles-remain/comment-page-1/#comment-270196</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 30 Oct 2008 13:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=2942#comment-270196</guid>
		<description>Just thought of something else.  Even if someone gets a controversial TLD, they&#039;ll have to convince registrars to offer it to customers.  That&#039;s not likely if it&#039;s controversial.</description>
		<content:encoded><![CDATA[<p>Just thought of something else.  Even if someone gets a controversial TLD, they&#8217;ll have to convince registrars to offer it to customers.  That&#8217;s not likely if it&#8217;s controversial.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://domainnamewire.com/2008/10/29/new-life-for-xxx-but-hurdles-remain/comment-page-1/#comment-269938</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Wed, 29 Oct 2008 21:46:21 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=2942#comment-269938</guid>
		<description>jp - good point.  ICANN probably doesn&#039;t want the publicity of it though.  Right now if someone registers a &quot;bad&quot; domain like that, news articles callout the registrar about it.  If it&#039;s a TLD, they&#039;ll call out ICANN.</description>
		<content:encoded><![CDATA[<p>jp &#8211; good point.  ICANN probably doesn&#8217;t want the publicity of it though.  Right now if someone registers a &#8220;bad&#8221; domain like that, news articles callout the registrar about it.  If it&#8217;s a TLD, they&#8217;ll call out ICANN.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jp</title>
		<link>http://domainnamewire.com/2008/10/29/new-life-for-xxx-but-hurdles-remain/comment-page-1/#comment-269930</link>
		<dc:creator>jp</dc:creator>
		<pubDate>Wed, 29 Oct 2008 21:29:37 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=2942#comment-269930</guid>
		<description>All things being equal, they should allow any extension. So what you can register killthepresident.com, but not a tld .killthepresident? Thus the uniquely democratic nature of the internet right? Is this one of those times where adding regulation is bad, or good?</description>
		<content:encoded><![CDATA[<p>All things being equal, they should allow any extension. So what you can register killthepresident.com, but not a tld .killthepresident? Thus the uniquely democratic nature of the internet right? Is this one of those times where adding regulation is bad, or good?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://domainnamewire.com/2008/10/29/new-life-for-xxx-but-hurdles-remain/comment-page-1/#comment-269929</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Wed, 29 Oct 2008 21:27:08 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=2942#comment-269929</guid>
		<description>Michael, presumably the draft will be refined before people apply.  But yes, they need to include this specific issue before application fees are collected.</description>
		<content:encoded><![CDATA[<p>Michael, presumably the draft will be refined before people apply.  But yes, they need to include this specific issue before application fees are collected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Berkens</title>
		<link>http://domainnamewire.com/2008/10/29/new-life-for-xxx-but-hurdles-remain/comment-page-1/#comment-269926</link>
		<dc:creator>Michael Berkens</dc:creator>
		<pubDate>Wed, 29 Oct 2008 21:13:14 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=2942#comment-269926</guid>
		<description>Andrew

Here&#039;s the problem.

ICANN should take a public position on this now.

Otherwise you are going to have companies putting up $185K application fees, non-refundable.

If no &quot;adult&quot; extension are going to be approved based on moral grounds, ICANN needs to state so now.</description>
		<content:encoded><![CDATA[<p>Andrew</p>
<p>Here&#8217;s the problem.</p>
<p>ICANN should take a public position on this now.</p>
<p>Otherwise you are going to have companies putting up $185K application fees, non-refundable.</p>
<p>If no &#8220;adult&#8221; extension are going to be approved based on moral grounds, ICANN needs to state so now.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
