Generic Names Supporting Organization

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). The GNSO is formed of Stakeholder Groups, themselves composed of Constituencies, which together form one Supporting Organization to form consensus, set policy, and make evidence-informed recommendations. The GNSO was previously known as the Domain Name Supporting Organization (DNSO), which it replaced in 2003.

Policy development within the GNSO is governed by the GNSO Council. The Council meets 12 times per year; four times face-to-face (three times at ICANN public meetings, and once at the Council Strategic Planning Session), and eight times via webinar.

Overview

The main objective of the GNSO is to ensure that gTLDs operate in a fair and orderly manner across the global Internet, without hindering innovation or competition.

Stakeholder Groups/Constituencies

Four Stakeholder Groups appoint 18 individuals to the GNSO Council. Two appointments are also made by ICANN's Nominating Committee. Certain Stakeholder Groups, like the Commercial one, opt to delegate the appointment of their representatives to their Constituencies.

Non-Contracted Parties

• Non-Commercial Users Stakeholder Group, 6 appointments
• Commercial Stakeholder Group, 6 total appointments coming from the 3 constituencies
  • Commercial and Business Users Constituency, 2 appointments
  • Intellectual Property Interests Constituency, 2 appointments
  • Internet Service and Connection Providers Constituency, 2 appointments

Contracted Parties

• Registrar Stakeholder Group, 3 appointments
• Registry Stakeholder Group, 3 appointments

GNSO Council, as photographed at ICANN 60 in Abu Dhabi in November 2017.

GNSO Council

Organizational Structure of the GNSO Coucnil(Image from ICANN.org)

The GNSO Council consists of 23 members, 20 of whom are voting members; they come from a variety of different regions and represent the aforementioned Stakeholder Groups and Constituencies involved in ICANN's multistakeholder model. Heather Forrest is its current chair.

Members Include:

GNSO Council

• Heather Forrest - GNSO Council Chair, Asia Pacific (Term ends at AGM 2018)
• Erika Mann - NCA, Europe (Term ends at AGM 2018)

ccNSO

• Ben Fuller - ccNSO Liaison, Africa - Non-Voting, Non-Member

ALAC

• Cheryl Langdon-Orr - ALAC Liaison, Asia-Pacific - Non-Voting Member

Contracted Parties House

• Donna Austin - Vice-Chair, Asia-Pacific (Term ends at AGM 2018)
• Carlos Gutierrez - Voting NCA, Europe (Term ends at AGM 2019)

Registry Stakeholder Group

• Keith Drazek - North America (Term ends at AGM 2018)
• Rubens Kuhl - Latin America/Caribbean (Term ends at AGM 2019)
• Donna Austin - Vice-Chair, Asia Pacific (Term ends at AGM 2018)

Registrar Stakeholder Group

• Pam Little - Asia Pacific (Term ends at AGM 2019)
• Darcy Southwell - North America (Term ends at AGM 2019)
• Michele Neylon - Europe (Term ends at AGM 2018)

Non-Contracted Parties House

• Rafik Dammak - Vice-Chair, Asia Pacific (Term ends at AGM 2018)
• Syed Ismail Shah - Asia Pacific (Term ends at AGM 2019)

Commercial Stakeholder Group

Commercial and Business Users - Business Constituency

• Marie Pattullo - Europe (Term ends Annual Meeting 2019)
• Susan Kawaguchi - North America (Term ends at Annual Meeting 2018)

Intellectual Property Interests - Intellectual Property Constituency

• Paul McGrady - North America (Term ends at Annual Meeting 2019)
• Heather Forrest - Vice-Chair, Asia Pacific (Term ends at Annual Meeting 2018)

ISP Interests - ISP Constituency

• Phillippe Fouquart - Europe (Term ends at Annual Meeting 2018)
• Tony Harris - Latin America/Caribbean (Term ends at Annual Meeting 2019)

Non-Commercial Stakeholder Group

• Rafik Dammak- Asia-Pacific (Term ends at Annual Meeting 2018)
• Ayden Férdeline - Europe (Term ends at Annual Meeting 2019)
• Stephanie Perrin - North America (Term ends at Annual Meeting 2018)
• Martin Silva Valent - Latin American/Carribean (Term ends at Annual Meeting 2018)
• Tatiana Tropina - Europe (Term ends at Annual Meeting 2019)
• Arsene Tungali - Africa (Term ends at Annual Meeting 2019)

GNSO Development Process

The GNSO is the primary engine within the ICANN community for developing, recommending changes, and making modifications to generic top-level domain policies. The GNSO aims to identify ways to improve the inclusiveness and representativeness of its work while increasing its effectiveness and efficiency.

An important GNSO improvement was the development of recommendations for the new GNSO policy development process. The ICANN Board launched a set of recommendations for improving the effectiveness of the GNSO in June, 2008. These recommendations were related to GNSO activities, operations and structure.

GNSO Improvements

GNSO Standing Committee on Improvements Implementation (SCI). The SCI will be responsible for reviewing and assessing the effective functioning of recommendations provided by the Operational Steering Committee (OSC) and Policy Process Steering Committee (PPSC) and approved by the GNSO Council. The main areas of GNSO improvements which were approved by the Board, and are being implemented by the GNSO, are classified into five main categories:

1. The creation of a Working Group Model
2. Revising the PDP (Policy Development process)
3. The restructuring of GNSO Council
4. Communication improvement and a better coordination between ICANN structures
5. Improving constituency procedures

GNSO Policy Development process

The Policy Development Process (PDP) Updates are one-page documents prepared by ICANN staff to inform the Governmental Advisory Committee (GAC) and other interested parties about potential opportunities to engage in and contribute to on-going GNSO PDP efforts. They are published on a regular basis and translations of these can be found on the GAC website. Please, also refer to our GNSO Policy Briefing for information on these and other GNSO activities.

Implementation of URS

In September 2012, ICANN senior executive Kurt Pritz sent a public email to GNSO Council Chairman Stephane Van Gelder advising him that URS implementation could begin after a year of delay. Implementing URS included a pair of open meetings in Fall 2012, including one at ICANN 45 in Toronto. ICANN acknowledged the role played by the GNSO Council in developing and approving the model and said they were willing to "work in whichever way the GNSO wishes to proceed".

ICANN Supporting Organizations and Advisory Committees

Apart from GNSO, there are other SO's (supporting organizations) and advisory committees which help ICANN to fulfill its objectives. They include:

• Address Supporting Organization (ASO)
• Country Code Domain Name Supporting Organization (ccNSO)
• At-Large Advisory Committee (ALAC)
• Governmental Advisory Committee (GAC)

Generic Names Supporting Organization. Develops and recommends to the Board substantive policies relating to generic top-level domains and other responsibilities set forth in the Bylaws (ICANN Bylaws).

Deprecated. Domain Name Supporting Organization. Predecessor of the Generic Names Supporting Organization, which advised the Board with respect to policy issues relating to the Domain Name System (ICANN Bylaws).

Country Code Names Supporting Organization. Develops and recommends to the Board global policies relating to country-code top-level domains (ICANN Bylaws).

At-Large Advisory Committee. Considers and provides advice on the activities of ICANN related to the interests of individual Internet users (ICANN Bylaws). Not to be confused with the Non-Commercial Stakeholder Group.

Policy Development Process

Governmental Advisory Committee. Considers and provides advice on the activities of ICANN as they relate to concerns of governments, particularly matters where there may be an interaction between ICANN's policies and various laws and international agreements or where they may affect public policy issues (ICANN Bylaws).

Address Supporting Organization. Advises the Board with respect to policy issues relating to the operation, assignment, and management of Internet addresses (ICANN Bylaws).