Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://icann-community.icannatlassian.orgnet/wiki/x/xBUFBQ1cOeBg
This agenda was established according to the GNSO Operating Procedures v3.3, updated on 30 January 2018
For convenience:
...
1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures:
Minutes of the GNSO Council meeting on the 24 May 2018 were posted on 14 June 2018
...
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 minutes)
...
On 2 November 2017, the ICANN Board, in considering SAC095, adopted the following:
Resolved (2017.11.02.09), the Board hereby directs that conformance to IDNA2008 and its successor will continue to be a necessary condition to determine valid IDN TLD labels.
Resolved (2017.11.02.10), the Board requests that the Country Code Names Supporting Organization (ccNSO) and the Generic Names Supporting Organization (GNSO) engage with the SSAC to more fully understand the risks and consequences of using a domain name that includes emoji in any of its labels, and inform their respective communities about these risks.
Resolved (2017.11.02.11), the Board requests that the ccNSO and GNSO integrate conformance with IDNA2008 and its successor into their relevant policies so as to safeguard security, stability, resiliency and interoperability of domain names.
Resolved (2017.11.02.12), the Board directs the ICANN CEO, or his designee(s), to engage with gTLD and ccTLD communities on the findings and recommendations in SAC095
...
Here, the Council will vote on whether or not to request delivery of the Final Report by the Council’s July meeting.
5.1 – Presentation of motion (Heather Forrest)
5.2 – Council discussion
...
The ccNSO and RySG appointed members to form the Charter Review Team from their respective SO and SG to conduct a review of the Customer Standing Committee (CSC) Charter in accordance with the Terms of Reference. The CSC Charter review team (RT) sought comment and input on its findings and proposed amendments to the CSC Charter, as included in the RT's Initial Report.
On 11 May 2018, Council member volunteers were sought to develop a draft comment for Council consideration forpublic comment on the Initial Report on Review of the CSC Charter. The Council discussed the Initial Report during their meeting on 24 May 2018 and submit their comments during the public comment process.
Taking into account comments received, the Review Team prepared a Final Report and Amended Charter for consideration and adoption by the ccNSO and GNSO Councils.
Here, the Council will vote to approve the changes made to the CSC Charter as a result of the Charter Review Process.
6.1 – Presentation of motion (Donna Austin)
6.2 – Council discussion
...
On 03 May 2017, the Council resolved to initiate the Section 16 process as requested by the Board, which resulted in the limited reconvening of the original PDP on Protection of IGO and INGO Identifiers in All gTLDs.
...
On 11 May 2018, ICANN released theTemporary Specification on gTLD Registration Data, which served as the main agenda topic for the subsequent Board Workshop in Vancouver. This proposed Temporary Specification provides an interim solution until the community completes a policy development process on the temporary specification which is expected to complete within a one year period.
On 14 May 2018, ICANN released arevised Temporary Specification and scheduled a webinar on 15 May 2018 to discuss the topic. The Board passed aresolution, noting their intent to adopt the Temporary Specification on or around 17 May 2018.
On 17 May 2017, the ICANN Boardapproved the proposedTemporary Specification for gTLD Registration Data, which establishes temporary requirements for how ICANN and its Contracted Parties will comply with both ICANN contractual requirements and the European Union’s General Data Protection Regulation (GDPR). On 21 May 2018, the Council and SG/C chairs met to discuss possible next steps for the ICANN Board adoption of the Temporary Specification.
On its 24 May 2018 meeting, the Council discussed possible next steps following ICANN Board adoption of the Temporary Specification. On 5 June 2018, the Council met with the ICANN Board to discuss a set of questions the Council and ICANN Board developed, as well as overall next steps. Subsequently, Council leadership and staff developed a Mindmapto help understand the elements around a potential Expedited Policy Development Process (EPDP), such as timing, team composition, and planning for ICANN62.
...
Here, the Council will vote to initiate an EPDP on the Temporary Specification, as well as to adopt the EPDP’s charter.
8.1 – Presentation of motion (Council Leadership)
8.2 – Council discussion
8.3 – Council vote (voting threshold: Supermajority)
Taking this action is within the GNSO’s remit as outlined in ICANN’s Bylaws as the GNSO ‘shall be responsible for developing and recommending to the Board substantive policies relating to generic top-level domains and other responsibilities of the GNSO as set forth in these Bylaws’ (Art.11.1). Furthermore, this action complies with the requirements set out in Annex A-1 GNSO Expedited Policy Development Process of the ICANN Bylaws as well as the EPDP Manual.
Item 9: ANY OTHER BUSINESS (15 minutes)
...