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).
Section 2.1-Council Member Term Limits [PDF, 132 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.]
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