Home / Blogs

Latest Turn of Events on .XXX, from ICANN Wellington

As the ICANN’s week-long meeting in Wellington, New Zealand is now fully underway, the approval of the proposed .XXX top-level domain (TLD) continues to remain a key topic of discussion and its eventual approval yet uncertain. The .XXX TLD was widely expected to receive its final approval at the ICANN’s last meeting held in Vancouver about 4 months earlier but the discussion was unexpectedly delayed as the organization and governments requested more time to review the merits of setting up such a domain.

“The DoC [US Department of Commerce] have obviously been busy since their original August 2005 intervention and John Kneuers visit to Vancouver when we were pulled off the agenda,” said Stuart Lawley, president of the would-be .XXX operator ICM Registry LLC, referring to DoC’s March 20, 2006 correspondence [PDF] recently published on ICANN’s website. “Unfortunately they don’t seem to have noticed that on September 15 the ICANN Board met and commented as follows and Voted 11-0 in favor of a resolution,” said Lawley in reference to the ICANN’s Special Meeting of the Board held in September 15, 2005 preliminary report:

“Whereas, the ICANN Board has expressed concerns regarding issues relating to the compliance with the proposed .XXX Registry Agreement (including possible proposals for codes of conduct and ongoing obligations regarding potential changes in ownership) and has noted the importance of private registry agreements, in creating contractual means of affecting registries and other actors of the Internet community for the public interest.

Whereas, ICANN has received significant levels of correspondence from the Internet community users over recent weeks, as well as inquiries from a number of governments.

Resolved (05.__), that the ICANN President and General Counsel are directed to discuss possible additional contractual provisions or modifications for inclusion in the .XXX Registry Agreement, to ensure that there are effective provisions requiring development and implementation of policies consistent with the principles in the ICM application. Following such additional discussions, the President and General Counsel are requested to return to the board for additional approval, disapproval or advice.”

ICM Registry has responded [PDF] to the Chair of ICANN’s Governmental Advisory Committee, explaining that “every thing contained in Acting Asst Secretary Kneuers letter, plus more, are included in the revised contract before ICANN,” said Lawley.

Coincidently, a very pointed letter was published yesterday, March 25 2006, in The Financial Times by Elly Plooij-van Gorsel, the former VP of the European Parliament, on the current status of .XXX approval dilemma.

By CircleID Reporter

CircleID’s internal staff reporting on news tips and developing stories. Do you have information the professional Internet community should be aware of? Contact us.

Visit Page

Filed Under

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

VINTON CERF
Co-designer of the TCP/IP Protocols & the Architecture of the Internet

Comments

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

Related

Topics

Domain Management

Sponsored byMarkMonitor

Threat Intelligence

Sponsored byWhoisXML API

IPv4 Markets

Sponsored byIPXO

Cybersecurity

Sponsored byVerisign

Domain Names

Sponsored byVerisign