Skip to main content

Final Public Comment Period begins on Draft Criteria for .net

The GNSO has continued the work to provide the ICANN Board with guidance on the criteria for designating a subsequent operator for the .net registry. The public is invited to submit comments on the new version of the initial draft report from the GNSO. This final comment period is ending on July 14, 2004 at 19:00 UTC.

Please click here to view public comments posted on this report

Background

The current .net Registry Agreement between ICANN and VeriSign, Inc. was signed in May 2001, and will expire on 30 June 2005. The agreement provides (per Section 5.2.1) that ICANN, no later than 30 June 2004, will adopt an open and transparent procedure for designating a subsequent registry operator.

The ICANN Board resolved at its meeting in Rome on 6 March 2004:

[04.18] that in order to prepare for the designation of a transparent procedure by 30 June 2004, the Board authorizes the President to take steps to initiate the process as specified in Section 5.2 of the .net Registry Agreement for designating a subsequent operator for the .net registry, including referrals and requests for advice to the GNSO and other relevant committees and organizations as appropriate.

As provided in this resolution, ICANN is taking steps to present and adopt the procedure under which a subsequent .net registry operator will be selected. Accordingly, on 31 March 2004, ICANN issued a formal request for guidance from the GNSO concerning the criteria for designating a subsequent operator for .net.

A GNSO subcommittee was formed to develop such guidance. The open and transparent process deployed to develop this guidance includes public comment periods as detailed further below.

Coincident with this work, ICANN has posted the procedure for determining the .net registry operator. This procedure has gone through a public comment ending June 25, 2004, and will be redrafted where relevant before it will be submitted to the ICANN Board of Directors for approval. The final procedure will be posted on the ICANN website at the latest by June 30, 2004.

The GNSO Process for Developing .net Selection Criteria

The new version of the initial draft report from the GNSO subcommittee can be viewed here.

The GNSO process:

28 May 2004 – 18 June 2004: First 20-day Public Comment Period

In this the first 20-day comment period, the public was invited to submit comments on the initial draft report from the GNSO subcommittee. The comments submitted can be viewed here.

The GNSO subcommittee reviewed the comments and incorporated changes in the report where relevant.

25 June 2004 – 14 July 2004 (19:00 UTC): Final Public Comment Period

In this final comment period, the public is invited to submit comments on the new version of the initial report from the GNSO subcommittee

The GNSO subcommittee will review and incorporate the relevant comments received in this final comment period. The final report will then be submitted to the GNSO council for review.

Please click here to view public comments posted on this report

20 July 2004: GNSO Council Voting

The GNSO Council will vote to recommend the final report describing the criteria for selecting the subsequent .net registry operator to the ICANN Board of Directors.

The ICANN Board will adopt the criteria for determining the subsequent .net registry operator based upon the recommendation to be provided by the GNSO and other relevant committees and organizations as appropriate.


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."