Skip to main content

ICANN Publishes Draft Agreement on .XXX

A Revised Proposed Registry Agreement with ICM to be designated as the Registry Operator for a .XXX Sponsored Top Level Domain (.XXX), as well as documentation submitted by ICM Registry in connection with the expedited due diligence conducted at the direction of the Board are being posting today for public comment.

This information is posted for a thirty day public comment period commencing at 12:00 pm Pacific Daylight Time (19:00 UTC) on 24 August 2010 through 11:59 a.m. Pacific Daylight time (18:59 UTC) on 23 September 2010.

Comments can be submitted to and viewed at


In 2004, ICM submitted an application in response to an ICANN Request for Proposals to create new Sponsored Top-Level Domain registries. A first proposed registry agreement for .XXX was posted on 16 April 2006. In May 2006, the Board voted not to approve the agreement as proposed, and two revisions to the proposed registry agreement were posted for public comment in January and February of 2007 (see

On 30 March 2007, the Board rejected the proposed agreement. After ICM sought an independent review of the Board’s denial of ICM’s application for the .XXX sTLD, the Independent Review Panel issued a declaration. On 25 June 2010, the Board determined to accept and act in accordance with some of the Panel’s findings and directed ICANN staff to conduct expedited due diligence of ICM and to proceed into draft contract negotiations with ICM. See On 5 August 2010, the Board directed staff, upon receipt of ICM’s application documentation, to post ICM’s supporting documents and proposed registry agreement for public comment for a period of no less than 30 days. See

Consistent with the Board’s Resolutions of 25 June 2010 and 5 August 2010, ICANN staff is posting the following materials for public comment:

Due Diligence Documentation submitted by ICM Registry:

Revised Proposed Registry Agreement for the .XXX sTLD

The Revised Proposed Registry Agreement was submitted by ICM Registry after negotiations with ICANN staff. The Revised Proposed Registry Agreement has not been considered or approved by the ICANN Board. The Revised Proposed Registry Agreement is revised from the proposed agreement considered by the Board in March 2007.

The documents are provided in both clean and redlined form for ease in identifying revisions.

Revised Proposed Registry Agreement:

Revised Proposed Appendix S to Registry Agreement:

Some of the major changes between the 2007 versions and the current proposed versions are:

  • The agreement is revised to reflect changes to address DNSSEC handling and current technical specifications, as well as links to current ICANN processes;
  • The agreement is revised to be consistent with most sTLD agreements in the renewal terms.
  • The termination, assignment and subcontracting provisions have been revised and clarified.
  • Modifications to Appendix S to further define the sTLD community and to provide the requirements of ICM in developing and implementing policy for the TLD through IFFOR, consistent with the ICM/IFFOR Sponsoring Organization Agreement and the sTLD charter.

ICM has committed to sign a standard release of all claims against ICANN in conjunction with the execution of a Registry Agreement.


1 ICM’s Cover Letter identifies additional information submitted to ICANN on a confidential basis. Those documents are not publicly posted.

More Announcements
Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as"""" is not an IDN."