敬请阅读 ICANN 的公告,了解最新政策制定活动和区域事务等等。

Draft Procedure for Designating Subsequent .net Registry Operator

2004 年 06 月 2 日


  • English


The following outlines the draft procedure to be followed for the designation of a subsequent registry operator for .net. This procedure is being announced in accordance with Section 5.2 of the current .net Registry Agreement and is being posted on the ICANN website to provide an opportunity for public comments. All substantive public comments will be provided to the ICANN Board prior to its meeting in June 2004 as a supplement to this document, after which the final procedure will be posted on the ICANN website.

In order to receive consideration by the Board in establishment of the final procedure, comments should be submitted by 24 June 2004, 12:00 PDT / 19:00 UTC.

Please click here to view public comments posted on the draft procedure


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 agreement also makes the following provisions regarding the establishment of the procedure and the obligations of the current registry operator:

5.2.2 Registry Operator or its assignee shall be eligible to serve as the successor Registry Operator and neither the procedure established in accordance with subsection
5.2.1 nor the fact that Registry Operator is the incumbent shall disadvantage Registry Operator in comparison to other entities seeking to serve as the successor Registry.
5.2.3 If Registry Operator or its assignee is not designated as the successor Registry Operator, Registry Operator or its assignee shall cooperate with ICANN and with the successor Registry Operator in order to facilitate the smooth transition of operation of the registry to successor Registry Operator. Such cooperation shall include the timely transfer to the successor Registry Operator of an electronic copy of the Registry Database and of a full specification of the format of the data.

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 has been formed to develop such guidance. The open and transparent process deployed to develop the criteria and conditions includes public comment periods. The report will then be passed on for approval by the GNSO Council after which it will be recommended to the ICANN Board of Directors as a part of the procedures that will lead to designation of a subsequent .net Registry Operator.

Procedure for Designation of Successor .net Registry Operator

The procedure for designation of a subsequent Registry Operator contains the following elements. The procedure is established in accordance with Section 2.1 to the current Registry Agreement, and the target schedule listed may be adjusted to the extent circumstances warrant.

1. Requests for Advice on Selection Criteria (31 March 2004 – 31 July 2004)

In developing the program and procedures for the selection of a subsequent registry operator ICANN is obligated to the terms in Section 5.2.1 of the existing .net Registry Agreement as follows.

“5.2.1 Not later than one year prior to the end of the term of this Agreement, ICANN shall, in accordance with Section 2.1, adopt an open, transparent procedure for designating a successor Registry Operator. The requirement that this procedure be opened one year prior to the end of the Agreement shall be waived in the event that the Agreement is terminated prior to its expiration.”
As requested by ICANN, the GNSO shall establish a recommendation for the selection criteria. In this work the GNSO will be guided by Section 5.2.4 of the current .net Registry Agreement:
5.2.4 ICANN shall select as the successor Registry Operator the eligible party that it reasonably determines is best qualified to perform the registry function under terms and conditions developed pursuant to Subsection 4.3 of this Agreement, taking into account all factors relevant to the stability of the Internet, promotion of competition, and maximization of consumer choice, including without limitation: functional capabilities and performance specifications proposed by the eligible party for its operation of the registry, the price at which registry services are proposed to be provided by the party, the relevant experience of the party, and the demonstrated ability of the party to manage domain name or similar databases at the required scale.

In this work, the GNSO has stated that they are considering the work of the DNSO with respect to the reassignment of the .org registry in 2002. The draft consensus statement from the GNSO will go through the process the process as outlined at the May 28, 2004 Announcement.

2. Development of Request for Proposal (1 August 2004 – 30 September 2004)

Following the recommendation from the GNSO to the ICANN Board of Directors, the Board will be asked to authorize the ICANN staff to issue a Request for Proposal (RFP). As part of the process of building the RFP, ICANN staff will request that relevant committees and organizations to comment on the selection criteria recommendation by the GNSO Council. Based on advice from these groups, the RFP will be developed to include all criteria by which the proposals will be judged.

ICANN will post an initial draft of the RFP for public comments. ICANN will take public comments into consideration prior to posting the finalized RFP documents and before publishing a full timeline for the submission and evaluation periods. The final RFP (including criteria for determining the .net registry operator based upon the recommendation as provided by the GNSO and other relevant committees and organizations as appropriate) will be approved by the ICANN Board prior to being posted publicly.

3. Proposal Submission Period (1 October 2004 - 30 November 2004)

A proposal submission period will be established in which interested parties may submit applications to become the subsequent .net registry operator. ICANN will only accept questions from applicants and other interested parties that are submitted to a designated email address during this period. Answers to these questions will be made publicly available.

4. Public Comment Period (1 December 2004 – 15 December 2004)

There will be a two-week period in which the community has the opportunity to post comments regarding the individual proposals. As will be described in the RFP, parts of the proposals may be kept confidential and not be posted for public review and comments.

5. Evaluation and Reporting Period (15 December 2004 – 28 February 2005)

ICANN will select a team of independent technical, business/financial and legal advisors to assist it in its review of .net proposals. The panel members will be selected based on their experience, talent and skills as they apply to the evaluation task as outlined in the RFP. There will be two separate panels formed, one to measure the technical merits of the application and the second panel to test the business plans described in the applications. Potential panel members will be screened to ensure that no material conflicts of interest exist.

The independent panel of evaluators will evaluate the applications against the criteria and questions posted in the RFP and reach appropriate recommendations. If the panel decides that clarifying information is necessary to make their recommendations, such information may be requested via an independent project manager who will communicate directly with the applicants as necessary. The recommendation from the panel will be formulated in a report to the ICANN Board recommending a successful applicant and the reasons for that choice. Initially a draft report will be issued which will include the findings of the independent evaluators. Applicants will be given the opportunity to comment on this draft report.

Comments received will be taken into consideration prior to the development and publication of the final report. This final report will be posted for the Board and public to review. Applicants are invited to submit a commentary on the final report. All comments received will be posted and provided to the Board for review.

Before the Board is asked to consider the recommendation contained in the final report, contractual terms will be finalized between ICANN and the successful applicant, as in accordance with the terms listed in the RFP.

6. Consideration by the ICANN Board (March 2005 Board meeting)

The Board will review the final report together with any comments prior to voting on the recommendation as contained in the final report.

7. Announcement of Subsequent .net Registry Operator (March 2005)

Following the Board’s decision, the concurrence of the US Department of Commerce will be sought by ICANN pursuant to Amendment 3 to ICANN/DOC Memorandum of Understanding. At the same time, ICANN will make an announcement of the designated subsequent .net registry Operator.

A subsequent .net registry agreement will be signed and if an operator other than VeriSign is selected, a business and technical transition period will take place prior to the effective date of the new agreement (30 June 2005).

In order to receive consideration by the Board in establishment of the final procedure, comments should be submitted by 24 June 2004, 12:00 PDT / 19:00 UTC.

Please click here to view public comments posted on the draft procedure