<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Please find the link to the Summary Report of Public Comment Proceeding regarding <br class="">
<span style="font-family: Arial; font-size: 14pt; font-weight: 700;" class="">Evolving ICANN’s Multistakeholder Model</span><span style="font-family: Arial; font-size: 18pt; font-weight: 700;" class=""> </span><div class=""><a href="https://www.icann.org/en/system/files/files/report-comments-evolving-multistakeholder-model-20jun19-en.pdf" class="">https://www.icann.org/en/system/files/files/report-comments-evolving-multistakeholder-model-20jun19-en.pdf</a></div><div class="">Just published</div><div class="">SeB<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Le 14 juin 2019 à 00:37, Marita Moll <<a href="mailto:mmoll@ca.inter.net" class="">mmoll@ca.inter.net</a>> a écrit :</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="content-type" content="text/html; charset=UTF-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""><p class=""><font face="Times New Roman, Times, serif" class="">Dear CPWG members. I
hope some of you were able to attend B. Cute's webinar on
Wednesday. As usual, he was quite clear about what he was
expecting from us next:</font></p><p class=""><font face="Times New Roman, Times, serif" class="">1. Map issues to
owners</font></p><p class=""><font face="Times New Roman, Times, serif" class="">2. Identify dates by
which owners will deliver a solution or approach to resolving
the issue</font></p><p class=""><font face="Times New Roman, Times, serif" class="">3. Identify resources
needed by owner(s) to deliver solutions</font></p><p class=""><font face="Times New Roman, Times, serif" class="">So, by the time of the
meeting in Marrakesh the issue identification part of the
exercise will have been completed. At the meeting in Marrakesh,
Brian will be looking for everyone's help in mapping issues to
owners. e.g. who (Board, SO/ACs, ICANN org, etc) needs to take
responsibility for resolving each of the issues which have been
identified. This is going to be tough. We all would like someone
else to solve the problems, but if we want our issues to be
addressed, we will have to step up to the plate and shoulder
some of the work. I pointed out, during the webinar, that all of
the volunteer communities were already so stretched that they
might hesitate to take responsibility for yet another major
project. He did say that he was aware of the problem and that
participants would get lots of support. <br class="">
</font></p><p class=""><font face="Times New Roman, Times, serif" class="">I really suggest that
there be some advance thought put into which issues at large
should take some ownership of. Do we want to have our fingers in
all the pies or just a few of them? Where should we concentrate
our efforts? It would seem to make sense to come into this
meeting with a united point of view <br class="">
</font></p><p class=""><font face="Times New Roman, Times, serif" class="">This work will go on
for the duration of the strategic plan, so it is certain to be a
long haul.</font></p><p class=""><font face="Times New Roman, Times, serif" class="">Marita</font><br class="">
</p>
</div>
_______________________________________________<br class="">CPWG mailing list<br class=""><a href="mailto:CPWG@icann.org" class="">CPWG@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/cpwg<br class=""><br class="">_______________________________________________<br class="">By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</div></blockquote></div><br class=""></div></body></html>