June 2018 - council - lists.icann.org

For your review - EPDP Initiation Request and EPDP Team Charter Templates
by Marika Konings June 14, 2018

June 14, 2018

Dear All, As discussed during today’s extraordinary Council meeting, staff has gone ahead and prepared a template for the EPDP Initiation Request as well as the EPDP Team Charter (see attached). As there is some duplication between the Initiation Request and the Charter, staff would like to suggest that you focus your attention on the EPDP Team charter for now. Once elements such as scope and team composition have been agreed on, these can then be lifted from the charter into the EPDP Initiation Request. Also note that staff has taken the liberty to prepopulate some of the sections of the charter to facilitate your deliberations. These entries are either based on existing charter language / practices / procedures and/or aspects that have come up in the context of the discussions to date, including the PDP 3.0 conversations. In addition, staff has flagged some items highlighted in yellow that will require further feedback before draft language can be added. Of course, it is up to you to edit / delete / add as you deem appropriate. If there is anything further that staff can do to facilitate your deliberations and drafting, please let me know. 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-…>.

2 1

Suggestion for membership criteria of proposed Expedited Policy Development Process
by Ayden Férdeline June 13, 2018

June 13, 2018

Dear all, I have just finished reviewing the proposed agenda for our meeting next week along with the mindmap that Council leadership and staff have developed (thanks for doing this!). I would like to put forward a suggestion for the Expedited Policy Development Process (EPDP) team criteria. While the scope of the EPDP remains unclear at present, what I took away from the call between the Board and the Council on Tuesday was that compliance with the law is crucial. As such I think it is imperative that *all* members be able to demonstrate that they have a basic understanding of the principles and legal terms of data protection. I would like to request that any community member who is appointed to the EPDP, or staff member supporting the EPDP, be able to demonstrate they have completed at least 3 hours of data protection training. I do not think this would be a huge burden, but I think it would make work easier, as there should be a common understanding of essential terms. There are short half-day 'Data Protection 101' classes run by institutions like the policy neutral International Association of Privacy Professionals, whose courses only use definitions of terms that have been defined in law for over 20 years. For those who don't hold this certification, I would like to request that ICANN reimburse the members of the EPDP for their modest and reasonable costs in obtaining it. I would like to hear your thoughts here, however I would also like to ask that this suggestion please be given serious consideration. Thank you. Best wishes, Ayden Férdeline

11 24

Doodle poll: GNSO Council Preparation call Initiation Request and Charter Drafting
by Nathalie Peregrine June 12, 2018

June 12, 2018

Dear all, As a follow-up action item from the extraordinary GNSO Council meeting held earlier, please be so kind as to complete the below Doodle poll in order to schedule a GNSO Council preparation call regarding Initiation Request and Charter drafting. The doodle poll slots have been chosen in order to have timeslots taking councilors’ time-zones into account, so as with GNSO Council meeting times, a certain flexibility is required ☺ Doodle poll: https://doodle.com/poll/p8vdnd95fgpb3vkt 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

MP3, Adobe Connect recording and chat transcript/ Extraordinary GNSO Council meeting on Tuesday, 12 June 2018 at 12:00 UTC.
by Terri Agnew June 12, 2018

June 12, 2018

Dear GNSO Council, Please find below the MP3, Adobe Connect recording and chat of the Extraordinary GNSO Council meeting held on Tuesday, 12 June 2018 at 12:00 UTC. MP3: <https://audio.icann.org/gnso/gnso-council-12jun18-en.mp3> https://audio.icann.org/gnso/gnso-council-12jun18-en.mp3 Adobe Connect Recording URL: <https://participate.icann.org/p2gm9co4zpi/> https://participate.icann.org/p2gm9co4zpi/ Adobe Connect chat at: <https://gnso.icann.org/sites/default/files/file/field-file-attach/transcrip…> https://gnso.icann.org/sites/default/files/file/field-file-attach/transcrip… All on page: <https://gnso.icann.org/en/group-activities/calendar> https://gnso.icann.org/en/group-activities/calendar Thank you. Happy listening and reading! 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…> 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

GDPR Training for EPDP
by Martin Pablo Silva Valent June 12, 2018

June 12, 2018

Dear all, Here goes something I would like to bring up. I was listening to todays morning call on the essential and difficult need to spread quickly more training among our icann colleagues on how GDPR works (not awareness, but actual skills to debate policy). In any case, I think that just a a two hours webinar (or a one hour session in Panama), regardless of the amazing people we have on board, we could use an already strong program that is deep enough to give meaningful knowledge, but is not overwhelming to learn in the next weeks. I found this “Get GDPR Ready” https://iapp.org/train/gdprready <https://iapp.org/train/gdprready> Course of International Association of Privacy Professionals (IAPP <https://iapp.org/>). On the other hand, the course is qualified for “Certified Information Privacy Professional /Europe”, which gives both legitimacy and some sort of credit afterwards. The course is not cheap, at least not for ICANN community members to individually purchase, so I think it would be ideal if ICANN strikes some sort of deal to have this course open, not in ICANN times, but in EPDP times!!! I know Sam Pfeifle, IAPP Content Director, is the person who did the presentation of this matter at INTA 2018, and I heard good thing about it. If INTA could strike a deal, ICANN should too. I think this is the right track to bring a game changer element to the EPDP debate, a fast track training by trusted party already set-up to implement tomorrow. Disclosure, I have attended as guest some IAPP events at Argentina, usually at some big trademark law firm, but I have no direct nor indirect relationship, nor-whatsoever, with them. Cheers, Martín

1 0

GNSO Council Abstention Notification Form [#277]
by ICANN June 12, 2018

June 12, 2018

1 0

Fwd: Mapping the Temp Spec to Existing ICANN Agreements and Policies
by Heather Forrest June 12, 2018

June 12, 2018

Dear Council colleagues, An immediate follow-up to my previous email - below and attached is the response outstanding to #9 (mapping across other ICANN policies), which I understand may require further refinements. Sincere thanks to Cherine, Chris, David and their colleagues for providing this information as quickly as possible. Best wishes, Heather ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: Tue, Jun 12, 2018 at 2:01 PM Subject: Mapping the Temp Spec to Existing ICANN Agreements and Policies To: "haforrestesq(a)gmail.com" <haforrestesq(a)gmail.com>, " gnso-chairs(a)icann.org" <gnso-chairs(a)icann.org> Cc: Cherine Chalaby <cherine.chalaby(a)board.icann.org>, Chris Disspain < chris(a)disspain.uk>, Goran Marby <goran.marby(a)icann.org>, John Jeffrey < john.jeffrey(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, Erika Randall <erika.randall(a)icann.org> Dear Heather ; Attached is the document mapping the Temporary Specification to existing agreements and policies. I have marked this document as “working draft” because we may need some refinements as we move forward. Best regards, David

2 1

Fwd: Letter from the GNSO Chairs/Co-Chairs on the GNSO Council – ICANN Board meeting to discuss next steps following the Board’s adoption of the temporary specification
by Heather Forrest June 12, 2018

June 12, 2018

Dear Council colleagues, Picking up on Pam's query to the list last week, we followed up by letter on 8 June with the Board in relation to the outstanding questions from our call. Please find responses sent through by David Olive below. I understand that #9 is in progress and the intention is to provide it to Council before our Extraordinary meeting (taking place in a matter of hours, so we won't have time to review it in depth, but hopefully will have it to hand to discuss). "See" you all later today at the Extraordinary Meeting. Best wishes, Heather ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: Tue, Jun 12, 2018 at 6:35 AM Subject: Letter from the GNSO Chairs/Co-Chairs on the GNSO Council – ICANN Board meeting to discuss next steps following the Board’s adoption of the temporary specification To: Heather Forrest <haforrestesq(a)gmail.com>, Gnso-chairs < gnso-chairs-bounces(a)icann.org> Cc: Cherine Chalaby <cherine.chalaby(a)board.icann.org>, Chris Disspain < chris.disspain(a)board.icann.org>, Goran Marby <goran.marby(a)icann.org>, John Jeffrey <john.jeffrey(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, Erika Randall <erika.randall(a)icann.org>, Wendy Profit < wendy.profit(a)icann.org> Dear Heather, On behalf of Cherine who is currently traveling, I would like to thank you for your letter dated 8 June 2018. In the interest of time, Chris Disspain has asked I respond to the outstanding questions as identified in your letter so that it is received in time for the upcoming GNSO Council meeting which has been scheduled for 12 June 2018. Hereby the responses to the outstanding questions identified: SCOPE: *(5) The Temporary Specification reasoning for including WHOIS as a security and stability issue is based on the new ICANN Bylaws; at time of contract signing, that wasn’t the case. Doesn’t that open a possible avenue to challenge it altogether? Wouldn’t phasing the EPDP allowing a quick Consensus Policy made of uncontroversial parts of the Temp Spec increase the assurances that this wouldn’t hamper ICANN Org’s compliance ability? * The Board has not had time yet to discuss this question but once it does, it will provide its feedback to the GNSO Council. *(8) The Temporary Specification covers a number of additional policies that go beyond the requirements of the RA and RAA as they relate to Registration Data Directory Services. How does the Board believe the GNSO Council should handle these areas of overlap? * The GNSO Council may want to consider taking the same approach that it currently uses in policy development processes for considering existing consensus policies that may be impacted by a proposed new consensus policy. However, the Board and ICANN Org stand ready to work with the GNSO Council on these issues as needed and if/when they arise. *(9) Does ICANN have/will ICANN develop a list of policies and contractual clauses that are impacted by the temporary specification (beyond what is currently identified in the Annex)? This would help with scoping the work. * ICANN Org is preparing a document that will show which areas of the existing agreements and consensus policies are changed as a result of the GDPR. It is expected that this document will be shared with the GNSO Council prior to its meeting. *(11) How does the Board expect the EPDP to follow and/or to incorporate ICANN ́s ongoing legal strategy and the decisions of EU country courts? * Ongoing discussions and pending court cases could have an impact on issues such as these, but the PDP on the temporary specification is not expected to deliberate on these issues, unless these are reflected in modifications that are made by the ICANN Board to the temporary specification. *PARTICIPATION: * *(3) What is the Board's expectation with regard to the Council's ongoing communication with Board/involvement of Board during the scoping process? (In particular here the notes reflect our discussion on the need for instant two-way consultation between the Board and the GNSO Council. As follow-up questions, it would be helpful if the Board could consider its ability and willingness to appoint a liaison to the EPDP to facilitate this communication on ongoing basis, and further reflect on the role of the Board once the PDP is established and working.)* As suggested during the meeting, if welcomed by the GNSO Council, the Board would be more than happy to appoint one or two liaisons to the PDP Team to facilitate communication on an ongoing basis. I hope that this input will facilitate the upcoming extraordinary Council meeting. As noted above, I also expect to send you the list of policies and contractual clauses that are impacted by the temporary specification as soon as it is available. Best regards, David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

REMINDER FOR REVIEW: Proposed Next Steps re: GNSO Council's New Roles and Responsibilities Outlined in the Post-Transition Bylaws
by Julie Hedlund June 11, 2018

June 11, 2018

Dear All, Per the message below, this is a reminder to review the proposed next steps to be taken as outlined in the attached table to ensure preparedness as well as facilitate the ability for the GNSO Council to act in relation to the new roles and responsibilities outlined in the post-transition Bylaws. Staff is seeking feedback on whether the Council is supportive of these proposed next steps or whether modifications should be considered. Please note also that unless there are objections, staff could begin to work on the various templates that are identified in the attached table. Best regards, Julie Julie Hedlund, Policy Director From: council <council-bounces(a)gnso.icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Wednesday, May 16, 2018 at 10:34 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] FOR REVIEW: Proposed Next Steps re: GNSO Council's New Roles and Responsibilities Outlined in the Post-Transition Bylaws Dear All, Following the adoption by the GNSO Council of the revised GNSO Operating Procedures, as well as the proposed modifications to the ICANN Bylaws adopted by the ICANN Board of Directors on 13 May, staff has outlined in the attached table the additional proposed steps to be taken to ensure preparedness as well as facilitate the ability for the GNSO Council to act in relation to the new roles and responsibilities outlined in the post-transition Bylaws. The GNSO Council is requested to review the proposed next steps and to provide feedback whether it is supportive of these proposed next steps or whether modifications should be considered. Best regards, Julie Julie Hedlund, Policy Director

1 0

GNSO Council Abstention Notification Form [#276]
by ICANN June 11, 2018

June 11, 2018

1 0