NameStarter.com :: domaining business blog // Domaining for Domainers

Archive for the ‘.xxx’ Category

“No Porn!” Shout Families to ICANN

Anti-porn group mobilized against .xxx.

If ICANN is supposed to include the thoughts of the greater internet community, it is certainly getting its wish.

Focus on the Family Some advocacy group — whether it be a religious right organization, parents organization, or someone else – has lit a fire under dozens of people to submit comments to ICANN regarding .xxx.

The comment period for the procedural issues around reconsidering ICM Registry’s .xxx application opened yesterday, and already there are over 50 comments. Subject lines include:

“Re: against porn web domains”
“PLEASE STOP EXPOSING OUR CHILDREN TO PORN!!”
“.XXX Comments READ THIS”
“No on pornography!! ”
“Are You Crazy”

From reading the comments, I don’t think most people understand the issue. Here’s one comment:

I am writing to encourage those who are involved in considering making a xxx domain to please think about the devastating affects of porn on families and individuals. I have seen porn and the addiction that some people develop to it destroy families and relationships. Creating an xxx domain will not help protect people, but will make a smooth path for even more hurt and destruction. Think about the hurt and the pain and then think about your place in possibly allowing more.

and

WE WISH THAT OUR CHILDREN WON BE EXPOSES TO SUCH NASTY HURTFUL THING ” PORNOGRAPHY’

and

Just want you to know, that pornography has caused lots of problems in our marriage. If that’s not your intention, please do not create more problem by trying to create this dot xxx thing.

May God bless you with wisdom in making such important decision.

Apparently God is getting involved with ICANN decisions these days. That should certainly speed things up.

OK, I get it. You’re opposed to porn. But creating a .xxx domain name isn’t going to result in more porn on the web. And your internet filters can easily block this porn — unlike what exists on other top level domain names.

Perhaps my favorite comment is the one that asks ICANN to “go with its initial gut feeling”, which the author says was to deny .xxx. Actually, its initial decision was to approve .xxx. Only later did it backtrack, which is why ICANN is in this mess with ICM to begin with.


© DomainNameWire.com 2009.

Review and rate domain name parking companies at Parking Judge.

Related posts:

  1. ICANN Gives New Life to .XXX Domain
  2. Commentless Comment Periods at ICANN
  3. My ICANN New gTLD Applicant Guidebook Version 2 Feedback

.XXX Registry to ICANN: “We Must Protect Our Rights”

February 27, 2010.xxx, Domaining, Domainnamewire, icann, icm registry, Policy & LawComments Off

ICM Registry notifies ICANN of its hopes and intentions.

Fresh off an independent review victory over ICANN, .XXX top level domain name applicant ICM Registry is asking ICANN to get the show on the road.

In a letter (pdf) to ICANN chairman of the board Peter Dengate-Thrush, ICM chairman Stuart Lawley writes:

“I am hopeful, as are others in the community, that ICANN will embrace the communications of the panel and use them to improve its processes and to restore confidence in ICANN as an institution.”

Lawley said time is of the essence for ICANN to regain institutional confidence:

“Assuming, as I do, that the Board takes its obligations under the accountability provisions of the Bylaws seriously and will respect the conclusions of this Panel of preeminent international jurists, we believe that it is now incumbent on ICANN to move expeditiously to execute a registry agreement with ICM for operation of the .xxx top level domain.”

And if ICANN doesn’t act expeditiously to get a contract in place with ICM registry? It probably faces a lawsuit:

“ICM is mindful that our patience has not always been rewarded in the past and can see no purpose (other than the expenditure of yet more time, money and effort by both parties) that would be served by delay. Accordingly, and with respect, I hope you will understand that we must protect our rights if it appears that our efforts to work in partnership with ICANN are failing, once again, to bear fruit.”

My guess is ICANN either approves the agreement or pays off ICM registry to go away until the new gTLD round gets going.


© DomainNameWire.com 2009.

Review and rate domain name parking companies at Parking Judge.

Related posts:

  1. ICM Registry Hopes to Offer .XXX Domains This Year
  2. ICANN to Hold Live Consultation on New gTLD Registry Agreement
  3. ICANN Seeks Fix for Registry Failure

ICM Registry Hopes to Offer .XXX Domains This Year

February 22, 2010.xxx, Domaining, Domainnamewire, icm registry, Policy & LawComments Off

Registry wants to offer name.xxx later this year.

After winning an independent review against ICANN for denying ICM Registry’s application for a .xxx top level domain name, the registry says it hopes to begin offering .xxx domain names later this year. It has already opened up a process on its web site to pre-reserve names.

Whether or not this time line is feasible depends in part on how ICANN’s board acts upon the independent review. In a strange version of accountability, ICANN’s board gets to review the outside arbitrator’s decision on the matter and decide if it should accept it. But it’s ICANN’s board that voted down .xxx to begin with.

The history here is long. But essentially, ICM registry applied to operate a .xxx top level domain name. By all accounts and a board vote, it met all of ICANN’s requirements and should have been awarded the TLD. The board authorized entering into negotiations with ICM for the registry. But the board then reconsidered it and voted it down because of pressure from outside groups including the U.S. Government.

The best case scenario for .xxx is that the ICANN board approves entering into a registry agreement with ICM registry during its Nairobi meeting next month.


© DomainNameWire.com 2009.

Review and rate domain name parking companies at Parking Judge.

Related posts:

  1. Domain Registries Clarify Stance on Registry-Registrar Separation
  2. Verisign to retain .net
  3. ICANN Seeks Fix for Registry Failure