Hi Joke, Thanks for it. I have no comments. Please make sure “Council” is always written with “C”. Best, Giovanni [cid:image002.jpg@01D51A25.966521E0]<http://www.eurid.eu/>Giovanni Seppia / External Relations Manager EURid vzw Telecomlaan 9, 1831 Diegem, Belgium T: +32 2 401 27 50 | M: +39 335 8141733 www.eurid.eu<http://www.eurid.eu/> RPR Brussel – VAT BE 0864.240.405 [cid:image003.jpg@01D4F6BF.C28BB830]<https://twitter.com/EUregistry> [cid:image004.jpg@01D4F6BF.C28BB830] <https://www.linkedin.com/company/eurid/> [cid:image005.jpg@01D4F6BF.C28BB830] <https://www.facebook.com/EUregistry> From: Ccnso-council [mailto:ccnso-council-bounces@icann.org] On Behalf Of Joke Braeken Sent: Monday, 3 June 2019 15:46 To: Bart Boswinkel <bart.boswinkel@icann.org>; ccnso-council@icann.org Subject: [ccnso-council] for your final review : draft council statement regarding evolving ICANN’s Multistakeholder Model Dear all, I am following up on the email below. Please find here the proposed draft council statement (clean version) regarding evolving ICANN’s Multistakeholder Model: https://docs.google.com/document/d/1nbKFm1f_eK23tz7E_ym7C-t_2n0XrQWDEx049Fb-poc/edit?usp=sharing<https://docs.google.com/document/d/1nbKFm1f_eK23tz7E_ym7C-t_2n0XrQWDEx049Fb-poc/edit?usp=sharing%20%5bdocs.google.com%5d> A word copy can be found in attachment. Kindly provide me with your input by the end of today, Monday, 3 June 2019, 23:59 UTC, in case you do not agree with the proposed council statement. Close date for public comments is tomorrow, 4 Jun 2019 23:59 UTC. Read more: https://www.icann.org/news/announcement-2019-04-25-en<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2019-2D04-2D25-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=HyTT2ymvadmiQcmo6B088sWOukGjEbibHJ64u5rMiME&m=QjdzMi9WWIgWOGs1R1zn-N7L0fKo0qUCPPpC1xrZVqw&s=9pcb5sNktHFNXUaJPlczAEYv68bReeCcnUgJ9pC_0fI&e=> Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken@icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org From: Ccnso-council <ccnso-council-bounces@icann.org<mailto:ccnso-council-bounces@icann.org>> on behalf of Joke Braeken <joke.braeken@icann.org<mailto:joke.braeken@icann.org>> Date: Thursday, 30 May 2019 at 11:10 To: Bart Boswinkel <bart.boswinkel@icann.org<mailto:bart.boswinkel@icann.org>>, ccnso-council <ccnso-council@icann.org<mailto:ccnso-council@icann.org>> Subject: Re: [ccnso-council] invitation to draft a council statement : your action is required by Friday, 31 May 2019 (noon UTC) Dear councillors, This is reminder regarding the email below. Your action is required by Friday, 31 May 2019 (noon UTC). Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken@icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ccNSO&d=DwM...> Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_ccnso_...> http://ccnso.icann.org [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__ccnso.icann.org&d=DwMGaQ...> From: Ccnso-council <ccnso-council-bounces@icann.org<mailto:ccnso-council-bounces@icann.org>> on behalf of Bart Boswinkel <bart.boswinkel@icann.org<mailto:bart.boswinkel@icann.org>> Date: Friday, 24 May 2019 at 11:43 To: ccnso-council <ccnso-council@icann.org<mailto:ccnso-council@icann.org>> Subject: [ccnso-council] invitation to draft a council statement : your action is required by Friday, 31 May 2019 (noon UTC) Dear Council members, On behalf of Joke: I am following up on Triage recommendation 25-2019 (Evolving ICANN’s Multistakeholder Model), which was recently approved by the ccNSO Council. Your action is required by Friday, 31 May 2019 (noon UTC). The recommendation specified that a Council statement is needed, as defined in https://ccnso.icann.org/sites/default/files/filefield_47783/guidelines-state... [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_d...> Close date for public comments is 4 Jun 2019 23:59 UTC Short summary: Building on the conversation at ICANN64, a public comment invites the community to further define issues that challenge the effectiveness of ICANN's multistakeholder model. Read more here: https://www.icann.org/news/announcement-2019-04-25-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_anno...> = = = = = |||| Your action is required ||| Kindly review the instructions included below, and provide input to the google document with the draft council statement.https://docs.google.com/document/d/1nbKFm1f_eK23tz7E_ym7C-t_2n0XrQWDEx049Fb-... [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_documen...> Deadline for this: Friday, 31 May 2019 (noon UTC), allowing for sufficient time to produce a final version of the Council statement. = = = = = Instructions Commenters should refer to the draft "Issues List" that reflects input received from the ICANN community about how to improve the effectiveness of ICANN's multistakeholder model. We welcome all comments, and encourage you to focus on the following: 1. For each issue, or your issues of interest, provide a specific example about how the issue hampers the effectiveness of ICANN's multistakeholder model. Be sure to provide a specific and clear articulation of the issue so that it is clearly and fully defined. Please provide fact-based examples only. If offering a "new" issue to be considered, provide a clear articulation of the issue along with fact-based examples and a rationale about how the issue is hampering the effectiveness of ICANN's multistakeholder model. If you believe that an issue or issues do not belong on the Issues List, provide a rationale as to why the issue or issues should be removed. 1. Commenters are also invited to offer prioritization of the issues on the Issues List. When offering prioritization, carefully consider the following: * Issues that, if they are constructively addressed and solutions can be found, would have the greatest impact in making ICANN's multistakeholder model more effective and efficient. * Whether there are interdependencies between any of the issues that you are prioritizing. That is to say, for issue "A" to be addressed a solution for issue "B" must be addressed as well to achieve improvements in the effective functioning of ICANN's multistakeholder model. * Which issues could favorably impact the effectiveness of ICANN's multistakeholder model at a potentially lower cost? * Which issues could favorable impact the effectiveness of ICANN's multistakeholder model without introduction of unnecessary layers of process or bureaucracy? * Which issues could be combined or consolidated because their nature is so similar? When considering consolidating issues, carefully consider whether there are any interdependencies that argue against consolidation. Disclaimer: This email and any attachment hereto is intended solely for the person to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient or if you have received this email in error, please delete it and immediately contact the sender by telephone or email, and destroy any copies of this information. You should not use or copy it, nor disclose its content to any other person or rely upon this information. Please note that any views presented in the email and any attachment hereto are solely those of the author and do not necessarily represent those of EURid. Any processing of personal data via email is done in accordance with our Privacy Policy. While all care has been taken to avoid any known viruses, the recipient is advised to check this email and any attachment for presence of viruses. http://www.eurid.eu/en/legal-disclaimer https://eurid.eu/en/other-infomation/privacy-policy

Dear Joke, I placed two comments with red-lines on the attached file. 1st : more emphasis on the excessive use of acronyms 2nd : editorial Hiro On Mon, 3 Jun 2019 13:45:52 +0000 Joke Braeken <joke.braeken@icann.org> wrote:

Dear all,

I am following up on the email below.

Please find here the proposed draft council statement (clean version) regarding evolving ICANN’s Multistakeholder Model: https://docs.google.com/document/d/1nbKFm1f_eK23tz7E_ym7C-t_2n0XrQWDEx049Fb-poc/edit?usp=sharing<https://docs.google.com/document/d/1nbKFm1f_eK23tz7E_ym7C-t_2n0XrQWDEx049Fb-poc/edit?usp=sharing%20%5bdocs.google.com%5d> A word copy can be found in attachment. Kindly provide me with your input by the end of today, Monday, 3 June 2019, 23:59 UTC, in case you do not agree with the proposed council statement.

Close date for public comments is tomorrow, 4 Jun 2019 23:59 UTC. Read more: https://www.icann.org/news/announcement-2019-04-25-en<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2019-2D04-2D25-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=HyTT2ymvadmiQcmo6B088sWOukGjEbibHJ64u5rMiME&m=QjdzMi9WWIgWOGs1R1zn-N7L0fKo0qUCPPpC1xrZVqw&s=9pcb5sNktHFNXUaJPlczAEYv68bReeCcnUgJ9pC_0fI&e=>

Best regards,

Joke Braeken ccNSO Policy Advisor joke.braeken@icann.org<mailto:joke.braeken@icann.org>

Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

From: Ccnso-council <ccnso-council-bounces@icann.org> on behalf of Joke Braeken <joke.braeken@icann.org> Date: Thursday, 30 May 2019 at 11:10 To: Bart Boswinkel <bart.boswinkel@icann.org>, ccnso-council <ccnso-council@icann.org> Subject: Re: [ccnso-council] invitation to draft a council statement : your action is required by Friday, 31 May 2019 (noon UTC)

Dear councillors,

This is reminder regarding the email below. Your action is required by Friday, 31 May 2019 (noon UTC).

Best regards,

Joke Braeken ccNSO Policy Advisor joke.braeken@icann.org<mailto:joke.braeken@icann.org>

Follow @ccNSO on Twitter: https://twitter.com/ccNSO [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ccNSO&d=DwM...> Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_ccnso_...> http://ccnso.icann.org [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__ccnso.icann.org&d=DwMGaQ...>

From: Ccnso-council <ccnso-council-bounces@icann.org> on behalf of Bart Boswinkel <bart.boswinkel@icann.org> Date: Friday, 24 May 2019 at 11:43 To: ccnso-council <ccnso-council@icann.org> Subject: [ccnso-council] invitation to draft a council statement : your action is required by Friday, 31 May 2019 (noon UTC)

Dear Council members,

On behalf of Joke: I am following up on Triage recommendation 25-2019 (Evolving ICANN’s Multistakeholder Model), which was recently approved by the ccNSO Council. Your action is required by Friday, 31 May 2019 (noon UTC). The recommendation specified that a Council statement is needed, as defined in https://ccnso.icann.org/sites/default/files/filefield_47783/guidelines-state... [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_d...> Close date for public comments is 4 Jun 2019 23:59 UTC

Short summary:

Building on the conversation at ICANN64, a public comment invites the community to further define issues that challenge the effectiveness of ICANN's multistakeholder model. Read more here: https://www.icann.org/news/announcement-2019-04-25-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_anno...>

= = = = =

|||| Your action is required |||

Kindly review the instructions included below, and provide input to the google document with the draft council statement.https://docs.google.com/document/d/1nbKFm1f_eK23tz7E_ym7C-t_2n0XrQWDEx049Fb-... [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_documen...> Deadline for this: Friday, 31 May 2019 (noon UTC), allowing for sufficient time to produce a final version of the Council statement.

= = = = =

Instructions

Commenters should refer to the draft "Issues List" that reflects input received from the ICANN community about how to improve the effectiveness of ICANN's multistakeholder model. We welcome all comments, and encourage you to focus on the following:

1. For each issue, or your issues of interest, provide a specific example about how the issue hampers the effectiveness of ICANN's multistakeholder model. Be sure to provide a specific and clear articulation of the issue so that it is clearly and fully defined. Please provide fact-based examples only. If offering a "new" issue to be considered, provide a clear articulation of the issue along with fact-based examples and a rationale about how the issue is hampering the effectiveness of ICANN's multistakeholder model. If you believe that an issue or issues do not belong on the Issues List, provide a rationale as to why the issue or issues should be removed.

1. Commenters are also invited to offer prioritization of the issues on the Issues List. When offering prioritization, carefully consider the following:

* Issues that, if they are constructively addressed and solutions can be found, would have the greatest impact in making ICANN's multistakeholder model more effective and efficient. * Whether there are interdependencies between any of the issues that you are prioritizing. That is to say, for issue "A" to be addressed a solution for issue "B" must be addressed as well to achieve improvements in the effective functioning of ICANN's multistakeholder model. * Which issues could favorably impact the effectiveness of ICANN's multistakeholder model at a potentially lower cost? * Which issues could favorable impact the effectiveness of ICANN's multistakeholder model without introduction of unnecessary layers of process or bureaucracy? * Which issues could be combined or consolidated because their nature is so similar? When considering consolidating issues, carefully consider whether there are any interdependencies that argue against consolidation.

I heard that the closing dates for comments was extended to 13 June – in case we do want to add further comments. The statement is fine from my perspective as far as it goes, and it’s hard anyway to disagree with the general thrust of the issues list. I am finding this whole process quite time-consuming and complex in itself! The irony … 😊 From: Ccnso-council <ccnso-council-bounces@icann.org> On Behalf Of Joke Braeken Sent: 03 June 2019 14:46 To: Bart Boswinkel <bart.boswinkel@icann.org>; ccnso-council@icann.org Subject: [ccnso-council] for your final review : draft council statement regarding evolving ICANN’s Multistakeholder Model Dear all, I am following up on the email below. Please find here the proposed draft council statement (clean version) regarding evolving ICANN’s Multistakeholder Model: https://docs.google.com/document/d/1nbKFm1f_eK23tz7E_ym7C-t_2n0XrQWDEx049Fb-poc/edit?usp=sharing<https://docs.google.com/document/d/1nbKFm1f_eK23tz7E_ym7C-t_2n0XrQWDEx049Fb-poc/edit?usp=sharing%20%5bdocs.google.com%5d> A word copy can be found in attachment. Kindly provide me with your input by the end of today, Monday, 3 June 2019, 23:59 UTC, in case you do not agree with the proposed council statement. Close date for public comments is tomorrow, 4 Jun 2019 23:59 UTC. Read more: https://www.icann.org/news/announcement-2019-04-25-en<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2019-2D04-2D25-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=HyTT2ymvadmiQcmo6B088sWOukGjEbibHJ64u5rMiME&m=QjdzMi9WWIgWOGs1R1zn-N7L0fKo0qUCPPpC1xrZVqw&s=9pcb5sNktHFNXUaJPlczAEYv68bReeCcnUgJ9pC_0fI&e=> Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken@icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org From: Ccnso-council <ccnso-council-bounces@icann.org<mailto:ccnso-council-bounces@icann.org>> on behalf of Joke Braeken <joke.braeken@icann.org<mailto:joke.braeken@icann.org>> Date: Thursday, 30 May 2019 at 11:10 To: Bart Boswinkel <bart.boswinkel@icann.org<mailto:bart.boswinkel@icann.org>>, ccnso-council <ccnso-council@icann.org<mailto:ccnso-council@icann.org>> Subject: Re: [ccnso-council] invitation to draft a council statement : your action is required by Friday, 31 May 2019 (noon UTC) Dear councillors, This is reminder regarding the email below. Your action is required by Friday, 31 May 2019 (noon UTC). Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken@icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ccNSO&d=DwM...> Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_ccnso_...> http://ccnso.icann.org [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__ccnso.icann.org&d=DwMGaQ...> From: Ccnso-council <ccnso-council-bounces@icann.org<mailto:ccnso-council-bounces@icann.org>> on behalf of Bart Boswinkel <bart.boswinkel@icann.org<mailto:bart.boswinkel@icann.org>> Date: Friday, 24 May 2019 at 11:43 To: ccnso-council <ccnso-council@icann.org<mailto:ccnso-council@icann.org>> Subject: [ccnso-council] invitation to draft a council statement : your action is required by Friday, 31 May 2019 (noon UTC) Dear Council members, On behalf of Joke: I am following up on Triage recommendation 25-2019 (Evolving ICANN’s Multistakeholder Model), which was recently approved by the ccNSO Council. Your action is required by Friday, 31 May 2019 (noon UTC). The recommendation specified that a Council statement is needed, as defined in https://ccnso.icann.org/sites/default/files/filefield_47783/guidelines-state... [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_d...> Close date for public comments is 4 Jun 2019 23:59 UTC Short summary: Building on the conversation at ICANN64, a public comment invites the community to further define issues that challenge the effectiveness of ICANN's multistakeholder model. Read more here: https://www.icann.org/news/announcement-2019-04-25-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_anno...> = = = = = |||| Your action is required ||| Kindly review the instructions included below, and provide input to the google document with the draft council statement.https://docs.google.com/document/d/1nbKFm1f_eK23tz7E_ym7C-t_2n0XrQWDEx049Fb-... [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_documen...> Deadline for this: Friday, 31 May 2019 (noon UTC), allowing for sufficient time to produce a final version of the Council statement. = = = = = Instructions Commenters should refer to the draft "Issues List" that reflects input received from the ICANN community about how to improve the effectiveness of ICANN's multistakeholder model. We welcome all comments, and encourage you to focus on the following: 1. For each issue, or your issues of interest, provide a specific example about how the issue hampers the effectiveness of ICANN's multistakeholder model. Be sure to provide a specific and clear articulation of the issue so that it is clearly and fully defined. Please provide fact-based examples only. If offering a "new" issue to be considered, provide a clear articulation of the issue along with fact-based examples and a rationale about how the issue is hampering the effectiveness of ICANN's multistakeholder model. If you believe that an issue or issues do not belong on the Issues List, provide a rationale as to why the issue or issues should be removed. 1. Commenters are also invited to offer prioritization of the issues on the Issues List. When offering prioritization, carefully consider the following: * Issues that, if they are constructively addressed and solutions can be found, would have the greatest impact in making ICANN's multistakeholder model more effective and efficient. * Whether there are interdependencies between any of the issues that you are prioritizing. That is to say, for issue "A" to be addressed a solution for issue "B" must be addressed as well to achieve improvements in the effective functioning of ICANN's multistakeholder model. * Which issues could favorably impact the effectiveness of ICANN's multistakeholder model at a potentially lower cost? * Which issues could favorable impact the effectiveness of ICANN's multistakeholder model without introduction of unnecessary layers of process or bureaucracy? * Which issues could be combined or consolidated because their nature is so similar? When considering consolidating issues, carefully consider whether there are any interdependencies that argue against consolidation.