Skip to main content

ICANN Posts Request for Proposals for Independent Evaluator for Nominating Committee Review, and Final Terms of Reference for This Review

Updated 25 April 2007
Note: deadline for responding to this RFP has been extended to 9 May 2007

1. Introduction

1.1. This document should be read in conjunction with the Terms of Reference for Independent Review of the Nominating Committee document (found at http://www.icann.org/reviews/tor-review-nomcom-15mar07.htm). Read together, these two documents provide the materials necessary to respond to this Request for Proposals (“RFP”) for Independent Review of the Nominating Committee (“Review”).

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 criteria for selection.

2. Objectives

2.1. The review is designed to determine : (i) whether the NomCom has a continuing purpose in the ICANN structure; and (ii) if so, whether any change in structure or operations is desirable to improve its effectiveness. The Review, which is mandated by the Bylaws concerning periodic review of elements of the ICANN structure, will be undertaken pursuant to guidance provided by the Board, including the Board’s approval of the Terms of Reference.

2.2. The Review is due to begin in Q1 2007. A full project timeline will be developed, but it is anticipated that a key milestone will include presentation of a draft Review at the June ICANN meeting. The results of the Review will be posted for public review and comment, and considered by the Board.

2.3. The Review of the NomCom is expected to include personal interviews, surveys and research using information provided by the chairs and members (current and former) of the NomCom, among other members of the ICANN community. The successful candidate is welcome to suggest additional forms of soliciting the information. ICANN will provide to the Review team background documentation and reports and access to a range of historical data on a confidential basis.

2.4. The Review team is expected to have detailed knowledge of and similar experience with corporate governance and recruitment issues, including with respect to international non-profit organizations, as well as some familiarity with the ICANN process.

3. Tender Scope and Conditions

3.1. Given the 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 projects, consultancies, research, publications and other relevant information, including references.

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. The 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 the 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 non-disclosure agreement.

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

3.2 Revised deadline / requirements: Interested applicants should submit proposals by email to rfpnomcom@icann.org to the attention of Denise Michel, Vice President, Policy Development, by 9 May 2007 (a confirmation email will be sent for each proposal received).


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