November 2018 - council - lists.icann.org

Fw: [Gnso-epdp-team] Report on Small team on roles & responsibilities in preparation for EPDP Team Meeting #25
by Ayden Férdeline 13 Nov '18

13 Nov '18

Hi all, I am forwarding the below message along for information purposes as there has been a suggestion raised that a matter may need to be brought back to the Council to consider revising the EPDP charter. It might be premature to be forwarding this along, and nothing may come of it, but I figure the Council should be aware that the idea has been floated. Kind regards, Ayden ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, 13 November 2018 12:09, Thomas Rickert <epdp(a)gdpr.ninja> wrote: > Hello Marika, all, > yesterday, the call of the small roles & responsibilities team had its call. > > We thank JJ and Erika from ICANN Org for attending the call. > > I will only be able to attend the first 90 mins of the call and I do not know whether it is possible to squeeze in a report and discussion of the outcome of our call while I am in attendance. Therefore, I would like to give a brief update in writing. > > The plan for the meeting was to discuss > > - what roles GDPR offers and if these are sufficiently described in the language I offered for the report > - discussion of Rationale for joint controller vs. other scenarios > - options and limitations of policy work / charter limitations > - strategy to implementation > > I hoped we could make sufficient progress during the call so that the small team could suggest a solid path forward to the EPDP plenary. > > JJ reported to us that ICANN Org has a 10 page memo in the making in which concerns and ICANN’s views on the roles are described. > He said that we should not jump to the conclusion that a joint controller scenario is given before the roles and responsibilities for the individual processing activities are determined. > In his view, it is like putting the cart before the horse if a joint controller scenario is adopted before all parties had a chance to assess the impact on their liabilities and that joint controllership might not adequately reflect the risks the respective parties might want to take. > > We then discussed that it is not really a question of what the parties want to choose to best suit their wishes, but a question of what the legal determination of the setup is. Several participants expressed their view that a joint controller scenario is likely present and therefore a joint controller agreement needs to be negotiated to reflect the roles and responsibilities and the required indemnifications etc. need to be put in place to associate the risks appropriately. > > There are two issues with this that the EPDP Team and - in particular - the leadership needs to decide. > > 1. The issue of legal assessment vs. policy work > > The question was brought up by Kurt and JJ in particular. They said - rightfully - that our group cannot really give legal advice. We have discussed the unfortunate situation that our policy group needs to do both compliance work as well as policy work in the EPDP plenary on multiple occasions before. We have a charter that requires us to speak to the responsibilities of the parties and this is just not possible without being transparent (in our report) about what concept we think is applicable. So I think the plenary needs to discuss and confirm that we will take position on this (which can be vetted during the public comment period). > > If the EPDP Team does not wish to take a position on this question, I think we need to go back to the GNSO Council to ask for a revision of the charter. > > 2. Timing > > We were not given any indication as to how quickly a memo would be shared with the EPDP Team. JJ said that their memo should inform and help our work but it should not stand in the way of our work. > > In my view (which was shared by several participants), the EPDP Team must know what ICANN org’s view on the matter is. The SGs and Cs need to be able to take into account the concerns and suggestions that ICANN Org might have to inform their own positioning. Also, I think we cannot detach our work from ICANN org’s position. It would be unfortunate - to say the least - if our group came up with a recommendation for the parties to negotiate a JCA just to find out that ICANN Org will refuse to implement that recommendation. Thus, clarity is required as soon as possible and a report should not be published before the memo has been shared, analyzed, discussed in the EPDP team and potential revisions to the initial report have been made. > > In closing, let me be honest with the entire team and express my frustration with the process. > We have asked both Board liaisons as well as ICANN staff multiple times to share any legal memos / opinions there are to inform our discussions. Also, we have asked whether there would be concerns by ICANN Org with respect to entering into a joint controller agreement or data processing agreements in several meetings. We were not given any indication whatsoever that there could be problems. It is unfortunate to only learn about ICANN’s memo and that there are concerns a few days before the planned publication of our report. > > Kind regards, > Thomas > >> Am 12.11.2018 um 16:25 schrieb Marika Konings <marika.konings(a)icann.org>: >> >> Dear All, >> >> Please find below the proposed agenda for the next EPDP Team meeting which is scheduled for Tuesday 13 November at 14.00 UTC. >> >> - In relation to agenda item #3, please find attached an updated version of the proposed language for inclusion in the Initial Report in which staff has aimed to capture some of the input that was received in response to the Initial Report through the google doc, as well as input received on the mailing list. >> >> - In relation to agenda item #4, please find attached a table which provides an overview of the changes proposed by EPDP Team members that staff didn’t feel comfortable applying because e.g. either the proposed change is not clear, the proposed change affects previously agreed preliminary agreements / text, or is a substantive change that requires further discussion / consideration by the full EPDP Team (see https://docs.google.com/document/d/1SoNTnvvadNQ8nX_-OxN4mtsd-gfLNxT54GXSXyG… for all comments received to date). In certain cases, staff has proposed a path forward, but would appreciate EPDP Team/commenter feedback before applying this change. Note that a number of comments were made in relation to preliminary recommendations and/or text that is still under consideration. It is the expectation that this input will be raised in the context of those discussions. >> >> FYI, staff expects to share an updated version of the Initial Report later today so you can see how other input has been addressed (non-substantial issues) as well as how other aspects are coming together as a result of the EPDP Team work over the last couple of meetings. >> >> Best regards, >> >> Caitlin, Berry and Marika >> >> ====================== >> >> [][EPDP Meeting #25 Agenda] >> Tuesday, 13 November 2018 >> >> - Roll Call & SOI Updates (5 minutes) >> >> - Welcome and Updates from EPDP Team Chair (5 minutes) >> >> - Initial Report finalization status, incl. items remaining to be addressed and schedule for the week ahead >> >> - Confirm status and next steps in relation to natural vs. legal and geographic status >> >> - Review of outstanding action items >> >> - Other updates, if applicable >> >> - Data Redaction (see attached) >> >> Objective of discussion: >> >> - Confirm language for inclusion in the Initial Report in relation to data redaction as well as email communication >> >> - Review latest version of language for inclusion in relation to data redaction >> >> - Consider charter questions: >> >> f2) Should standardized requirements on registrant contact mechanism be developed? >> f3) Under what circumstances should third parties be permitted to contact the registrant, and how should contact be facilitated in those circumstances? >> And related draft recommendation: >> In relation to facilitating email communication between third parties and the registrant, the EPDP Team recommends that [current requirements in the Temporary Specification that specify that a Registrar MUST provide an email address or a web form to facilitate email communication with the relevant contact, but MUST NOT identify the contact email address or the contact itself, remain in place. [[[Other to be decided]]]. >> >> - Confirm next steps, if any >> >> - Commence review & discussion of comments / input received on Initial Report >> >> Objective of discussion: >> (1) Review proposed changes / comments on the Initial Report that require EPDP Team consideration >> (2) Agree on if/how these proposed changes / comments are to be applied to the Initial Report >> >> - Commence review of proposed changes / comments on the Initial Report (see list attached) >> >> - Confirm approach for addressing these >> >> - Confirm next steps, if any >> >> - Wrap and confirm next meeting to be scheduled for Wednesday 14 November / Thursday 15 November at 14.00 UTC (dependent on progress made). >> >> - Confirm action items >> >> - Confirm questions for ICANN Org, if any >> >> Marika Konings >> Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) >> Email: marika.konings(a)icann.org >> >> Follow the GNSO via Twitter @ICANN_GNSO >> Find out more about the GNSO by taking our [interactive courses](https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.or… and visiting the [GNSO Newcomer pages](https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_s…. >> >> <Data Redaction - up 12 November 2018.docx><Initial Report changes for discussion - upd 12 November 2018.docx>_______________________________________________ >> Gnso-epdp-team mailing list >> Gnso-epdp-team(a)icann.org >> https://mm.icann.org/mailman/listinfo/gnso-epdp-team

5 6

Notification of Electronic vote: Motion regarding the Revised Nomination of GNSO Candidates for the Third Review of ICANN Accountability and Transparency (ATRT3)
by Nathalie Peregrine 13 Nov '18

13 Nov '18

Dear Councilors, The GNSO Council email ballot on the motion regarding the Revised Nomination of GNSO Candidates for the Third Review of ICANN Accountability and Transparency (ATRT3) will be launched shortly. The corresponding motion will be circulated to the Council mailing list in the next few days and will be posted here: https://community.icann.org/display/gnsocouncilmeetings/Motions+29+November… The vote opens at 23:59 UTC on Tuesday 20 November 2018 and closes at 23:59 UTC on Monday 26 November 2018. Please make sure that you receive your ballot, from tally(a)icann.org<mailto:tally@icann.org>, and if you do not please let me know immediately: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please remember that if you are off email, you can cast your vote by voice, but please provide me with a telephone number before 19 November 2018. Please be sure to mark only one response: * In favour, * Not in favour, * Abstain Please also note the following applicable procedures: * The Operating Procedures do not permit absentee voting for either motion. Under Section 4.5 of the GNSO Operating Procedures, an abstention counts as a vote “not in favour”. The ballot includes a text box for you to state your reason(s) if you wish, should you decide to abstain from voting on either motion. * The voting threshold required for the motion to pass successfully is a simple majority of the Council. * In accordance with the rules for a vote outside a Council meeting, this ballot will be an open vote (i.e. not secret) and we will record and publish the outcomes as required by the GNSO Operating Procedures. Please let me know if you have any questions. Thank you. 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

Draft IANA/PTI FY20 Budget
by Berry Cobb 12 Nov '18

12 Nov '18

Dear Xavier, On behalf of the GNSO Council, please find attached comments regarding the draft FY20 IANA/PTI budget as constructed by the SCBO and accepted by the GNSO Council without objection. Thank you. B Berry Cobb GNSO Policy Consultant @berrycobb

1 0

Proposed GNSO Council comment on the draft FY20 IANA/PTI Budget
by Ayden Férdeline 12 Nov '18

12 Nov '18

Dear all, On behalf of the Council's Standing Committee on Budget and Operations, please find attached a comment that we have prepared on the draft FY20 IANA/PTI budget. We are seeking to submit this comment on behalf of the Council on 12 November 2018, absent any objections from a member of the Council. With apologies for not getting this into your inbox sooner, can you please review the attached document as a matter of urgency. Thank you very much. Kind regards, Ayden Férdeline

7 10

FY20 Supporting Organization & Advisory Committee (SO/AC) ABR Kickoff
by Nathalie Peregrine 12 Nov '18

12 Nov '18

Dear ICANN Community Member, ICANN’s Planning Team would like to notify you that the FY20 Supporting Organization and Advisory Committee (SO/AC) Additional Budget Request process has begun. This additional budget approval process is part of the overall ICANN annual budgeting process that is for the review of specific requests from the community that are not already included in the budget but serve to further the key objectives of the requesting community group. Your active participation and adherence to procedural guidelines is greatly appreciated. Information concerning the FY20 SO/AC additional request process, timeline, and additional budget request template can be found on the Finance Community Wiki<https://community.icann.org/pages/viewpage.action?pageId=96213580>. Please email any questions that you may have to planning(a)icann.org<mailto:planning@icann.org>. We look forward to your continued engagement on the SO/AC Additional Budget Request Process for FY20. Angela Hillman ICANN| Sr. Financial Analyst III 12025 Waterfront Drive, Suite 300 |Los Angeles |California | 90094-2536 |US 310.578.8917 voice | 310.823.8649 fax | Angela.Hillman(a)icann.org<mailto:Angela.Hillman@icann.org> www.icann.org [icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFAg…> Angela Hillman ICANN| Sr. Financial Analyst III 12025 Waterfront Drive, Suite 300 |Los Angeles |California | 90094-2536 |US 310.578.8917 voice | 310.823.8649 fax | Angela.Hillman(a)icann.org<mailto:Angela.Hillman@icann.org> www.icann.org [icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFAg…> <image002.jpg> _______________________________________________ community-finance mailing list community-finance(a)icann.org<mailto:community-finance@icann.org> https://mm.icann.org/mailman/listinfo/community-finance _______________________________________________ Team-Leaders mailing list Team-Leaders(a)icann.org<mailto:Team-Leaders@icann.org> https://mm.icann.org/mailman/listinfo/team-leaders

1 0

Reminder: Document and Motion deadline Monday 19 November 2018 at 23:59 UTC for the GNSO Council Meeting 29 October 2018 at 12:00 UTC
by Nathalie Peregrine 12 Nov '18

12 Nov '18

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday 19 November 2018 at 23:59 UTC) of the GNSO Council Meeting on Thursday 29 November 2018 at 12:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Motions+29+November… Thank you very much. With kind regards, Nathalie

1 1

Proposed GNSO Council meeting times and dates 2019
by Nathalie Peregrine 09 Nov '18

09 Nov '18

Dear all, Please find below list of proposed GNSO Council meeting dates with times added for 2019. Having received no objection to the 2019 dates proposed during ICANN63 and having taken into account the new time-zone set-up due to outgoing and incoming councilors, a rotation of two meeting times (instead of three in 2018) seems to be the ideal solution: 12:00 UTC and 21:00 UTC. This rotation will of course apply to meetings held remotely exclusively and will not be valid for the four face-to-face meetings (Strategic Planning Session and 3 ICANN Public meetings) planned for 2019. * January 24th (Pacific time, during the GNSO Strategic Planning session) * February 21st: 12:00 UTC * March 13th (ICANN64 Kobe) * April 18th: 21:00 UTC * May 16th: 12:00 UTC * June 26th (ICANN65 Marrakech) * July 18th: 21:00 UTC * August 22nd: 12:00 UTC * September 19th: 21:00 UTC * October 24th: 12:00 UTC * November 6th (ICANN66 Montreal) * December 19th: 21:00 UTC Please let me know if you have any questions or concerns regarding this schedule and the times proposed. Thank you! 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 1

Re: [council] [Ext] RE: Invitation - RSVP - ICANN Leadership Program (LP) 2019 - deadline Wednesday 7 November
by Marika Konings 09 Nov '18

09 Nov '18

On behalf of Council leadership: The GNSO Council leadership reviewed the candidates for the ICANN Leadership Academy and based on the current roles and responsibilities of these candidates in relation to Council activities has agreed to recommend Ayden Ferdeline as the Council candidate. However, both Marie and Arsene (in that order) will be submitted as alternate candidates so that if additional slots become available, they will hopefully be able to participate as well. The GNSO Secretariat will communicate this decision to the ICANN Leadership Academy while all three candidates need to fill out the following registration form: here [goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_forms_HAInCnPEw…> as soon as possible. Best regards, Marika From: "Drazek, Keith" <kdrazek(a)verisign.com> Date: Tuesday, November 6, 2018 at 6:30 AM To: Marika Konings <marika.konings(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [Ext] RE: Invitation - RSVP - ICANN Leadership Program (LP) 2019 - deadline Wednesday 7 November Thanks Marika. Apologies to all for the short notice and deadline on this. There’s no obligation to fill this spot, but if anyone is interested, speak up now. Best, Keith From: council <council-bounces(a)gnso.icann.org> On Behalf Of Marika Konings Sent: Tuesday, November 06, 2018 4:16 PM To: council(a)gnso.icann.org Subject: [EXTERNAL] [council] FW: Invitation - RSVP - ICANN Leadership Program (LP) 2019 - deadline Wednesday 7 November Dear All, Please see below the invitation for candidates to participate in the ICANN Leadership Program which is scheduled to take place 7-8 March 2019, two days prior to the official start of ICANN64 in Kobe, Japan. One seat is reserved for the GNSO Council (SG/Cs have been invited to put forward candidates separately). If you are interested, please state your interest on the Council mailing list by Wednesday 7 November at the latest (apologies for the short deadline). Should there be more than one candidate, the Council leadership team will decide how to proceed. Thanks, Marika From: Public Responsibility Support <prs(a)icann.org<mailto:prs@icann.org>> Date: Tuesday, October 2, 2018 at 4:27 PM To: Heather Forrest <haforrestesq(a)gmail.com<mailto:haforrestesq@gmail.com>> Cc: Ergys Ramaj <ergys.ramaj(a)icann.org<mailto:ergys.ramaj@icann.org>>, "info(a)hoferichter.eu<mailto:info@hoferichter.eu>" <info(a)hoferichter.eu<mailto:info@hoferichter.eu>>, Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>> Subject: Invitation - RSVP - ICANN Leadership Program (LP) 2019 Dear Heather, The ICANN Academy Leadership Program (LP) during the ICANN61 Meeting in Puerto Rico<https://community.icann.org/display/LTP/2018+Leadership+Program> was another success and we are now preparing the 6th edition that is scheduled to take place 7-8 March 2019, two days prior to the official start of ICANN64 in Kobe, Japan. For this program, one (1) seat is reserved for a representative from the GNSO Council. The program is designed for current and incoming leaders, helping to increase understanding of the complexity of ICANN and to develop facilitation skills, as well as building a network with other leaders. We are aware that understanding ICANN as an organization, the topics discussed within ICANN, and interaction within other stakeholder groups can be challenging for incoming leaders, but sometimes also for experienced leaders. ICANN and the community are making considerable efforts in order to help incoming leaders have a good start to their terms and to provide current leaders the opportunity to strengthen their leadership and facilitation skills. Opportunities for Leadership Program participants include the following: * Meet leaders from the other SOs/ACs and get an insight of the functionality and issues in other groups * Discuss current ICANN topics in an in-depth manner * Deepen the understanding of key ICANN processes * Develop facilitation and leadership skills, focused personal effectiveness to run meetings and foster processes A preliminary program is attached to this email. Kindly note that this is subject to change. Accommodation for participants will be covered between Wednesday and Thursday, 6-7 March 2019, and participants will receive a stipend. Please note that flights will NOT be covered under this program, as incoming and current leaders are normally covered by the regular ICANN travel support. Please ensure that the leaders you select are being covered by ICANN Travel Support for their flights to Kobe for ICANN64. We would like to ask you to identify one incoming or current leader from your stakeholder group who is interested and available to participate in this program. We recommend that you also identify an alternate candidate. Kindly forward us the names and email addresses of the endorsed individuals no later than Thursday, 8 November 2018, and ask them to register here [goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_forms_HAInCnPEw…> by 23:59 UTC on 8 November as well. We hope this program will meet the needs of your community. All participants will be encouraged to partake in an open exchange of their views, as this will help facilitate cross-constituency collaboration during their terms. We are very happy to answer any questions you may have on this exciting LP and look forward to having your group’s participants confirmed. Kind regards, Sandra Hoferichter, Chair of the ICANN Academy Working Group Ergys Ramaj, VP, Public Responsibility Support

4 3

2017-2018 GNSO Chair Report to Council - Thank You!!
by Drazek, Keith 07 Nov '18

07 Nov '18

Dear Heather, On behalf of the GNSO and the GNSO Council, I would like to formally acknowledge your excellent 2017/2018 Annual Report of the Chair and thank you for your very thoughtful and constructive observations and recommendations. As the incoming Chair, I welcome each and every point you highlighted in the report, and you have my assurance the new leadership team will take them on board and benefit greatly from your advice. I would also like to take this opportunity to acknowledge the significant contributions of Donna Austin and Rafik Dammak to the 2017/2018 leadership team. I agree fully with your assessment and recommendation that the next GNSO Council Chair should rely on a team approach and I'm confident that Rafik, Pam and I will work very effectively and collaboratively together in this regard. You, Donna and Rafik have set a high bar, and I'm glad that Rafik will be able to provide important continuity for the 2018/2019 leadership team. I also support your observation concerning the "tyranny of distance," and not only for Chairs. I recognize the challenge and believe that, as a Council and within PDP Working Groups, we must ensure equal opportunity and distribution of pain in managing time-zone scheduling challenges. As you noted in your report, this is important not only for existing participants, but also to ensure an equitable opportunity for potential future contributors. Further, as the incoming Council Chair, I am fully committed to continuing your excellent leadership on the PDP 3.0 effort. This will be a significant focus of the Council's 2018/2019 Strategic Planning Session in January and throughout the year. The GNSO and ICANN will be well-served by your vision and the work we accomplished in 2018, and I assure you it will continue with the energy and spirit you instilled from the outset. Finally, on behalf of the entire Council, past and present, I would like to extend our gratitude for your service, respect for your incredible commitment to excellence, and well-wishes in your future endeavors. Don't be a stranger...you are already missed! Best regards, Keith

1 0

FW: Invitation - RSVP - ICANN Leadership Program (LP) 2019 - deadline Wednesday 7 November
by Marika Konings 06 Nov '18

06 Nov '18

Dear All, Please see below the invitation for candidates to participate in the ICANN Leadership Program which is scheduled to take place 7-8 March 2019, two days prior to the official start of ICANN64 in Kobe, Japan. One seat is reserved for the GNSO Council (SG/Cs have been invited to put forward candidates separately). If you are interested, please state your interest on the Council mailing list by Wednesday 7 November at the latest (apologies for the short deadline). Should there be more than one candidate, the Council leadership team will decide how to proceed. Thanks, Marika From: Public Responsibility Support <prs(a)icann.org> Date: Tuesday, October 2, 2018 at 4:27 PM To: Heather Forrest <haforrestesq(a)gmail.com> Cc: Ergys Ramaj <ergys.ramaj(a)icann.org>, "info(a)hoferichter.eu" <info(a)hoferichter.eu>, Marika Konings <marika.konings(a)icann.org> Subject: Invitation - RSVP - ICANN Leadership Program (LP) 2019 Dear Heather, The ICANN Academy Leadership Program (LP) during the ICANN61 Meeting in Puerto Rico<https://community.icann.org/display/LTP/2018+Leadership+Program> was another success and we are now preparing the 6th edition that is scheduled to take place 7-8 March 2019, two days prior to the official start of ICANN64 in Kobe, Japan. For this program, one (1) seat is reserved for a representative from the GNSO Council. The program is designed for current and incoming leaders, helping to increase understanding of the complexity of ICANN and to develop facilitation skills, as well as building a network with other leaders. We are aware that understanding ICANN as an organization, the topics discussed within ICANN, and interaction within other stakeholder groups can be challenging for incoming leaders, but sometimes also for experienced leaders. ICANN and the community are making considerable efforts in order to help incoming leaders have a good start to their terms and to provide current leaders the opportunity to strengthen their leadership and facilitation skills. Opportunities for Leadership Program participants include the following: * Meet leaders from the other SOs/ACs and get an insight of the functionality and issues in other groups * Discuss current ICANN topics in an in-depth manner * Deepen the understanding of key ICANN processes * Develop facilitation and leadership skills, focused personal effectiveness to run meetings and foster processes A preliminary program is attached to this email. Kindly note that this is subject to change. Accommodation for participants will be covered between Wednesday and Thursday, 6-7 March 2019, and participants will receive a stipend. Please note that flights will NOT be covered under this program, as incoming and current leaders are normally covered by the regular ICANN travel support. Please ensure that the leaders you select are being covered by ICANN Travel Support for their flights to Kobe for ICANN64. We would like to ask you to identify one incoming or current leader from your stakeholder group who is interested and available to participate in this program. We recommend that you also identify an alternate candidate. Kindly forward us the names and email addresses of the endorsed individuals no later than Thursday, 8 November 2018, and ask them to register here<https://goo.gl/forms/HAInCnPEwsYRxKFs2> by 23:59 UTC on 8 November as well. We hope this program will meet the needs of your community. All participants will be encouraged to partake in an open exchange of their views, as this will help facilitate cross-constituency collaboration during their terms. We are very happy to answer any questions you may have on this exciting LP and look forward to having your group’s participants confirmed. Kind regards, Sandra Hoferichter, Chair of the ICANN Academy Working Group Ergys Ramaj, VP, Public Responsibility Support

10 9