Skip to main content

ICANN Publishes Telcordia Report on their Findings and Rankings for .NET

The following is an update on the selection of a successor operator for the .NET registry.

Telcordia has completed a period of extensive evaluation, including site visits by the Telcordia team to each applicant's facilities, the completion of preliminary written reports, and follow-up questions to each applicant. A team of technical experts from Asia, Europe and North America provided technical advice to Telcordia concerning operational aspects of the DNS during this process. ICANN has now received the evaluators' final report and rankings.

Telcordia Report

The Telcordia report contains the results of the evaluation of the responses to the .NET reassignment RFP. The report consists of four sections: an executive summary of the findings, a description of the procedures that were used to evaluate the responses, the findings by RFP section, and the overall evaluation.

The Telcordia report noted the following: "The evaluators find that all the vendors have the capabilities to run the .NET registry". Telcordia concluded that the "distinguishing characteristics are largely difference in experience, risk and price". The final scoring result gave a slight advantage to VeriSign over Sentan, who were in order followed by Afilias, Denic and CORE++. Here are the rankings:

Rankings at a glance, taken from the Telcordia report:

 

Afilias Limited

CORE++

DENIC Domain

SentanRegistry

VeriSign, Inc.

Applicant Ranking (overall)

3

5

4

2

1

High priority criteria

3 Blue

3 Blue

1 Red

4 Blue

1 Yellow

12 Blue

14 Blue

Medium priority criteria

-

1 Blue

-

1 Blue

-

Pricing rank (medium priority)

1

4

5

2

2

Lower priority criteria

-

-

-

-

-

1 Throughout the process scores of Red, Yellow, Green or Blue were used. Although specific definitions of the scores were developed for each criteria in the RFP (process described below), the intuitive meaning of these scores is: Red = unacceptable, Yellow = has serious flaws or issues, Green = acceptable, Blue = exceeds requirements. 2 ICANN .net Request for Proposals, http://www.icann.org/tlds/dotnet-reassignment/net-rfp-final-10dec04.pdf

The full Telcordia report is published here: http://www.icann.org/tlds/dotnet-reassignment/net-rfp-finalreport-28mar05.pdf

The Internet community is now invited to review the report. ICANN will promptly enter negotiations with the top-ranked applicant to reach a mutually acceptable registry agreement.

ICANN's proposed form of the registry agreement has been posted on the ICANN website http://www.icann.org/tlds/dotnet-reassignment/draft-net-agreement-9mar05.pdf.

For additional information concerning the .NET selection process, please see http://www.icann.org/tlds/dotnet-reassignment/dotnet-general.htm.

Background

The Request for Proposals concerning the successor .NET registry operator was posted on 10 December 2004. An open question period for applicants was conducted through 7 January 2005. On 20 January 2005, ICANN announced the receipt of five applications. On 7 February 2005, ICANN announced that Telcordia Technologies, Inc. had been retained to conduct the independent evaluation of the applications.

About Telcordia

For more information about Telcordia please see the following link:

http://icann.org/announcements/announcement-07feb05.htm

About ICANN

ICANN is an internationally organised, non-profit corporation that has responsibility for Internet Protocol (IP) address space allocation, protocol identifier assignment, generic (gTLD) and country code (ccTLD) Top-Level Domain name system management, and root server system management functions. As a private-public partnership, ICANN is dedicated to preserving the operational stability of the Internet; to promoting competition; to achieving broad representation of global Internet communities; and to developing policy appropriate to its mission through bottom-up, consensus-based processes.

For all media enquiries: please email press@icann.org or call +1 310 301 5801


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