ICANN posts summary/analysis of .xxx comments
 

ICANN has posted a summary and analysis of the .xxx public comments:

http://forum.icann.org/lists/xxx-rev.../msg00723.html

(the link to the PDF attachment gets randomized every few minutes, so you don't want to link directly to that)

It's a good primer for those who want to get up to speed on the issues, or see if their own comments were summarized properly. I found it amusing that 448 of the 455 comments in favour of .xxx were "webform/standard form submissions" (see the table on page 11).

The next ICANN Board meeting is on October 28:

http://www.icann.org/en/minutes/agenda-28oct10-en.htm

and .xxx is on the agenda (item #8), but ICANN isn't expected to actually do anything until they've received advice from the GAC (i.e. the Governmental Advisory Committee). You can see a list of those GAC members at:

http://gac.icann.org/gac-members

Supposedly a "final" decision will be made at the Catagena meeting in December:

http://cartagena39.icann.org/

but who knows for sure......certainly the losing side will appeal or sue in court.

any more comments from Rod Beckstrom?

Even if the manage to pull it through, no one is gonna use .xxx It's stupid. Just like it was with the .co - all hype.

Not to my knowledge. I think the only other "news" out of ICANN was the denial of FSC's request for more information, see:

http://dotxxxopposition.com/2010/10/...-info-request/

http://www.icann.org/en/corresponden...08sep10-en.pdf (initial request)

sadly, politicians are already talking about making it mandatory for adult content (whatever the definition of adult content may be).

nah, there is no way to enforce that.

At the Federal level, probably not. Enforcement via local community standards in various jurisdictions maybe, though that would be a stretch.

However, via corporate policy, .XXX would be a cinch to enforce.

Payment processors, which already enforce all sorts of rules on adult sites, could simply add another rule requiring adult sites to operate completely within a .XXX domain.

If that seems impossible, think again - payment processors already restrict the words that may be used in branding and the domain name, such as Lolita, Lolikon, YoungTeens, etc.

And the search engines could potentially get into the act too requiring adult sites seeking to advertise to be in .XXX, or even more extreme, to even be visible in the default search results.

Ron

Fight the .$$$!

Especially outside USA

There are a lot of things governments enforce these days, things people once considered unenforceable...

Why would they ask a governmental committee for advice? Seeing what close-minded control-freaks run governments these days, that's not a good idea.

Yep, for example, starting in the early 1990s, laws restricting the type of toilets one buy and install in their own home.

http://www.sepp.org/Archive/reality/lowflush.html

And beginning in 2012 regular traditional incandescent light bulbs will no longer be legally available. And sometime between 2014-2020, the restrictions are set to get even tighter with many "exempted" bulbs no longer be allowed either.

http://www.aboutlightingcontrols.org...ergy_law.shtml

Bottom line is the fear of laws requiring using .XXX is well justified - the government already restricts many things / activities that years ago, to reiterate the point the u-Bob makes, seemed improbable.

Never underestimate what the government can do - first assume the worst and then push back (ie. write comments to ICANN, etc) / plan accordingly (ie. be prepared to move into .xxx, if it comes to pass).

Ron

Don't forget to post on every domaining blog or forum out there. On mosts blogs you don't need to register to comment. Leaving a small comment about how you are part of the adult industry and don't like the .xxx tld will only take a minute of one's time, but will do a lot to spread the message.

Don't go silently into the night!

ICANN = Greed

Judging from the comments, I perceive a credibility problem for ICM.

95+% of the "yes go ahead"-votes came from their servers... That should tell ICANN enough...