Skip to main content

Generic Names Supporting Organization (GNSO) Review

The Board took action on 21 June 2021 to defer the Third Review of the Generic Names Supporting Organization. See the Board resolution here.

GNSO Review Wiki Workspace Page
Find the latest status updates, recordings of past meetings, and opportunities to participate
Introduction to Reviews
Learn more about Reviews, their purpose and process for conducting and opportunities to participate

The Generic Names Supporting Organization (GNSO) is a policy-development body which is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains (gTLDs).  For more information on the GNSO, click here.

GNSO Organizational Review

The goal of the review, to be undertaken pursuant to such criteria and standards as the Board shall direct, shall be to determine (i) whether that organization, council or committee has a continuing purpose in the ICANN structure, (ii) if so, whether any change in structure or operations is desirable to improve its effectiveness and (iii) whether that organization, council or committee is accountable to its constituencies, stakeholder groups, organizations and other stakeholders.

These periodic reviews shall be conducted no less frequently than every five years, based on feasibility as determined by the Board. Each five-year cycle will be computed from the moment of the reception by the Board of the final report of the relevant review Working Group.

The first GNSO Review commenced in 2008 and concluded in 2012.  The second GNSO Review commenced in 2014 and implementation of the recommendations in the independent reviewer’s report is expected to conclude in 2019.

The graphic below illustrates phases and status of each review - a  indicates that all activities within a given phase have been completed.  The chart that follows the graphic provides further details of key activities and milestones within each phase – you can view these details by clicking on each of the phases in the graphic.  The table also contains links to relevant documents.


GNSO2 (2014-2015)
PhaseActivityDescriptionStart DateDocuments
Plan ReviewAppointment of review team membersAppointment of review team members1 Jan 2014
Terms of ReferenceDocument outlining the scope of work adopted by the Board1 Jan 2014
RFP for Independent EvaluatorIndependent Expert Request for Proposals announcement23 Apr 2014
Conduct ReviewSelection of Independent ConsultantAnnouncement of selection of independent consultant23 Jun 2014
Draft Report of Independent ConsultantWestlake Governance published its Draft Report1 Jun 2015
Public comment on Independent Consultant’s Draft ReportPublic comment on recommendations on Westlake Governance’s Draft Report1 Jun 2015
Final Report of Westlake Governance Final Report of Independent Examiner, Westlake Governance, on GNSO Review (translations of Executive Summary available)15 Sep 2015
Final Report CorrectionFinal Report Correction to Recommendation 1 issued by Westlake Governance 5 Oct 2015
GNSO Council actionGNSO Council adopts GNSO Review Recommendations Feasibility and Prioritization14 Apr 2016
OEC accepts Final ReportOEC agreed to make the recommendation to the Board to accept the Final Report of the independent examiner and to adopt the recommendations as recommended by the GNSO Review Working Party, including the modification of the GNSO Council.15 May 2016
Board receipt and action on the Final ReportBoard receipt and action on the Final Report25 Jun 2016
Plan ImplementationGNSO Council actionGNSO Council adopts draft Charter for Implementation Working Group11 Jul 2016
Call for VolunteersCall for Volunteers: GNSO Review Working Group responsible for developing an implementation plan27 Jul 2016
Implement ImprovementsLatest details of implementationInformation available on the community wiki1 Sep 2016
GNSO Review Recommendations Implementation PlanGNSO Review Recommendations Implementation Plan21 Nov 2016
GNSO Council Adoption of Implementation PlanGNSO Council Resolution Adopting the GNSO Review Implementation Plan15 Dec 2016
Implementation Plan Accepted by the BoardImplementation plan accepted by the Board and directs the Working Group to provide updates to the OEC every six months3 Feb 2017
GNSO2 Review Implementation Final ReportGNSO2 Review Implementation Final Report30 Jul 2018
Board Accepts Implementation Final ReportAcceptance of GNSO2 Review Working Group's Implementation Final Report27 Jan 2019
Standard Operating ProceduresDeferral of Third GNSO ReviewDeferral of the third Generic Names Supporting Organizational Review (GNSO3)21 Jun 2021

GNSO1 (2008-2012)

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"""" is not an IDN."