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

Final Proposed Agenda 13 July 2017 - GNSO Council Meeting

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 01 September 2016.

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:
14:00 Los Angeles; 17:00 Washington; 22:00 London; (Friday 14 July) 00:00 Istanbul; 07: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 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures:

Minutes of the meeting of the GNSO Council on 18 May 2017, posted on 5 June 2017.

Minutes of the meeting of the GNSO Council on 28 June 2017, circulated on 10th July 2017, to be posted on 20 July 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 (5 mins)

Following the adoption of the recommendations of the GNSO Standing Selection Committee during ICANN60, the GNSO Council leadership met and agreed that James Bladel would serve as the GNSO representative to the Empowered Community Administration until the end of his term at ICANN61. Following the adoption of this item, the GNSO Secretariat is requested to communicate this decision to the ICANN Secretary and the Empowered Community Administration.

Item 4: COUNCIL VOTE – Proposed Fundamental Bylaw Changes (15 minutes)

On 23 May 2017, the ICANN organization sent a notice to the Empowered Community (EC) that the ICANN Board has approved amendments to ICANN's Fundamental Bylaws to move the Board Governance Committee's reconsideration responsibilities to another Board Committee. This notice triggered the Bylaws-mandated process according to which the EC is to consider whether to approve the amendments before they can go into effect.

On 27 June 2017 at ICANN59, the first Community Forum under the revised ICANN Bylaws, discussed the proposal, where the EC came together to exercise one of the EC's new powers under the revised ICANN Bylaws.

Here, the Council will vote whether to adopt the Fundamental Bylaw change.

4.1 – Presentation of motion (James Bladel)

4.2 – Council Discussion

4.3 – Council vote (voting threshold: simple majority)

[PLACEHOLDER] Item 5: COUNCIL VOTE – Petition for a Rejection Action of the FY18 Operating Plan and Budget

On 24 June 2017, the ICANN Board adopted ICANN's FY18 Operating Plan and Budget, the FY18 IANABudget, and updates to the Five-Year Operating Plan. Under ICANN's post-IANA Stewardship Transition Bylaws, the Empowered Community has the ability to consider and, if they choose, initiate a rejection action as outlined in Annex D, article 2 of the ICANN Bylaws within 21 days following notification of the adoption by the FY18 Operating Plan and Budget by the ICANN Board.

The [placeholder community name] has submitted a petition for a rejection action [placeholder aspect of the budget] because of [reasons].

Here, the Council will vote whether it supports the petition for a rejection action concerning the FY18 Operating Plan and Budget.

5.1 – Presentation of motion (TBD)

5.2 – Council Discussion

5.3 – Council vote (voting threshold: simple majority)

Item 6. COUNCIL VOTE – Approval of GNSO Council Review of the GAC Communique from Johannesburg (10 minutes)

The GNSO Council has adopted the practice of providing feedback to the ICANN Board on matters pertaining to gTLD policy, where the Governmental Advisory Committee (GAC) has included advice on such matters as part of a GAC Communique issued at each ICANN Public Meeting. Following the issuance of the GAC Johannesburg Communique (, a team of Councilors and the current GNSO Liaison to the GAC agreed to prepare an initial draft of possible GNSO Council input to the Board for Council consideration. This draft was circulated to the Council mailing list on 9 July 2017 (

Here the Council will discuss the draft Council feedback, and vote on whether or not to approve it for transmission to the ICANN Board.

6.1 – Presentation of motion (James Bladel)

6.2 – Council discussion

6.3 – Council vote (voting threshold: simple majority)

Item 7: COUNCIL Vote – Next steps in relation to Charter for the Cross Community Working Group on Internet Governance (20 minutes)

At ICANN57 in Hyderabad in November 2016, the GNSO Council approved a motion conditioning the future participation of the GNSO as a Chartering Organization of the CCWG on Internet Governance (CCWG-IG) upon a comprehensive review of the group's Charter by the CCWG-IG, in accordance with the Framework of Uniform Principles for CCWGs that had been adopted recently by the ccNSO and GNSO Councils ( In its resolution, the GNSO Council had noted that the CCWG-IG's future work is expected to be subject to a clear work plan, with regular updates and clear deliverables, and had requested that, by ICANN58, the CCWG-IG was to report on its findings, which report may include a revised charter, and the CCWG-IG was to also consider whether it will be preferable to reconstitute the group under a new structure ( - 20161107-3). The CCWG-IG provided a written report on its 2016 activity and a draft revised Charter for the GNSO Council's consideration on 10th March 2017 (

At its Public Meeting at ICANN58 in Copenhagen on 15 March 2017 and its joint meeting with the ccNSO Council on 13 March 2017, the Council engaged in a discussion with the CCWG-IG co-chairs regarding the group's reports. At the GNSO Council's call on 18 May 2017, the Council continued its discussion of the topic as well as during ICANN59 during which it became clear that although there is strong support to continue the GNSO's involvement in Internet Governance, a CCWG is not considered the appropriate vehicle for such involvement..

Here the Council will consider the motion that has been submitted in relation to this topic.

7.1 – Presentation of motion (Keith Drazek)

7.2 – Council discussion

7.3 – Council vote (voting threshold: simple majority)         

Item 8. COUNCIL DISCUSSION – Possible Change to the Name of the GNSO (10 minutes)

Some in the community have noted that as domain names are available globally, the term "generic" has certain meanings to different parts of the ICANN community, that the usage of "generic" to describe a .brand is potentially confusing, and among other reasons, that it might make sense to substitute the word "Generic" for "Global" in Generic Names Supporting Organization.

Here, the GNSO Council will consider whether a change of this nature should be considered and if so, discuss next steps to effectuate that change.

8.1 – Introduction of topic (Paul McGrady)

8.2 - Council discussion

8.3 – Next steps

Item 9: COUNCIL DISCUSSION – Cross Community Working Group on the Use of Country and Territory Names (15 minutes)

On 26 March 2014, the GNSO Council resolved to approve the charter for the Cross Community Working Group on the Use of Country and Territory Names (CWG-UCTN). The purpose of the CWG-UCTN was to assess the feasibility of developing a harmonized framework for the use of country and territory names that could be applicable across the respective Supporting Organizations and Advisory Committees.

On 24 February, the CWG-UCTN published its Interim Report for public comment. While the CWG-UCTN considered two and three-character country codes, it was determined that consensus was not feasible; the group did not consider full country and territory names. The CWG-UCTN therefore recommended that the CWG be closed, that policy efforts within the community should be consolidated, and that future work must be fully inclusive of the community.

As a Chartering Organization, the GNSO is expected to consider the CWG-UCTN's Final Report and determine next steps.

Here, the Council will discuss the Final Report and its recommendations and consider next steps (Letter from CWG UCTN co-Chairs to GNSO and ccNSO Chairs 25 June 2017).

9.1 – Update on current status (Heather Forrest)

9.2 – Council discussion

9.3 – Next steps


During ICANN59, the proposed block schedule for ICANN60 was shared ( – note that further updates are expected to be based on input received from the SO/AC Planning Committee). Based on requests received to date from the different GNSO PDP WGs, CCWGs and WGs, the Council leadership has put together a draft GNSO schedule for Council input and review. Following Council review, this draft GNSO schedule will be shared with the GNSO Stakeholder Groups and Constituencies to facilitate their planning and scheduling.

10.1 - Update on planning for ICANN60 (Council leadership)

10.2 – Council discussion

10.3 – Next steps

Item 11: ANY OTHER BUSINESS (5 minutes)

11.1 - Update from the New gTLD Subsequent Procedures PDP WG co-chairs on their anticipated next steps for collaborating with the community to address geographic names at the top-level.

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 March and October Summer in the NORTHERN hemisphere

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

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

For other places see and