Skip to main content

Request for Proposals for Independent Evaluator for GNSO Review

(revised 19 December 2005)

1. Introduction

1.1. This document should be read in conjunction with the GNSO Review – Background Information document (found at http://www.icann.org/en/gnso/review-tor-background-04nov05.htm). Read together, the two documents provide the materials necessary to consider the GNSO Review Terms of Reference (GNSO ToR) which will be completed in early 2006. The documents reflect detailed consultation between ICANN Staff, the GNSO Council and between the GNSO Council and individual members of the ICANN Board.

1.2. ICANN now seeks to appoint an independent consultant to undertake the Review. The information outlined below illustrates the scope of the work and the selection criteria for evaluators.

2. Objectives

2.1. The review (among other actions) is designed to lead to improvements to one of the key policy development supporting organisations within the ICANN community. The ICANN Board requested a review of the GNSO in compliance with the ICANN Bylaws and resolved at its annual general meeting in Vancouver, Canada to formally initiate the review.

2.2. The review is due to begin in early February 2006 and should be completed by early Q2 2006. A full project timeline will be developed, but it is anticipated that a key milestone will include the presentation of a draft report at the Wellington, New Zealand meeting in March 2006.

2.3. The evaluation of the GNSO is expected to include face-to-face interviews, online surveys and desk research using information provided by the GNSO constituencies. The successful candidate is welcome to suggest additional forms of soliciting the information. ICANN will provide to the evaluation team baseline statistics that have been requested of each of the GNSO constituency chairs. ICANN will also provide background documentation and reports and access to a range of historical data.

2.4. Evaluators are expected to have detailed knowledge of or similar experience with policy making in an online environment, most particularly in relation to Internet governance.

3. Tender Scope and Conditions

3.1. Given the GNSO Review Terms of Reference found below and responding specifically to the requests for further information, applicants should provide:

3.1.1. Statement of Suitability. The Statement of Suitability must include a detailed outline of the applicant’s ability to perform the work showing past consultancies, research and publications.

3.1.2. Work Approach. The Work Approach needs to detail the way in which the applicant would respond to the Terms of Reference; provide details about specific skills with interview techniques, data gathering and report writing. Successful candidate will be required to communicate through email, conference calls, and video conference over IP.

3.1.3. Description of Final Product. Describe, prospectively, the form and organization of a final report. The report should be suitable for electronic transmission, i.e., limited file size and widely used format.

3.1.4. Team Curriculum Vitae. The response must include Curriculum Vitae for the whole team showing each individual’s suitability for the proposed work.

3.1.5. ICANN Contract Compliance: Applicants should warrant that they are willing to operate under a standard non-disclosure agreement.

3.1.6. The proposal should include a work schedule including key milestone dates and a statement of fees.

3.2 Revised deadline / requirements: Interested applicants should submit proposals by email to Kurt Pritz, Vice President, Business Operations (pritz@icann.org), and Dr. Liz Williams, Senior Policy Counselor (liz.williams@icann.org) by Monday 9 January 2005.


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