Skip to main content

ICANN Releases .NET RFP for Public Comment

Marina del Rey (November 12, 2004) – ICANN has released for public comment a draft of the .NET Request for Proposals (RFP). The public comment period will commence today and will end in two weeks on 26 November 2004 at 17:00 UTC.

The draft .NET RFP can be found here.

General information about past actions and correspondence in regards to the .NET reassignment process can be viewed here.

Click here to view comments on the draft .NET RFP

The current 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 "successor" registry operator. The procedure was announced on 29 June 2004.

The draft .NET RFP has been developed by adopting the recommendation from the GNSO Council and previous public comment periods and correspondence from interested parties has been taken into consideration.

The RFP contains all criteria by which the proposals will be judged as well as a timeline for the continued .NET reassignment process.

Following the public comment period, all relevant comments will be taken into consideration for development of the final .NET RFP. The final .NET RFP will be approved by the ICANN Board and posted online at which time the Proposal Submission Period will begin.

For further details of the timeline involved in the .NET reassignment please see the timeline included in the draft .NET RFP.


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