Skip to main content

Welcome to the new ICANN.org! Learn more, and send us your feedback. Dismiss

ICANN Publishes Revision to Proposed ICM (.XXX) Registry Agreement for Public Comment

Consistent with the direction given by the ICANN Board as described in the Preliminary Report of the 12 February 2007 Special Meeting of the Board, ICANN today posted for public comment a revised Appendix S [PDF, 108K] of the proposed registry agreement with ICM (sponsoring organisation for the proposed .XXX registry).

The remainder of the proposed agreement (posted in the 5 January 2007 announcement below) is unchanged.

Public comments can be made at xxx-icm-agreement@icann.org and viewed at http://forum.icann.org/lists/xxx-icm-agreement/. Public comments received on or before 9 March 2007 will be considered at the next scheduled Special Meeting of the ICANN Board (see http://www.icann.org/minutes/).

 


 

ICANN Publishes Revised Proposed Agreement on .XXX

5 January 2007

A revised proposed agreement with ICM providing for designation of a .XXX sTLD registry is published for public comment. The public comment period will be open until 5 February 2007.

Background

ICM submitted one of ten applications received in response to an ICANN Request for Proposal to create new Sponsored Top-Level Domain (sTLD) registries (see http://www.icann.org/tlds/stld-apps-19mar04/).

Details on the process are contained in the recently posted announcement.

More recently, a proposed registry agreement for .XXX (sponsored by the ICM registry) was posted on 16 April 2006 (see http://www.icann.org/announcements/announcement1-18apr06.htm). ICANN requested and received substantial comments on the previously posted agreement. ICANN also requested and received advice from the ICANN Governmental Advisory Committee (GAC) regarding the application (see, http://www.icann.org/committees/gac/communique-28mar06.pdf [PDF, 91K]).

The ICANN Board considered the agreement at its meeting on 10 May 2006 and voted not to approve the agreement as proposed, but did not reject the application.

Subsequently, ICM has continued to work to modify the agreement in order to address public policy issues raised by the GAC. ICM and ICANN Staff have been renegotiating a revised agreement for community review and board consideration. Following the public comment period, the ICANN Board will consider the revised proposed agreement in light of the ICANN community feedback and other public comments received.

Revised Proposed Agreement

Appendix S Part 8 [PDF, 21K] (New) to the proposed ICM Registry Agreement – describing the ICM Registry Operator’s Commitments regarding Policy Development and Stakeholder Protection Activities

Proposed ICM Registry Agreement for .XXX [PDF, 240K]

Public Comment Forum
Send comments to: xxx-icm-agreement@icann.org
View comments at: http://forum.icann.org/lists/xxx-icm-agreement/

ICM Documents

Additional new documents provided by ICM in support of their application:

1) Summary of Major Changes to the previously posted agreement

2) Additional Assurances Regarding Policy Development

a) Letter re ICM commitments regarding compliance monitoring [PDF, 108K]
b) Background on Internet Content Rating Association [PDF, 98K]
c) Letter re Policy Development [PDF, 99K]
d) Background on Family Online Safety Institute [PDF, 31K]

3) Child Safety Provisions

4) Enforceability Provisions

5) Changes Responding to GAC Advice:

a) ICM Statement on Response to GAC Communique re Policy and Enforcement
b) ICM Statement on GAC Request for Information


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""icann.org"" is not an IDN."