Skip to main content

GNSO Council Operations Work Team and Constituency and Stakeholder Group Operations Work Team Recommendations

Open: 28 June 2010
Closed: 18 July 2010

Explanation/Background: These recommendations are the product of two Work Teams (Sections A and B below) that were chartered by the GNSO's Operations Steering Committee (OSC) in March 2009 to review and recommend implementation proposals concerning certain sections of the Board's GNSO Improvements Report (3 February 2008).

  1. The GNSO Council Operations Work Team was tasked with a cross-constituency effort to review the existing GNSO operating rules and procedures and to recommend changes consistent with the new GNSO Council's goal to become a strategic manager of the policy process.  In June 2009, the Work Team developed a package of those recommendations, particularly those necessary to seat the new GNSO Council at the ICANN meeting in Seoul, South Korea in October 2009. The GNSO Council approved the recommendations for new GNSO Council Operating Procedures on 28 October 2009. Subsequently, the GNSO Council Operations Work Team identified additional recommendations for amending the GNSO Council Operating Procedures in accordance with the Board's GNSO Improvements Report. These additional recommendations are the subject of this announcement. In particular, the Work team completed and submitted certain documents that it recommends be incorporated into the GNSO Operating Procedures (GOP) as follows:
  2. Section 2.1-Council Member Term Limits [PDF, 132 KB]
    Section 2.4-Board Seat Elections [PDF, 85 KB]
    Section 3.8-Absences and Vacancies [PDF, 141 KB]
    Chapter 4.0-Voting [PDF, 297 KB]
    Chapter 5.0-Statements and Disclosures of Interest [PDF, 93 KB]

    [Note that two sections, 5.3.2 and 5.3.3, are not approved pending further Staff action to be determined. These sections are footnoted in the document as "inactive" until subsequently approved by the OSC and Council.]

  3. The Constituency and Stakeholder Group Operations Work Team (CSG-WT) was tasked with developing recommendations on Constituency and Stakeholder Group participation rules, operating principles, and member databases. The Work Team divided this task into the following four subtasks:
  • Subtask 1: Develop recommendations for a set of participation rules and operating procedures, to which all Constituencies should abide;
  • Subtask 2: Develop recommendations for clear operating principles for Constituencies to ensure they function in a representative, open, transparent and democratic manner;
  • Subtask 3: Develop recommendations for creating and maintaining a database of all Constituency members and others not formally a part of any Constituency that is up-to-date and publicly accessible; and
  • Subtask 4: Develop a "toolkit" of in-kind staff support and/or services for all Constituencies.

The Work Team completed the recommendations for Subtask 4 ahead of the other subtasks and submitted these recommendations separately to the OSC for review. The OSC approved the recommendations with modifications and submitted them to the GNSO Council, which voted to accept the recommendations on 17 December 2009 and staff work on implementation is underway.

The consolidated recommendations on the three subtasks are detailed in the following report: Recommended Common Operating Principles and Participation Guidelines for GNSO Stakeholder Groups and Constituencies; and Recommendations on a GNSO Database of Community Members [PDF, 453 KB].

At its 23 June 2010 GNSO Council directed the Staff to post for public comment for a 21-day period the recommendations of the GNSO Council and Constituency and Stakeholder Group Operations Work Teams for public review and comment. Community members are invited to review the recommendations and comment on all aspects of the recommended procedures.

The Process From Here:

At the end of this Public Comment Forum period, ICANN Staff will review the comments submitted and prepare a summary analysis of the various submissions for Work Team and GNSO Council review.

Deadline and How to Submit Comments:

At the direction of the GNSO Council, the Staff is opening a 21-day public consultation forum, from 28 June through 18 July 2010 and invites community comments concerning this document.

Staff Responsible: Julie Hedlund

Staff member responsible: Julie Hedlund

Announcement | Comments | Summary/analysis of comments

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