Sorry, you need to enable JavaScript to visit this website.
Skip to main content

Proposed Final Agenda For GNSO Council Meeting 19 January 2017

Last Updated:

Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access:

This agenda was established according to the GNSO Operating Procedures v3.2, updated on 19 January 2017.

For convenience:

  • An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda.
  • An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda.

Coordinated Universal Time: 21:00 UTC

13:00 Los Angeles; 16:00 Washington; 21:00 London; (Friday 20 January 2017) 00:00 Istanbul; 08:00 Hobart

GNSO Council Meeting Audio Cast
To join the event click on the link:
Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call.

Item 1. Administrative Matters (5 mins)

1.1 - Roll Call

1.2 - Updates to Statements of Interest

1.3 - Review / Amend Agenda

1.4 - Observer status on GNSO Council mailing list

1.5 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures:

Minutes of the meeting of the GNSO Council part II on 7 November 2016, posted on 19 January 2017.

Minutes of the meeting of the GNSO Council on 1 December 2016, posted on 19 December 2016.

Minutes of the meeting of the GNSO Council on 15 December 2016, posted on 4 January 2017.

Item 2. Opening Remarks / Review of Projects & Action List (10 mins)

2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List and Action Item List

Item 3. Consent Agenda (0 mins)

Item 4. COUNCIL VOTE – Endorsement of GNSO Representatives to the Second Security, Stability & Resiliency Review Team (SSR-2 RT) (20 minutes)

The ICANN Bylaws mandate a periodic review of ICANN's commitment to "enhance the operational stability, reliability, resiliency, security, and global interoperability of the systems and processes, both internal and external, that directly affect and/or are affected by the Internet's system of unique identifiers that ICANN coordinates", to be conducted by a community-led Review Team. This security, stability and resiliency (SSR) review has to be conducted no less frequently than once every five years, measured from the date the previous SSR Review Team (RT) was convened. The first SSR RT was formed in October 2010, and it delivered its final report in June 2012. A Call for Volunteers to the SSR-2 RT was issued on 30 June 2016, with applications closing on 15 September 2016. A total of 12 applicants indicated that they were seeking endorsement from the GNSO, for a possible maximum of 7 out of 21 slots on the SSR-2 RT. Under the selection process agreed among the ICANN Supporting Organizations and Advisory Committees (SO/ACs), the top 3 nominees from each SO/AC will be guaranteed a slot.

A small group of volunteer Councilors have reviewed the list and qualifications of the candidates who are seeking the GNSO's endorsement. The current slate of applicants can be viewed at Here the Council will decide whether to approve the proposed slate of nominees for GNSO endorsement, as circulated to the Council list on 9 January 2017.

4.1 – Presentation of the motion (James Bladel)

4.2 – Council discussion

4.3 – Council vote (voting threshold: simple majority)

Item 5. COUNCIL DISCUSSION – Proposal for a Facilitated Discussion between the GAC and the GNSO to Resolve Outstanding Differences in GAC Advice and GNSO Policy Recommendations concerning Second Level Protections for International Governmental Organization (IGO) Acronyms and Certain Names and Acronyms of the Red Cross Movement (25 minutes)

On 20 December 2016, the GNSO Council Chairs participated in a teleconference with several members of the ICANN Board, the GAC Chair and several GAC member representatives. The purpose of the call was to discuss possible objectives for, and the scope of, a possible facilitated discussion between the GAC and the GNSO in order to resolve the inconsistencies between GAC advice and GNSO policy recommendations on the topic of IGO and Red Cross protections. These inconsistencies mainly concern second level protections for IGO acronyms and the following Red Cross identifiers: the names of 189 Red Cross National Societies, the names International Federation of Red Cross and Red Crescent Societies and International Committee of the Red Cross, and the acronyms associated with the two international names (IFRC/FICR and ICRC/CICR).

The idea for a facilitated discussion had been suggested by the ICANN Board during the second Public Forum at ICANN57, in November 2016. Following the call, the GNSO Chair requested feedback from Councilors regarding any concerns or questions about GNSO participation in the proposed discussion.

Board members who had participated in the 20 December call are preparing to circulate a proposed process outline describing the objectives and scope of the proposed discussion. Here the Council will continue its deliberations on the topic, including the timing of the discussions in relation to the work of the ongoing Working Group that is conducting the GNSO's Policy Development Process on IGO curative rights protection issues.

5.1 – Summary and update (Council Chairs)

5.2 – Council discussion

5.3 – Next steps

Item 6. COUNCIL DISCUSSION – Letter from Thick WHOIS Implementation Review Team on Privacy Issues relating to Implementation of the Thick WHOIS Consensus Policy Recommendations (10 minutes)

On 15 December 2016, the Thick WHOIS Implementation Review Team (IRT) sent a letter to the GNSO Council describing a number of privacy law developments and how the IRT has considered them (see The letter noted that the IRT's implementation plan has been published for public comment (see and that the IRT does not currently expect the developments in question to affect the timeline for transition to thick WHOIS. Here the Council will discuss the letter, and any actions it may wish to take or feedback it may wish to provide to the IRT on this topic.

6.1 – Summary and update (Amr Elsadr)

6.2 – Council discussion

6.3 – Next steps

Item 7: COUNCIL DISCUSSION – Community Budget Requests for Financial Year 2018 (15 minutes)

On 15 December 2016, ICANN launched the FY18 SO-AC Community Additional Budget Request process. This process concerns a dedicated part of the overall ICANN annual budget that is set aside to fund specific requests from the community for activities in that specific Financial Year not already included in the recurring ICANN budget. The deadline for submission of community budget requests for FY2018 is 30 January 2017. Following preliminary review by ICANN staff and community consultations at ICANN58 in March 2018, final assessments are expected to be made by mid-April in time for Board approval by the end of May. The proposed timeline, guidelines and request templates can be found at Here the Council will discuss whether, and what, additional specific FY18 budget requests it may wish to make (distinct from any requests individual GNSO Stakeholder Groups or Constituencies may submit).

7.1 – Summary (GNSO Council Chairs/ Rob Hoggarth)

7.2 – Council discussion

7.3 – Next steps

Item 8: COUNCIL DISCUSSION – Planning for ICANN58 (15 minutes)

The GNSO Council had agreed previously on the need to start planning early for ICANN58, and to confirm certain important sessions (including joint meetings with other SO/ACs and the ICANN Board) as fixed in the overall meeting schedule. Advance planning will be helpful for scheduling purposes, including for GNSO Stakeholder Groups and Constituencies, coordination between and with other SO/ACs, and ensuring that sufficient time is given over to policy development work. To assist in the Council's deliberations, staff compiled all GNSO Council input received on the ICANN58 Council Planning Survey: Based on the Council's deliberations at ICANN58 and its two December 2016 meetings, the Council Chairs, with the assistance of staff, have been developing a proposed ICANN58 schedule for the GNSO Council. The draft GNSO schedule was circulated on 19 January 2017 (see, and attempts to take into account the current overall block schedule (see Here the Council will continue its discussion of scheduling priorities for the GNSO at ICANN58.

8.1 – Status summary (GNSO Council leadership)

8.2 – Council discussion

8.3 – Next steps

Item 9: ANY OTHER BUSINESS (10 minutes)

Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i))


Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4)


References for Coordinated Universal Time of 21:00 UTC
Local time between October and March Winter in the NORTHERN hemisphere

California, USA (PST) UTC-8 +0DST 13:00
San José, Costa Rica UTC-6 +0DST 15:00
Iowa City, USA (CST) UTC-6 +0DST 15:00
New York/Washington DC, USA (EST) UTC-5 +0DST 16:00
Buenos Aires, Argentina (ART) UTC-3+0DST 18:00
Rio de Janeiro, Brazil (BRST) UTC-2 +0DST 19:00
London, United Kingdom (GMT) UTC+0DST 21:00
Bonn, Germany (CET) UTC+1+0DST 22:00
Cairo, Egypt, (EET) UTC+2 +0DST 23:00
Istanbul, Turkey (TRT) UTC+3+0DST (20 Jan 2017) 00:00
Singapore (SGT) UTC +8 +0DST (20 Jan 2017) 05:00
Tokyo, Japan (JST) UTC+9+0DST (20 Jan 2017) 06:00
Sydney/Hobart, Australia (AEDT) UTC+11+0DST (20 Jan 2017) 08:00

DST starts/ends on last Sunday of March 2017, 2:00 or 3:00 local time (with exceptions)

For other places see and