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

Compare with Current View Page History

« Previous Version 292 Next »


Entry Date (E)


Target Date (T)

Action Item

Responsible Council Member


Responsible Staff member

Additional Notes

Assignment of Council Liaisons



  • ICANN Staff to post updated description of Council liaisons to the GNSO Procedures web page.
  • ICANN Staff to update Projects List to account for any new Council liaisons.
  • ICANN Staff to circulate call for volunteers for any liaison roles where the existing liaison wishes to step down (i.e., ccNSO, New gTLD Subsequent Procedures).

Drafting Team on charter related to the next steps for the ICANN Procedure of Handling Whois conflicts with Privacy




  • GNSO Council, after having considered the 1 August letter from Akram Atallah and receiving a brief update from GDD on its 24 August Council meeting, should determine next steps for reviewing the Whois Procedure.
  • Drafting team members to share draft charter and identified questions in charter with respective SG/Cs for feedback, following which the drafting team will review this input and finalize the charter for GNSO Council consideration.
  • Council to consider adoption of charter at its upcoming meetingI
  • ICANN Staff to circulate a call for volunteers on or after 1 June 2018 to the GNSO Stakeholder Groups, with the request for each Stakeholder Group to appoint up to 3 members to the Implementation Advisory Group (IAG). The call for volunteers should also be more widely circulated to seek volunteers to serve as participants and observers to the IAG.

Updated Charter for the Cross Community Working Group on Internet Governance



  • Council Leadership to ensure that the Cross Community Working Group on Internet Governance topic, and its proposed new structure, be added to the March 2018 Council meeting agenda as a discussion item.
  • Council Leadership to ensure that the Cross Community Working Group on Internet Governance topic, and its proposed new structure, be included in the list of topics to discuss with other SO/ACs during meetings at ICANN61, as appropriate.

GNSO Standing Committee on Budget and Operations (SCBO) review of the Draft FY19 ICANN Operating Plan and Budget



  • SCBO to liaise with New gTLD Subsequent Procedures PDP WG Co-Chairs to determine if and how concerns about the lack of FY19 budget allocation to the implementation of New gTLD Subsequent Procedures policy recommendations can be addressed in the Council’s public comment. 

Discussion of the Draft Post-Implementation Review Framework



  • ICANN Staff to further develop the draft policy post-implementation review framework, including the development of a detailed process flow document.

GNSO members for the ICANN Accountability and Transparency (ATRT3) Review Team



  • GNSO Secretariat to communicate resolved #1 (“The GNSO Council nominates, ranked in order: Brian Cute (RySG), Wolfgang Kleinwächter (NCSG), Stéphane Van Gelder (RySG) as its primary three candidates for the ATRT3. Furthermore, the GNSO nominates, in ranked order: Tatiana Tropina (NCSG), Michael Karanicolas (NCSG), Adetola Sogbesan (BC), Erica Varlese (RySG) to be considered for inclusion in the ATRT3 by the SO-AC Chairs should additional places be available that need to be filled.”) to the staff supporting the ATRT3.
  • GNSO Secretariat to inform the endorsed candidates that the GNSO Council expects that if selected for the ATRT3, the applicant will represent the views of the entire GNSO community in their work on the ATRT3, and provide regular feedback as a group on the discussions taking place in the ATRT3, as well as the positions being taken by GNSO Review Team members. (to be completed after meeting with other SO/ACs to determine final Review Team membership)
  • Staff supporting the ATRT3 and application process to send a response to those applicants who did not receive endorsement for this Review Team, thanking them for their interest and note their importance in the event an alternate is needed in the future. The response should encourage them to follow the ATRT3 work, participate in Public Comments and community discussions, and to apply for future opportunities within the GNSO Community as they arise. (to be completed after meeting with other SO/ACs to determine final Review Team membership)
  • ICANN Staff to post GNSO Council Leadership letter to GNSO nominated ATRT3 members on the GNSO Correspondence page.

Revised GNSO Operating Procedures and ICANN Bylaws



  • Staff to put forth recommendation on how Council can better consider topic and determine next steps (e.g., webinar, review red-line of GNSO Operating Procedures/ICANN Bylaws, etc.)
  • Council to consider next steps and provide feedback on what further is needed for the discussion planned during the Council Strategic Planning Session in January 2018.
  • ICANN Staff to post the new version of the GNSO Operating Procedures on the GNSO website, effective immediately.
  • ICANN Staff to inform the ICANN Board of Directors that the GNSO Council recommends adoption of the proposed changes to section 11.3.i of the ICANN Bylaws to reflect new GNSO voting thresholds, which are different from the current threshold of a simple majority vote of each House (see

Other Council Related Action Items

TopicEntry DateAction Item

Review of all Rights Protection Mechanisms in all gTLDs data request


  • PDP WG Co-Chairs to work with SubPro WG Co-Chairs to provide the GNSO Council with a consolidated timeline by ICANN61. The timeline should include milestones and dependencies, both between the two PDPs, but also external (e.g., CCT-RT).

  • No labels
For comments, suggestions, or technical support concerning this space, please email: ICANN Policy Department
© 2015 Internet Corporation For Assigned Names and Numbers