You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

  1. Motion to adopt the GNSO Review Working Party’s feasibility and prioritization analysis of the GNSO Review Recommendations

Motion withdrawn 9 March 2016
Made by: Wolf-Ulrich Knoben

Seconded by: Amr Elsadr

Whereas,

  1. The GNSO Review Working Party was formed to serve as a liaison between the GNSO, the independent examiner and the ICANN Board’s Organizational Effectiveness Committee.
  2. Each GNSO Stakeholder Group and Constituency appointed representatives to serve on the Working Party.
  3. The GNSO Review Working Party provided input on the review criteria, 360 assessment and served as a conduit for input from GNSO Stakeholder Groups, Constituencies as well as the GNSO Council.
  4. The GNSO Review Working Party offered guidance to the independent examiner to ensure the draft report accurately reflects the GNSO structure, scope and dynamics.
  5. The Final Report of the independent examiner was published on 15 September 2015 (see https://www.icann.org/en/system/files/files/gnso-review-final-15sep15-en.pdf) and contained 36 recommendations in the areas of: participation & representation, continuous development, transparency and alignment with ICANN’s future.
  6. The GNSO Review Working Party reviewed the recommendations and conducted a feasibility and prioritization analysis (see http://gnso.icann.org/en/drafts/review-feasibility-prioritization-25feb16-en.pdf), which it submitted to the GNSO Council on 28 February 2016. 
  7. The GNSO Council reviewed the feasibility and prioritization analysis provided by the GNSO Review Working Party.

Resolved,

The GNSO Council adopts the GNSO Review Recommendations Feasibility and Prioritization analysis (see http://gnso.icann.org/en/drafts/review-feasibility-prioritization-25feb16-en.pdf

  1. The GNSO Council instructs the GNSO Secretariat, on behalf of the GNSO Council and Chair, to communicate the GNSO Review Recommendations Feasibility and Prioritization analysis to the ICANN Board’s Organizational Effectiveness Committee (OEC) and communicate that the GNSO Council expects that the ICANN Board and the OEC will factor in the GNSO Revie Recommendations Feasibility and Prioritization analysis as part of its consideration of the GNSO Review Recommendations.
  2. The GNSO Council requests that ICANN policy staff prepare a discussion paper that outlines the possible options for dealing with the implementation of the GNSO Review recommendations following adoption by the ICANN Board taking into account the past implementation of the GNSO Review as well as existing mechanisms such as the SCI, the GNSO Review Working Party and other applicable best practices and lessons learned from past reviews.
  3. The GNSO Council thanks the GNSO Review Working Party for its work and hopes its members will continue their contributions as part of the implementation phase.


2. Motion to confirm the role and process for a GNSO Liaison to the Governmental Advisory Committee

Made by: James Bladel
Seconded by: Jennifer Gore

Whereas:

 

  1. As part of the discussions within ICANN between the GNSO and GAC, on how to facilitate early engagement of the GAC in GNSO policy development activities, the option of appointing a GNSO liaison to the GAC was proposed as one of the mechanisms to explore and implemented as a one-year pilot program in FY15 on the recommendation of the GAC-GNSO Consultation Group.
  2. The GAC and GNSO Council agreed that additional time was needed to fully evaluate this pilot program and as such requested, and received, support for continuing the pilot program in FY16.
  3. The GAC-GNSO Consultation Group reviewed the pilot project (see http://gnso.icann.org/en/drafts/review-liaison-gac-pilot-29feb16-en.pdf) and has recommended to the GAC and GNSO that ‘the GNSO Liaison to the GAC, in conjunction with the other improvements recommended by the GAC-GNSO Consultation Group, has positively contributed to the GAC engagement with the GNSO, and recommends that the GNSO Liaison to the GAC is transformed from a pilot project to a permanent role’. 
  4. The GAC and GNSO discussed the review of the pilot project during their joint session at the ICANN meeting in Marrakesh.
  5. The GNSO Council reviewed the ‘Request for Candidates – GNSO Liaison to the GAC’ which includes the proposed call for volunteers, application and evaluation process (see [include link].

Resolved:

  1. The GNSO Council hereby confirms that the GNSO Liaison to the GAC is to become a permanent role at the start of FY17 (1 July 2016) and adopts the ‘Request for Candidates – GNSO Liaison to the GAC’ as the requirements, process and procedures for this role (see [include link]).
  2. The GNSO Council instructs the GNSO Secretariat to distribute the request for candidates to the GNSO Stakeholder Groups and Constituencies in accordance with the timeline outlined in the ‘Request for Candidates – GNSO Liaison to the GAC’.
  3. The Council thanks Mason Cole who has been fulfilling this role for the last two years and looks forward to working with him during the remainder of his term.

 

3. Adoption of the GNSO Review of GAC Communiqué for submission to the ICANN Board

 Made by: Susan Kawaguchi

Seconded by:

Whereas,

 

  1. The Governmental Advisory Committee advises the ICANN Board on issues of public policy, and especially where there may be an interaction between ICANN's activities or policies and national laws or international agreements. It usually does so as part of a Communiqué, which is published towards the end of every ICANN meeting.
  2. The GNSO is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains.
  3. The GNSO has expressed a desire to provide feedback to the ICANN Board on issues in the GAC Communiqué as these relate to generic top-level domains to inform the ICANN Board as well as the broader community of past, present or future gTLD policy activities that may directly or indirectly relate to advice provided by the GAC.
  4. The GNSO Council developed a template to facilitate this process, which was completed following the publication of the Marrakesh GAC Communiqué by a volunteer and shared with the GNSO Council for its review.
  5. The GNSO hopes that the input provided through its review of the GAC Communiqué will further enhance the co-ordination and promote the sharing of information on gTLD related policy activities between the GAC, Board and the GNSO.

 

Resolved,

  1. The GNSO Council adopts the GNSO Review of the Marrakesh GAC Communiqué (see [include link]) and requests that the GNSO Council Chair communicate the GNSO Review of the Marrakesh GAC Communiqué to the ICANN Board.
  2. Following the communication to the ICANN Board, the GNSO Council requests that the GNSO Council Chair informs the GAC Chair as well as the GAC-GNSO Consultation Group of the communication between the GNSO Council and the ICANN Board.
  • No labels
For comments, suggestions, or technical support concerning this space, please email: ICANN Policy Department
© 2015 Internet Corporation For Assigned Names and Numbers