<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/">
<channel>
<title>Techdirt. Stories about &quot;icm&quot;</title>
<description>Easily digestible tech news...</description>
<link>http://www.techdirt.com/</link>
<language>en-us</language>
<image><title>Techdirt. Stories about &quot;icm&quot;</title><url>http://www.techdirt.com/images/td-88x31.gif</url><link>http://www.techdirt.com/</link></image>
<item>
<pubDate>Wed, 23 Nov 2011 11:09:06 PST</pubDate>
<title>ICANN Sued Over .xxx; Porn Company Points Out That It's A Pure Money Grab</title>
<dc:creator>Mike Masnick</dc:creator>
<link>http://www.techdirt.com/articles/20111123/02272116882/icann-sued-over-xxx-porn-company-points-out-that-its-pure-money-grab.shtml</link>
<guid>http://www.techdirt.com/articles/20111123/02272116882/icann-sued-over-xxx-porn-company-points-out-that-its-pure-money-grab.shtml</guid>
<description><![CDATA[ With .xxx domains now available, we've noted how organizations were <a href="http://www.techdirt.com/articles/20111114/11220716766/universities-buying-up-xxx-domains-to-stop-porn-sites-showing-once-again-that-xxx-is-pure-money-grab.shtml">snapping them up</a> not because they want to create porn websites, but because they <i>don't</i> want porn sites under their name.  Of course, that just highlights the key problem with any new TLD: they become a total <a href="http://www.techdirt.com/articles/20041213/1526210.shtml">cash grab</a> by ICANN and whoever manages the TLD.  It's even worse with .xxx, since many organizations feel they <i>need</i> to grab their brands on that to prevent any connection to porn.
<br /><br />
Even worse, it appears that the registrar handling .xxx, ICM recognizes this and is even <a href="http://www.law.com/jsp/cc/PubArticleCC.jsp?id=1202533104723&#038;Porno_and_Madison_Avenue_Strange_Bedfellows" target="_blank">advertising with that in mind</a>:
<blockquote><i>
When the sellers of .xxx domain names put them on sale last week, they did not address their marketing campaigns just to adult content owners. Instead, they ran ads with headlines like ".XXX LANDRUSH IS NOW OPEN. PROTECT YOUR BRAND" or "SECURE YOUR DOMAIN. PROTECT YOUR REPUTATION," By heeding their warnings, brands, universities, and individuals flocked to the sites of domain name sellers and bought up tens of thousands of names, at about $200 per name. According to press reports, more than 70,000 applications have been received since the doors opened, netting sellers more than $15 million barely out of the gate. 
</i></blockquote>
Basically, the company admits that this is a borderline shakedown: if you want to "protect" yourself from someone building a porn site with your brand, pay up.
<br /><br />
The whole thing appears to have angered online porn giant Manwin Licensing International, who is now <a href="http://news.cnet.com/8301-13506_3-57326708-17/xxx-marks-the-lawsuit-from-peeved-porn-giant/" target="_blank">suing ICANN and ICM</a> saying that the whole thing is about "monopolistic conduct, price gouging, and anticompetitive and unfair practices."  I would imagine that in any such lawsuit, ICM's advertising practices around the "buy up or else" won't look too good...<br /><br /><a href="http://www.techdirt.com/articles/20111123/02272116882/icann-sued-over-xxx-porn-company-points-out-that-its-pure-money-grab.shtml">Permalink</a> | <a href="http://www.techdirt.com/articles/20111123/02272116882/icann-sued-over-xxx-porn-company-points-out-that-its-pure-money-grab.shtml#comments">Comments</a> | <a href="http://www.techdirt.com/articles/20111123/02272116882/icann-sued-over-xxx-porn-company-points-out-that-its-pure-money-grab.shtml?op=sharethis">Email This Story</a><br />
 ]]></description>
<slash:department>moneygrab.xxx</slash:department>
<wfw:commentRss>http://www.techdirt.com/comment_rss.php?sid=20111123/02272116882</wfw:commentRss>
</item>
<item>
<pubDate>Mon, 22 Feb 2010 12:54:28 PST</pubDate>
<title>Independent Review Finds ICANN Screwed Up In Approving... Then Rejecting .xxx</title>
<dc:creator>Mike Masnick</dc:creator>
<link>http://www.techdirt.com/articles/20100222/0253398249.shtml</link>
<guid>http://www.techdirt.com/articles/20100222/0253398249.shtml</guid>
<description><![CDATA[ If you haven't followed the .xxx saga, it's been a bit convoluted.  While it's still not at all clear why we need top level domains at all any more (or, if we must have them, why they should be limited to the ones chosen by ICANN), for many years, ICANN has been in charge of reviewing various proposals to expand the available top level domains (things like .com, .net, .org, etc.).  That's how we got other such useless TLDs like .info, .jobs and .mobi -- which have mostly just turned into money grabs for the companies that operate them, rather than anything that was really needed.  .xxx is the same story.  Obviously, it's a huge money grab, because whoever would operate it would stand to <a href="http://www.techdirt.com/articles/20040322/090206.shtml">rake in the cash</a> from porn operators looking to set up new sites.  While ICANN initially rejected the proposal at the beginning of the decade, the guy behind .xxx tried again, and in 2005, ICANN <a href="http://www.techdirt.com/articles/20050601/185234.shtml">agreed</a> that .xxx met all the criteria and should be allowed.
<br /><br />
So why doesn't the internet yet have this official redlight district?
<br /><br />
Well, what really happened was that "protect the children"-type family groups freaked out about admitting to the fact that (gasp!) porn exists on the internet.  Amusingly, some of those same groups and their favorite politicians had <a href="http://www.techdirt.com/articles/20060317/0223255.shtml">pushed for .xxx anyway</a>, in an effort to <i>force</i> all porn to be located there.  But, for some reason, <i>after</i> .xxx was approved, they suddenly freaked out that this somehow meant porn was okay, and started causing trouble.   Suddenly, months after ICANN had already approved .xxx, the federal government (under whose umbrella ICANN kinda-sorta belonged) suggested rather strongly that <a href="http://techdirt.com/articles/20051201/1325225_F.shtml">.xxx was not a good idea</a>.  Suddenly, everything was put on hold, and in 2007, ICANN officially <a href="http://www.techdirt.com/articles/20070330/101213.shtml">said no</a> to .xxx. 
<br /><br />
This infuriated the folks behind .xxx, a group called ICM, and they asked for an independent dispute resolution, which was released last Friday.  So, after all these many years, the review found <a href="http://www.thedomains.com/2010/02/20/report-finds-against-icann-in-denying-the-xxx-extension-charges-them-the-475k-cost/" target="_blank">that ICANN totally screwed up</a>, and it never should have backed down after its 2005 approval of .xxx.  It's also demanding that ICANN pay up for this review process, in the range of half a million dollars.  Of course, the ruling is non-binding, so it doesn't necessarily mean that ICANN now does need to approve .xxx, but it makes it harder to explain why it hasn't.  Also complicating matters is ICANN's more recent decision to let pretty much anyone with a ton of cash to throw away <a href="http://www.techdirt.com/articles/20080626/1301511528.shtml">create their own TLD</a>.  So, perhaps the .xxx guys can just do that...<br /><br /><a href="http://www.techdirt.com/articles/20100222/0253398249.shtml">Permalink</a> | <a href="http://www.techdirt.com/articles/20100222/0253398249.shtml#comments">Comments</a> | <a href="http://www.techdirt.com/articles/20100222/0253398249.shtml?op=sharethis">Email This Story</a><br />
 ]]></description>
<slash:department>who-did-what-now?</slash:department>
<wfw:commentRss>http://www.techdirt.com/comment_rss.php?sid=20100222/0253398249</wfw:commentRss>
</item>
</channel>
</rss>