January 2018 - council - lists.icann.org

Draft GNSO Council comments on Operating Standards for Specific Reviews
by Austin, Donna 25 Jan '18

25 Jan '18

All Please find attached draft GNSO Council comments on Operating Standards for Specific Reviews. These comments have been drafted by Susan Kawaguchi, Darcy Southwell and myself and are not submitted to Council for consideration. I think the comments are in really good shape with one exception: 3.15 that addresses removal of review team members. So it would be appreciated if folks could pay particular attention to that section. The aim is to have the comments approved during our Council meeting on 30 January, in order to submit the comments by the deadline of 2 February. https://www.icann.org/public-comments/reviews-standards-2017-10-17-en https://www.icann.org/en/system/files/files/draft-operating-standards-speci… Look forward to your input. Thanks Donna Donna Austin Neustar, Inc. / Senior Policy Manager, Registry Solutions Mobile: +1 310 890 9655 donna.austin(a)team.neustar<mailto:donna.austin@team.neustar> / Website: home.neustar<http://www.home.neustar/> Follow Neustar: LinkedIn<http://www.linkedin.com/company/5349> / Twitter<http://www.twitter.com/neustar> Reduce your environmental footprint. Print only if necessary. ________________________________ The information contained in this email message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this email message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.

4 7

Draft GNSO Council comments on Proposed Incremental Changes to ICANN Meetings Strategy
by Austin, Donna 25 Jan '18

25 Jan '18

All Please find attached draft GNSO Council comments on Proposed Incremental Changes to ICANN Meetings Strategy. These comments have been drafted by Michele Neylon, Carlos Raul Gutierrez and myself and are now submitted to Council for consideration. These comments include some high level comments about ICANN meetings that go beyond the intended scope of the public comment being sought. Michele, Carlos and I understand that the Council as a whole may not agree with the general sentiment of the comments and as such welcome your feedback. The aim is to have the comments approved during our Council meeting on 30 January, in order to submit the comments by the deadline of 1 February. https://www.icann.org/public-comments/proposed-changes-meetings-strategy-20… https://community.icann.org/download/attachments/45744715/Meeting-Strategy-… Thanks Donna Donna Austin Neustar, Inc. / Senior Policy Manager, Registry Solutions Mobile: +1 310 890 9655 donna.austin(a)team.neustar<mailto:donna.austin@team.neustar> / Website: home.neustar<http://www.home.neustar/> Follow Neustar: LinkedIn<http://www.linkedin.com/company/5349> / Twitter<http://www.twitter.com/neustar> Reduce your environmental footprint. Print only if necessary. ________________________________ The information contained in this email message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this email message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.

3 4

Safe travels and informal get-together on arrival in LA
by Heather Forrest 25 Jan '18

25 Jan '18

Dear colleagues, We're nearing go-time for travel to LA (thanks to the international date line, I arrive in LA *before *I departed Melbourne - truly bizarre). Staff, Council leadership and our facilitator Jonathan Robinson will be at the venue over the weekend to get things ready for our start on Monday morning. For all those interested in an informal hello over drinks on arrival day, we have reserved space at the Doubletree Hotel bar on Sunday evening from 1800. Best wishes and safe travels to everyone, see you soon, Heather

2 1

Re: [council] FW: Motion and charter - Adoption of the charter for the ICANN Procedure For Handling WHOIS Conflicts with Privacy Law Implementation Advisory Group (WHOIS Procedure IAG)
by Heather Forrest 24 Jan '18

24 Jan '18

Dear colleagues, The version of the draft charter circulated for document deadline contained an unresolved question that had been raised by Pam Little (RrSG). Following discussions with Pam, I would like to propose the attached revisions, which I understand to be semantic in nature and not affecting the substance (ie, edits to clarify the intention rather than change the scope of the group's efforts or outcomes), as friendly amendments for the Council's consideration. Many thanks to Pam for her willingness to discuss and reach a way forward with plenty of time for us all to consider these before next Tuesday. I note that one decision remains, which is the question of whether policy or GDD staff should support the effort. I encourage those with experience of the previous IAG to weigh in. Best wishes, Heather On Sun, Jan 21, 2018 at 11:07 AM, Austin, Donna <Donna.Austin(a)team.neustar> wrote: > All > > > > The deadline for submitting motions for the Council meeting on 30 January > 2018, is today 20 January 2018 at 23:59 UTC. > > > > Rafik and I were reminded that the deadline was looming about two hours > ago by Marika. In accordance with Heather’s email of 18 January 2018, to > this list, we agreed that in the absence of being able to find anyone on > this distribution list to submit the motion and charter to meet the motion > deadline, I would do it. > > > > To that end it is important that you all review the Charter as submitted > to be sure that the version is correct. In the interests of time, Pam’s > edits were accepted, but her question regarding impact analysis was not > addressed. I’m sure we can swap it out if necessary, citing administrative > error. > > > > Donna > > > > > > *From:* council [mailto:council-bounces@gnso.icann.org] *On Behalf Of *Austin, > Donna via council > *Sent:* Saturday, January 20, 2018 3:49 PM > *To:* council(a)gnso.icann.org > *Subject:* [EXTERNAL] [council] Motion and charter - Adoption of the > charter for the ICANN Procedure For Handling WHOIS Conflicts with Privacy > Law Implementation Advisory Group (WHOIS Procedure IAG) > > > > All > > > > Please find attached the motion for the “Adoption of the charter for the > ICANN Procedure For Handling WHOIS Conflicts with Privacy Law > Implementation Advisory Group (WHOIS Procedure IAG)” along with the > proposed Charter for consideration during our next Council call on 30 > January 2018. > > > > Thanks > > > > Donna > > >

2 1

Terms of Reference - Work Track 5 - New gTLD Subsequent Procedures PDP WG
by Emily Barabas 24 Jan '18

24 Jan '18

Dear Councilors, As you may recall, the New gTLD Subsequent Procedures Policy Development Process Working Group established a sub-team, known as Work Track 5, in late 2017 to address the issue of geographic names at the top level. Work Track 5’s first task was to agree upon a Terms of Reference (ToR) document describing the scope of work and methods for completing this work. Please find the ToR attached, which closely follows the format of a GNSO Working Group charter. The Terms of Reference document is also available on the Work Track wiki: https://community.icann.org/x/RgS8B. If you have any questions, please do not hesitate to contact the leadership team, copied here. Kind regards, Emily Emily Barabas | Senior Policy Specialist ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

1 0

Re: [council] Additional budget requests
by Michele Neylon - Blacknight 24 Jan '18

24 Jan '18

Marika Thanks for sharing these with us. Personally I think all 3 make a lot of sense and support core activities. * GNSO Council strategic session – while we haven’t had the first of these yet it makes a lot of sense that we take a few days to do advance planning without the distractions we commonly encounter within the normal meeting cycle * PDP leadership support – this makes a lot of sense. The people who are putting in the time and energy to drive policy development often do so with little or no support and this has a chilling effect. Being able to provide travel support could help a lot. * PDP / WG signup automation – seems logical and self-explanatory to me. Our budget request might be rejected if ICANN has it already on their budget and plan, but requesting it could help ensure that it actually gets done in a timely fashion, unlike some other internal projects that seem to take forever without any tangible progress Regards Michele * -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ https://ceo.hosting/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265, Ireland Company No.: 370845 From: council <council-bounces(a)gnso.icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Wednesday 24 January 2018 at 01:23 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Additional budget requests Dear All, Please find attached for your review the proposed Council Additional Budget Requests. See also item 6 on the Council Agenda (Council Discussion – Update on potential FY19 GNSO Additional Budget Requests). The deadline for submission is 31 January 2018. Best regards, Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

Additional budget requests
by Marika Konings 24 Jan '18

24 Jan '18

Dear All, Please find attached for your review the proposed Council Additional Budget Requests. See also item 6 on the Council Agenda (Council Discussion – Update on potential FY19 GNSO Additional Budget Requests). The deadline for submission is 31 January 2018. Best regards, Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

For your review: Projects List
by Nathalie Peregrine 23 Jan '18

23 Jan '18

Dear Councilors, Attached please find the updated Project List in both red-line and clean version for your review before the Council meeting. If there are no comments, the list will be posted on the website on page: http://gnso.icann.org/en/council/project<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc…> and be directly viewed at :http://gnso.icann.org/meetings/projects-list.pdf<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_meetings…> Thanks so much, Kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Re: [council] Please read: GNSO Council Strategic Planning Session
by Michele Neylon - Blacknight 23 Jan '18

23 Jan '18

Thanks Marika Re: transport from the airport – the ride sharing pickup areas are very well signposted at LAX. Personally I prefer using Lyft – if anyone wants a discount code let me know ☺ See you all in a few days. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ http://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: council <council-bounces(a)gnso.icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Monday 22 January 2018 at 21:14 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Please read: GNSO Council Strategic Planning Session Sending on behalf of the Council Leadership ___ All Please find attached two versions of the Agenda for our Strategic Planning Session to be conducted next week in Los Angeles. One is a simple version of the agenda that gives you a good overview of the three days, while the detailed agenda provides you with more information about the goals/objectives for each session along with required reading. The required reading is an important part of your preparation for the three days and we sincerely hope that you will take the time to either refresh your memory of a number of the documents or make yourself familiar with them for the first time. It is our hope that as we work through the agenda and discuss the relevance and importance of these documents it will provide us all with a working understanding of how they apply in our work as the GNSO Council. In order to assist you in this regard, a Google drive has been created that contains all the materials that are required to be reviewed and read prior to the meeting, as well a number of documents that provide additional background information but which are of an optional nature (Please see here<https://drive.google.com/drive/u/1/folders/1BZtK5S4pC1Fx9hkieNS5Nm1WwPvM1-yF>). The detailed agenda identifies the documents that will be relevant to each day. Please make sure to take the time to review at a minimum the required documents as it will be imperative to have a common understanding and background with regards to the topics under discussion. Logistical information: In addition, the agenda and practical information regarding the meeting and location can be found in the General Information folder (please see here<https://drive.google.com/drive/u/1/folders/1z0aKG5A4p4mMLOlnsK-kK3ZJbfT4CEpW>). Look forward to seeing you all next week and don't hesitate to ask any questions. Heather, Donna & Rafik

1 0

Re: [council] [gnso-secs] Final Proposed Agenda GNSO Council Meeting - 30 January 2018 at 22:00 UTC
by Nathalie Peregrine 22 Jan '18

22 Jan '18

Dear all, Please find the updated GNSO Council agenda updated here with the Whois conflicts draft charter and the incremental changes to the ICANN meeting strategy draft response. For your convenience, the agenda is posted and regularly updated here: https://community.icann.org/x/ZwCfB Kind regards, Nathalie From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Saturday, January 20, 2018 at 11:31 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Final Proposed Agenda GNSO Council Meeting - 30 January 2018 at 22:00 UTC Councilors, Please below find the final proposed agenda for the GNSO Council Meeting on 30 January 2018 at 22:00 UTC. This has been posted on the GNSO Council meeting wiki page and on the GNSO master calendar[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>. Final proposed agenda 30 January 2018 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/bgCfB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> This agenda was established according to the GNSO Operating Procedures<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> 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: 22:00 UTC: https://tinyurl.com/y8v2lryd[tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_y8v2lryd&d…> 14:00 Los Angeles; 17:00 Washington; 22:00 London; (Wednesday 31 January) 03:00 Islamabad; 07:00 Tokyo; 09:00 Hobart GNSO Council Meeting Audio Cast To join the event click on the link: http://stream.icann.org:8000/stream01.m3u[stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> 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[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_meet…> of the GNSO Council meeting on the 30 November were posted on 21 November 2017. Minutes[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_meet…> of the GNSO Council meeting on the 21 December 2017 were posted on 8 January 2018. 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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>and Action Item List[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Item 3. Consent Agenda (0 min) None Item 4: COUNCIL VOTE – Adoption of the Revisions to GNSO Operating Procedures and Recommendations for Amendments to ICANN Bylaws (15 minutes) On 27 May 2016, the ICANN Board adopted[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> a set of new ICANN Bylaws which became effective upon the expiration the IANA Functions Contract between ICANN and NTIA. Accordingly, on 30 June 2016, the GNSO Council established[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> a Drafting Team to identify all the new or additional rights and responsibilities that the GNSO has under the revised Bylaws. On 12 October 2016, the Drafting Team submitted its Final Report<http://mm.icann.org/pipermail/gnso-bylaws-dt/2016-October/000145.html> to the GNSO Council. On 01 December 2016, the GNSO Council accepted[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> the recommendations in the Drafting Team’s Final Report and directed staff to draft proposed language for any necessary modifications or additions to the GNSO Operating Procedures and, if applicable, those parts of the ICANN Bylaws pertaining to the GNSO. On 19 June 2017, ICANN staff published[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> its proposed changes to the GNSO Operating Procedures and ICANN Bylaws to implement the DT recommendations for public comment. Public comment closed on 10 August 2017 and staff published the Report of Public Comments[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>. The proposed changes were discussed on the GNSO Council’s 20 September 2017 meeting and again during the GNSO Council’s Strategic Planning sessions on 26 January 2018. Here, the Council will vote to adopt the proposed revisions to the GNSO Operating Procedures and the recommended amendments to the ICANN Bylaws. 4.1 – Presentation of motion (Heather Forrest) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) Item 5: COUNCIL VOTE – Adoption of the Charter related to the next steps for the ICANN Procedure of Handling WHOIS conflicts with Privacy Law (15 minutes) As a result of community input and the work of the Implementation Advisory Group (IAG), ICANN made effective the revised WHOIS Conflicts with Privacy Law Procedure[whois.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__whois.icann.org_en_rev…> on 18 April 2017 to better accommodate issues where WHOIS requirements conflict with applicable laws. As requested by this GNSO Council, ICANN published a paper[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> for public comment[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> to provide analysis and solicit community input on the practicality and feasibility of the triggers identified in the revised WHOIS Conflicts with Privacy Law Procedure. The public comment period was also intended to collect suggestions for moving forward with the review. The public comment period closed on 7 July 2017 and the staff report of public comments[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> was published on 28 July 2017. On 1 August 2017, the Council received a letter[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_corr…> from Akram Atallah providing a collection of possible options for proceeding with the review, and offering to discuss those options or others identified by Council. On 24 August 2017, the Council received an update from GDD staff and discussed possible options for moving forward with the review of the Procedure for Handling WHOIS Conflicts with Privacy Law. A small group of Councilors have prepared a Charter (including guidelines and parameters around scope, deliverables, composition, operating procedures, etc.) pursuant to which a subsequent group will operate as it deliberates and provides suggested next steps and/or recommendations. Here, the Council will vote to approve the Charter. 5.1 – Presentation of motion (TBD) 5.2 – Council Discussion 5.3 – Council vote (voting threshold: simple majority) Item 6: COUNCIL DISCUSSION – Update on potential FY19 GNSO Additional Budget Requests (15 minutes) On 5 December 2017, ICANN launched[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> the FY19 SO/AC Additional Budget Request Process, with a due date of 31 January 2018 for community requests. During the FY18 cycle, the GNSO requested and was granted two Additional Budget Requests: 1) GNSO Council Strategic Planning Session Pilot Project; and 2) GNSO PDP WG Chairs Support Pilot Project. For FY19, the GNSO Council is proposing to again request those two successful items, along with a third request to fund a Working Group sign-up and management tool. Here, the Council will discuss the proposed Additional Budget Requests for FY19. 6.1 – Presentation of discussion topic (Council Leadership) 6.2 – Council Discussion 6.3 – Next Steps Item 7: COUNCIL DISCUSSION – GNSO Council Public Comment to the Proposed Incremental Changes to the ICANN Meetings Strategy (10 minutes) On 02 February 2013, the ICANN Board resolved[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> to establish the Multi-Stakeholder Meeting Strategy Working Group (MSWG), allowing community members and the Board to work together to develop a meeting strategy that aligns with community needs. On 25 February 2014, the MSWG published its report<https://meetings.icann.org/en/mswgrecommendations-icannfuturemeetingsstrate…> and recommendations for public comment. The recommendations of the MSWG led to the current structure now in place (i.e., Meeting A, B, and C). Many in the community are generally supportive of the new and now existing structure, but still see room for improvement. On 17 August 2017, community leaders and ICANN staff held a discussion[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> regarding possible changes to ICANN meetings and the venue selection process. The potential changes envisioned are generally considered adjustments to the existing meeting strategy rather than a wholesale change to that meeting strategy. On 14 December 2017, the Proposed Incremental Changes to the ICANN Meetings Strategy was published for public comment[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…>. A small group of Councilors have prepared a draft public comment response. Here, the Council will discuss the potential response and ensure that there are no objections to the submission of the public comment. 7.1 - Presentation of discussion topic (Council leadership) 7.2 – Council discussion 7.3 – Next steps Item 8: COUNCIL DISCUSSION – GNSO Council Public Comment to the Operating Standards for ICANN’s Specific Reviews (10 minutes) Under ICANN’s Bylaws[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, four specific reviews are required: Competition, Consumer Trust and Consumer Choice Review, the Security, Stability, and Resiliency of the DNS Review, the Accountability and Transparency Review, and the Registration Directory Service Review. Section 4.6[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> of the Bylaws further calls for Operating Standard for these Specific Reviews, which are intended to provide consistency, clarity, and transparency around the reviews. On 17 October 2017, ICANN published a draft set of Operating Procedures[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> for public comment[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…>, seeking feedback in particular on scoping and review team composition. A small group of Councilors have prepared a draft public comment response. Here, the Council will discuss the potential response and ensure that there are no objections to the submission of the public comment. 8.1 - Presentation of discussion topic (Council leadership) 8.2 – Council discussion 8.3 – Next steps Item 9: COUNCIL DISCUSSION – Review of Second Security, Stability, and Resiliency (SSR2-RT) Letter from GNSO Council to SO/AC leadership (10 minutes) The Security, Stability, and Resiliency Review, mandated by the ICANN Bylaws, assembled its review team and began administrative and step steps in early 2017. During ICANN60 in Abu Dhabi, the ICANN Board paused the second community-driven review of ICANN’s Security, Stability, and Resiliency Review Team (SSR2-RT[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>). Following ICANN60, the SSR2-RT members prepared a matrix of members’ skills and expertise and an evaluation of the scope of the review. As there is no established process by which to re-start the SSR2-RT, the SO/AC leaders have been collaborating since ICANN60 on the process to re-starting this important review effort. The GNSO Council will discuss the issue with a view to sharing its findings with the SO/AC leaders through the Council Chair. In order to inform the wider community of the GNSO Council’s intentions, a small group of Councilors have drafted a letter to be shared with SO/AC leaders. Here, the Council will discuss the draft letter and ensure that there are no objections to the transmission of the letter to SO/AC leaders. 9.1 - Presentation of discussion topic (Council leadership) 9.2 – Council discussion 9.3 – Next steps Item 10: ANY OTHER BUSINESS (0 minutes) 10.1 – Planning for ICANN61 ________________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11[icann…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf[gnso.icann.o…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>. References for Coordinated Universal Time of 22:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-8 14:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EDT) UTC-5 17:00 Buenos Aires, Argentina (ART) UTC-3 19:00 Rio de Janeiro, Brazil (BRST) UTC-2 20:00 London, United Kingdom (GMT) UTC 22:00 Paris, France (CEST) UTC+1 23:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 23:00 Islamabad, Pakistan (PKT) UTC+5 (+ 1 day) 03:00 Singapore (SGT) UTC+8 (+ 1 day) 06:00 Tokyo, Japan (JST) UTC+9 (+ 1 day) 07:00 Sydney/Hobart, Australia (AEDT) UTC+11 (+ 1 day) 09:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 25 of March 2018, 2:00 or 3:00 local time (with exceptions) for EU countries. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com[timeanddate.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_&d=…> and https://tinyurl.com/y8v2lryd[tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_y8v2lryd&d…>

1 0