May 2018 - council - lists.icann.org

Final Proposed FY19 Operating Plan and Budget
by Ayden Férdeline 22 May '18

22 May '18

The final proposed FY19 Operating Plan and Budget has now been published: https://www.icann.org/news/blog/final-proposed-fy19-operating-plan-and-budg… Per page 26 of Document 2, it would appear that our Strategic Planning Session was recommended for approval in FY19, however only for two days (rather than the three days which had been requested). Ayden Férdeline

1 0

Attendance, MP3, AC recording and chat/ Webinar: Next steps temporary policy / specification by the ICANN Board/ interim model for GDPR Compliance Monday 21 May 2018 at 21:00 UTC
by Terri Agnew 22 May '18

22 May '18

Hi all, Please find below the mp3, Adobe Connect recording and attached is the attendance, AC Chat and slide presentation from the Webinar: Next steps temporary policy / specification by the ICANN Board/ interim model for GDPR Compliance held on Monday, 21 May 2018 at 21:00 UTC. MP3: https://audio.icann.org/gnso/gnso-gdpr-compliance-temporary-policy-next-step s-21may18-en.mp3 Adobe Connect Recording: <https://participate.icann.org/p9az32xuzvu/?OWASP_CSRFTOKEN=0d56dfabb1e399a6 01c2e50edc78ad9da59687b5c9871332cbe14e6cd14c2cc8> https://participate.icann.org/p9az32xuzvu/ Recordings, transcript, AC Chat transcript and presentation are located on the GNSO Calendar: https://gnso.icann.org/en/group-activities/calendar Thank you. With kind regards, Terri --- Terri Agnew Operations Support - GNSO Lead Administrator Internet Corporation for Assigned Names and Numbers (ICANN) Email: <mailto:terri.agnew@icann.org> terri.agnew(a)icann.org Skype ID: terri.agnew.icann Find out more about the GNSO by taking our interactive courses and visiting the <https://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy -efforts.htm#newcomers> GNSO Newcomer pages Follow @GNSO on Twitter: <https://twitter.com/ICANN_GNSO> https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: <https://www.facebook.com/icanngnso/> https://www.facebook.com/icanngnso/ <http://gnso.icann.org/en/> http://gnso.icann.org/en/

1 0

Notes and action items from today's next steps regarding temporary policy in relation to GDPR compliance meeting
by Marika Konings 21 May '18

21 May '18

Dear All, Please find below the notes and action items from today’s call. Attached you will find the slides shared during the meeting. The link to the recording and chat transcript will be circulated shortly. Best regards, Marika ============================== Notes and Action items next steps regarding temporary policy in relation to GDPR compliance on Monday 21 May 2018 at 21:00 UTC. See proposed agenda & slides: * Background * Current status & objectives * Proposed immediate next steps * Questions * Reference slides: EPDP Initiation Request / Draft EPDP Timeline * Discussion & next steps Objective of today's meeting is to discuss procedure and process, not substance. A number of procedural steps that need to be decided upon first, substance is for subsequent discussions. Flexibility likely needed in the charter as there is a likelihood that there may be further changes to the temporary specification as the Board is required to renew the temporary specification every 90 days. Will need to confirm with the Board whether changes are possible or whether it is only a reconfirmation of the originally adopted temporary specification. If changes are possible, what impact does that have on the PDP, does the clock restart? Need clarification from the Board on intention and exact scope of the PDP. Are multiple tracks within the PDP an option or if the scope is narrow question, or would a parallel PDP be needed to consider a possible wholesale replacement for the temporary specification? Need to get clarity on which tracks are on 1 year clock and whether other tracks may have more flexibility. Need to see list of policies and contractual clauses that are impacted by the temporary specification. Proposed Immediate Next Steps (slide 5) Action item #1: Need to confirm who would be on a follow up call with the ICANN Board (discuss during Thursday's Council meeting - 24 May) Action item #2: If an EPDP is to be initiated, need to put together a drafting team to develop proposed EPDP Initiation Request. Action item #3: Schedule additional Council meeting, possibly for 14 June (if agreement that it would be helpful to be able to consider possible EPDP Initiation Request prior to Panama) Questions (slide 6) EPDP * Expedited PDP seems to be the only option that would meet the timetable available. * EPDP has to be initiated by Council. Supermajority support needed which means that nearly everyone needs to be on board with this approach if this path is chosen. If Council does nothing, Board will initiate a PDP which would take Council partly out of the driver's seat. * Need to ensure that cope of work is realistic to deliver on within a year. * May need an implementation check-list / parallel track that keeps track in parallel of implementation and implementation related issues to not have any kind of delay at the end of the process. * Feedback from RDS PDP leadership team was that it was not feasible to repurpose that WG - Council will need to consider what happens with that effort in the meantime. Council to consider whether to terminate or suspend the PDP. See process outlined in the PDP Manual. May need direction from RDS PDP leadership team. May first need to understand the requirements of this effort, but doubt that it is possible to continue the RDS PDP WG at the same time as the EPDP. * Need to decide which issues need to be decided within 365 days, which issues can be dealt with on a separate track or work stream 2 kind of approach. EPDP Team Composition (see options outlined in attached possible next steps document) * In order for this to succeed, it needs a relatively small and committed group, willing to work towards consensus. * Need to keep group small. * Consider read-only access to mailing list for non-members (publicly archived) to keep discussions focused. * Need to think of ways to make it inclusive/transparent while keeping it effective. * Responsibility and representation is key. Members would need to buy-in / sign off on the responsibilities associated with being a member. Need to work with respective groups that have appointed member to ensure positions are agreed to / signed off on. * Lessons learned from RDS PDP WG may help in avoiding mistakes previously made. * SG/Cs could apply mechanisms that were used in the CWG-Stewardship related work for internal discussions and consultations. * Consider also the input provided in response to PDP3.0 discussions. * CCWG minus model may meet requirements - not too exclusive or too inclusive to be disruptive. * Cannot have people coming in cold - need some level of expertise / knowledge on the subject. * Consider limiting membership to max 2 members per SG, instead of 3. EPDP Leadership * May be difficult to find someone with no strong position. * Need clear and direct link to Council. Is liaison role the right one here or is something different needed. If a liaison is appointed, this would be a major responsibility. * Could/should Council leadership take a proactive role? * Need to balance Council involvement so that it is not to the detriment of other PDPs. EPDP Working Methods * How to optimize F2F time and is more F2F time needed? Until exact scope is known, it may be difficult to determine what additional F2F time is needed, if any. Could consider meeting prior to ICANN meetings like CCWG-Accountability? Look at experience of other groups. * Resources needed will need to be part of the discussion with the Board as it has not been specifically budgeted for (as this was not on the cards when original budget was developed). * Need mechanism to inform broader community - for example, monthly general assembly. Timeline - See slide 10 * Council needs to set this up for success. Need to identify all questions, all variables so that when it is handed over to the EPDP, the Council has done the best it can in doing the necessary preparatory work to allow EPDP team to focus on the substance. Try to get it in a good position to kick things off at ICANN62 in Panama. Action item #4: discuss on Council meeting on Thursday 24 May formation of drafting team to draft EPDP initiation request as well as EPDP Charter From: council <council-bounces(a)gnso.icann.org> on behalf of Heather Forrest <haforrestesq(a)gmail.com> Date: Monday, May 14, 2018 at 16:20 To: "arzaneh.badii(a)gmail.com" <arzaneh.badii(a)gmail.com>, "joan(a)npoc.org" <joan(a)npoc.org>, Joan Kerr <joankerr(a)fbsc.org>, Renata Aquino Ribeiro <raquino(a)gmail.com>, Paul Diaz <pdiaz(a)pir.org>, Graeme Bunton <gbunton(a)tucows.com>, "Selli, Claudia" <cs574w(a)intl.att.com>, Brian Winterfeldt <Brian(a)winterfeldt.law>, Wolf-Ulrich Knoben <wolf-ulrich.knoben(a)t-online.de>, GNSO Council List <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Fwd: RDS message for circulation Dear Council colleagues, SG/C Chairs, On behalf of Council leadership, I would like to invite you to an informational webinar to discuss possible next steps in preparation for a possible adoption of a temporary policy / specification by the ICANN Board in relation to the interim model for GDPR Compliance. This webinar will be scheduled on Monday 21 May at 21.00 UTC. The adoption of a temporary policy by the ICANN Board contemplates a Policy Development Process (PDP) which would need to be completed within the one-year timeline following adoption of the temporary policy. To ensure readiness of the GNSO Council in its role as manager of the PDP, Council leadership has documented possible next steps and related questions for your consideration (see attached document). These questions are purely focused on the process aspect of a possible expedited policy development process, as the substance will be dealt with at a subsequent stage. We are aware that there may be disagreement with regards to the approach ICANN Org and/or the ICANN Board are taking, but this is not the subject of our conversation, or the Council’s responsibility at this stage. What the Council will be responsible for is creating the optimal circumstances to allow this (E)PDP to succeed. As you can see from the draft timeline, time is of the essence. As such, it is of key importance that we work collaboratively and diligently, taking responsibility for and ownership of this important task. We hope we can all count on your support and commitment. Rafik, Donna and I hope that as a result of this meeting Council members will be prepared to confirm a direction and next steps at our May GNSO Council meeting, which is scheduled for later that week. Call details will be circulated by the GNSO Secretariat shortly. Best wishes, Heather Forrest GNSO Chair

2 1

For your review: GNSO May 2018 Project List
by Nathalie Peregrine 21 May '18

21 May '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

1 0

Fwd: [So-ac-sg-cleaders] ICANN Reviews
by Heather Forrest 21 May '18

21 May '18

Dear Council colleagues, Further information below on the published options to adjust the timelines of ICANN Reviews. For us to consider whether Council would benefit from a Q&A session, or whether this would best happen through SG/Cs. Here we might bear in mind that the Council's Standing Selection Committee was set up to manage the selection of GNSO candidates to specific reviews, and whether that gives rise to particular questions we want to ask. Best wishes, happy weekend to all, Heather Forrest ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: Thu, May 17, 2018 at 11:09 AM Subject: [So-ac-sg-cleaders] ICANN Reviews To: "so-ac-sg-cleaders(a)icann.org" <so-ac-sg-cleaders(a)icann.org> Cc: Sherwood Moore <sherwood.moore(a)icann.org>, Theresa Swinehart < theresa.swinehart(a)icann.org> Dear Community Leaders As many of you may know, yesterday we published public comments for short-term and long-term options to potentially adjust the timeline of ICANN Reviews. This is in response to issues raised by the community about the number of concurrent reviews and the strain that this has placed on volunteer and ICANN org resources. We’re hoping to share some additional opportunities for engagement and discussion on this important topic. I was wondering if you could help us to promote these resources with your respective communities? - Theresa Swinehart has shared a high-level introduction on the Public Comments on Review Timelines in her blog post published today. The post includes background information, key resources, and requests for the community to share their input via two public comments: https://www.icann.org/news/blog/please-comment-on-the-timing-of-reviews <https://www.icann.org/news/blog/please-comment-on-the-timing-of-reviews> - Two webinars will also be offered to help the ICANN Community understand the proposals and provide additional opportunity for Q&A. To participate, please request a calendar invitation by sending your email request to mssi-secretariat(a)icann.org and indicate which webinar you will join. - Webinar 1: 07 June 2018: 5:00-6:00 UTC[local time <https://www.timeanddate.com/worldclock/fixedtime.html?msg=Please+Comment+on…> ] - Webinar 2: 07 June 2018:17:00-18:00 UTC [local time <https://www.timeanddate.com/worldclock/fixedtime.html?msg=Please+Comment+on…> ] - Last, if community members are interested, we are encouraging them to invite us to present options and hold a Q&A with their constituencies via a remote call. Interested parties can schedule this by emailing: reviews(a)icann.org. As always, thank you for your support. Sherwood Moore Senior Project Manager, Strategic Communication & Community Engagement 424.443.8216 | sherwood.moore(a)icann.org Skype: sherwood.moore.icann Sent from my iPhone David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) _______________________________________________ So-ac-sg-cleaders mailing list So-ac-sg-cleaders(a)icann.org https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders

4 3

Your input requested: MSSI trends and cocktails to replace GNSO Council dinner at ICANN62?
by Heather Forrest 18 May '18

18 May '18

*Dear Council colleagues,As we work towards finalising the ICANN62 GNSO schedule, Council leadership has been thinking creatively with ICANN staff to find an opportunity for the GNSO Council to undertake the “trends exercise” conducted by Theresa Swinehart’s team (MSSI). This exercise is intended to be an input to ICANN’s next strategic plan. Donna and I had an opportunity to participate in a similar exercise during the SO/AC Chairs’ workshop held prior to the start of ICANN61 and found it to be an interesting exercise. We think it is useful to capture the particular perspective of the GNSO Council as manager of the GNSO PDP in this trends exercise as a complement to the inputs of the various SGs and Cs and consistent with our discussions at the Strategic Planning Session back in January. ICANN62 offers the best timing for us to do this before Theresa’s team finalises its data gathering and contributes this to ICANN Org for strategic plan development.At the same time, we are mindful of the limited time available to us during a policy forum meeting and we have taken the general approach so far in drafting the ICANN62 schedule of prioritising PDP time over Council meetings. We therefore seek your input on the idea of conducting the “trends exercise” as the Council over cocktails on the Wednesday evening from 18:30-19:30. This would replace the traditional Council dinner, free up the remainder of an evening for any other plans and experiment a new format, but would still offer us an opportunity to get together informally over drinks and canapes, enjoy each other’s company, while contributing our unique perspective to the “trends” that have been identified by other parts of the community to date. Please contribute your thoughts on this idea of getting together on Wednesday evening (ie, the evening after the GNSO Council meeting) over cocktails, in lieu of the traditional Council dinner.Best wishes,Heather ForrestDonna AustinRafik Dammak*

12 12

Fwd: [So-ac-sg-cleaders] Data Protection/Privacy – Meetings & Work Sessions - ICANN
by Heather Forrest 18 May '18

18 May '18

Dear Council colleagues, Please find below links to recordings on the webinar held earlier this week on the Temporary Specification. Best wishes, Heather ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: Wed, May 16, 2018 at 5:14 AM Subject: [So-ac-sg-cleaders] Data Protection/Privacy – Meetings & Work Sessions - ICANN To: "so-ac-sg-cleaders(a)icann.org" <so-ac-sg-cleaders(a)icann.org> Dear Community Leaders: https://www.icann.org/resources/pages/data-protection-meetings-2017-12-08-en Materials from today’s webinar on the Proposed Temporary Specification for gTLD Registration Data have been published in the Meetings & Work Sessions section <https://www.icann.org/resources/pages/data-protection-meetings-2017-12-08-en> of our Data Protection/Privacy page <https://www.icann.org/dataprotectionprivacy>. This includes the recording and supporting reference documents. Regards. David Sent from my iPhone David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) _______________________________________________ So-ac-sg-cleaders mailing list So-ac-sg-cleaders(a)icann.org https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders

1 0

Fwd: [So-ac-sg-cleaders] ICANN Board approves Temporary Specification
by Heather Forrest 18 May '18

18 May '18

Dear Council colleagues, For completeness of the GNSO Council list record, I forward the links to the Board announcement, resolution and Temporary Specification here. Best wishes, Heather ---------- Forwarded message ---------- From: Mary Wong <mary.wong(a)icann.org> Date: Fri, May 18, 2018 at 9:48 AM Subject: [So-ac-sg-cleaders] ICANN Board approves Temporary Specification To: "so-ac-sg-cleaders(a)icann.org" <so-ac-sg-cleaders(a)icann.org> Dear community leaders, Please be informed that, earlier today, the ICANN Board approved the Temporary Specification for gTLD registration data, in accordance with the procedure outlined in the Registrar Accreditation Agreement and the Registry Agreement. The Board action today initiates the community-led policy development process to consider the development and adoption of a consensus policy based on the issues outlined within the Temporary Specification, and as part of its resolution the Board, at the GAC’s request, also deferred formal action on certain pieces of advice the GAC had provided in its San Juan Communiqué. You can find the announcement, with links to the Board resolution and the Temporary Specification as approved, here: https://www.icann.org/news/ announcement-2018-05-17-en. We will greatly appreciate it if you can disseminate the above-noted information to your respective community groups. With best regards Mary Wong (sending this message on behalf of David Olive, SVP for Policy Development Support) _______________________________________________ So-ac-sg-cleaders mailing list So-ac-sg-cleaders(a)icann.org https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders

1 0

Fwd: [So-ac-sg-cleaders] Chair's Blog: Approving the Temporary Specification for gTLD Registration Data and Next Steps - ICANN
by Heather Forrest 18 May '18

18 May '18

Dear Council colleagues, Forwarding the link to the blog on the approval of the temporary specification. Best wishes, Heather ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: Fri, May 18, 2018 at 1:28 PM Subject: [So-ac-sg-cleaders] Chair's Blog: Approving the Temporary Specification for gTLD Registration Data and Next Steps - ICANN To: "so-ac-sg-cleaders(a)icann.org" <so-ac-sg-cleaders(a)icann.org> https://www.icann.org/news/blog/chair-s-blog-approving- the-temporary-specification-for-gtld-registration-data-and-next-steps Chair's Blog: Approving the Temporary Specification for gTLD Registration Data and Next Steps Chair's Blog: Approving the Temporary Specification for gTLDRegistration Data and Next Steps <https://www.icann.org/news/blog/chair-s-blog-approving-the-temporary-specif…> <https://www.icann.org/news/blog/chair-s-blog-approving-the-temporary-specif…> <https://www.icann.org/news/blog/chair-s-blog-approving-the-temporary-specif…> <https://www.icann.org/news/blog/chair-s-blog-approving-the-temporary-specif…> <https://www.icann.org/news/blog/chair-s-blog-approving-the-temporary-specif…> <https://www.icann.org/news/blog/chair-s-blog-approving-the-temporary-specif…> [image: Approving gtld registration data specs 750x425 17may18 en] The ICANN Board's approval today of <https://www.icann.org/news/announcement-2018-05-17-en> the proposed "Temporary Specification for gTLDRegistration Data <https://www.icann.org/resources/pages/gtld-registration-data-specs-en>" is an important step towards bringing ICANN and its contracted parties into compliance with the European Union's General Data Protection Regulation (GDPR). The Board took this action so that ICANN and its contracted parties may remain in compliance with both existing contractual requirements and community-developed policies as they relate to WHOIS. The adoption of this Temporary Specification is a major and historic milestone as we work toward identifying a permanent solution. The ICANN org and community have been closely working together to develop this interim model ahead of the GDPR's 25 May 2018 enforcement deadline, and the Board believes that this is the right path to take. WHOIS is an important system, and preserving it allows it to continue to act as a key tool in the ongoing fight against cybercrime, malicious actors, intellectual property infringement, and more. This Temporary Specification, which is based on the Proposed Interim Compliance Model <https://www.icann.org/en/system/files/files/gdpr-compliance-interim-model-0…> [PDF, 922 KB], aims to prevent fragmentation of WHOIS and ensure that WHOIS continues to be available, to the greatest extent possible. ICANN's role in providing the technical coordination of the globally distributed WHOISsystem is a unique matter, including the public interest nature of WHOIS. In my previous post <https://www.icann.org/news/blog/chair-s-blog-a-wrap-up-of-the-vancouver-boa…>, I provided the background into how the Board reorganized its Vancouver Workshop to dedicate a significant amount of time, and effort to review and discuss the proposed Temporary Specification, This extra time was also an important opportunity for us to have ICANNorg answer our questions and discuss the potential risks that could accompany either no action or adoption of a proposed Temporary Specification. Above all, ICANN's mission, as laid out in the bylaws <https://www.icann.org/resources/pages/governance/bylaws-en>, is to preserve the Internet's system of unique identifiers. We believe that this Temporary Specification strikes the right balance between upholding that mission and bringing the org and its contracted parties into compliance with this law. As with the requirements of a temporary policy, if still needed, the Board will reconvene in 90 days to reaffirm its adoption. Until that time, I encourage you to submit your thoughts to gdpr(a)icann.org. And I invite you to visit the dedicated Data Protection/Privacy <https://www.icann.org/dataprotectionprivacy> page to follow the latest updates. Finally, I want to thank the community, ICANNorg and the Board for their hard work over the past year in getting us to this place. While I recognize there are important elements remaining to be finalized, the adoption of this Temporary Specification today is a first step, and it sets us on the right path to maintaining WHOIS in the public interest, while complying with GDPR. Sent from my iPhone David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) _______________________________________________ So-ac-sg-cleaders mailing list So-ac-sg-cleaders(a)icann.org https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders

1 0

Canceled: Pre-ICANN62 GNSO Policy Webinar
by ICANN Policy Calendar 17 May '18

17 May '18

Meeting: Pre-ICANN62 GNSO Policy Webinar Date/Time: Monday, 18 June 2018 at 21:00 UTC for 90 minutes Please note: Joining information will be sent closer to the date.

1 0