<div dir="ltr"><br>Dear EC,<div>We have to nominate a representative here. Atleast to the NCSG , how do we go about this? </div><div><br></div><div>Kind regards,</div><div>Benjamin</div><div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <span dir="auto"><<a href="mailto:philippe.fouquart@orange.com">philippe.fouquart@orange.com</a>></span><br>Date: Mon, Jan 31, 2022 at 5:55 PM<br>Subject: FW: Moving ahead with the WS2 Community Coordination Group | Response Requested by Friday, 11 February 2022<br>To: <a href="mailto:mason.cole@appdetex.com">mason.cole@appdetex.com</a> <<a href="mailto:mason.cole@appdetex.com">mason.cole@appdetex.com</a>>, <a href="mailto:wolf-ulrich.knoben@t-online.de">wolf-ulrich.knoben@t-online.de</a> <<a href="mailto:wolf-ulrich.knoben@t-online.de">wolf-ulrich.knoben@t-online.de</a>>, <a href="mailto:lschulman@inta.org">lschulman@inta.org</a> <<a href="mailto:lschulman@inta.org">lschulman@inta.org</a>>, <a href="mailto:bruna.mrtns@gmail.com">bruna.mrtns@gmail.com</a> <<a href="mailto:bruna.mrtns@gmail.com">bruna.mrtns@gmail.com</a>>, <a href="mailto:plommer@gmail.com">plommer@gmail.com</a> <<a href="mailto:plommer@gmail.com">plommer@gmail.com</a>>, <a href="mailto:benakin@gmail.com">benakin@gmail.com</a> <<a href="mailto:benakin@gmail.com">benakin@gmail.com</a>>, <a href="mailto:aheineman@godaddy.com">aheineman@godaddy.com</a> <<a href="mailto:aheineman@godaddy.com">aheineman@godaddy.com</a>>, <a href="mailto:sdemetriou@verisign.com">sdemetriou@verisign.com</a> <<a href="mailto:sdemetriou@verisign.com">sdemetriou@verisign.com</a>>, <a href="mailto:chair@rysg.info">chair@rysg.info</a> <<a href="mailto:chair@rysg.info">chair@rysg.info</a>>, <a href="mailto:secretariat@rysg.info">secretariat@rysg.info</a> <<a href="mailto:secretariat@rysg.info">secretariat@rysg.info</a>>, <a href="mailto:secretariat@icannregistrars.org">secretariat@icannregistrars.org</a> <<a href="mailto:secretariat@icannregistrars.org">secretariat@icannregistrars.org</a>>, <a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a> <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>><br>Cc: <a href="mailto:gnso-secs@icann.org">gnso-secs@icann.org</a> <<a href="mailto:gnso-secs@icann.org">gnso-secs@icann.org</a>><br></div><br><br>
<div lang="FR" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="m_-1068527788781280567WordSection1">
<p class="MsoNormal"><span lang="EN-US">Dear Councilors, Dear SG/C leaders,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">With some delay – and my apologies for this - please note the following and therefore to the SG/C a reminder to appoint/confirm a representative for this group if you haven’t already.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">On Council’s side, in addition to looking for a rep (volunteer welcome) and to avoid duplication of the work, we may want to think about how we may articulate our potential inputs to
this, and future work under the </span><span lang="EN-US">GNSO Council Committee for Overseeing and Implementing Continuous Improvement, which in principle was intended to cover such non PDP related work. The discussion that we will have soon on the completion
of the pilot’s first task for this CCOICI would be a good opportunity to discuss this too.
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Philippe</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="m_-1068527788781280567msipfootered91ed98" align="center" style="margin:0cm;text-align:center">
<span style="font-size:8.0pt;font-family:"Helvetica 75 Bold",sans-serif;color:#ed7d31">Orange Restricted</span><u></u><u></u></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">De :</span></b><span lang="EN-US"> soac-chairs <<a href="mailto:soac-chairs-bounces@icann.org" target="_blank">soac-chairs-bounces@icann.org</a>>
<b>De la part de</b> Chantelle Doerksen via soac-chairs<br>
<b>Envoyé :</b> mardi 25 janvier 2022 18:54<br>
<b>À :</b> <a href="mailto:soac-chairs@icann.org" target="_blank">soac-chairs@icann.org</a><br>
<b>Cc :</b> Mary Wong <<a href="mailto:mary.wong@icann.org" target="_blank">mary.wong@icann.org</a>>; Mariana Marinho <<a href="mailto:mariana.marinho@icann.org" target="_blank">mariana.marinho@icann.org</a>>; Alperen Eken <<a href="mailto:alperen.eken@icann.org" target="_blank">alperen.eken@icann.org</a>>; Alice Jansen <<a href="mailto:alice.jansen@icann.org" target="_blank">alice.jansen@icann.org</a>>; Giovanni Seppia <<a href="mailto:giovanni.seppia@icann.org" target="_blank">giovanni.seppia@icann.org</a>><br>
<b>Objet :</b> [soac-chairs] Moving ahead with the WS2 Community Coordination Group | Response Requested by Friday, 11 February 2022<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt">Dear SOAC Chairs,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt">We are reaching out to you about proceeding to form the community group that will serve as an information sharing and coordinating forum for the community’s implementation of certain specific
recommendations from the Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) Work Stream 2 (WS2). As suggested in the most recent summary of the scope of work for the WS2 Community Coordination Group, we would like to request
that each Supporting Organization, Advisory Committee, Regional At-Large Organization, and GNSO Stakeholder Group confirm their appointment of a representative (and alternate, if appropriate).
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:12.0pt">Background</span></b><span lang="EN-US" style="font-size:12.0pt"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt">In relation to a timeline, ICANN org had suggested that each SO/AC/RALO/SG complete its appointment of its primary and secondary representatives by late January or early February 2022, with the
aim of having the WS2 Community Coordination Group hold an initial call before ICANN73.The initial call will allow the group to familiarize itself with its scope of work, discuss a potential timeline and a cadence for its calls. Subsequent calls would then
involve discussion as to the order in which the community would approach implementing the relevant recommendations. These recommendations are Recommendation 1.1 (on proposed elements of diversity), Recommendation 1.7 (on a process for handling complaints about
diversity), and Recommendation 2.3 (on a standalone framework for exercising Empowered Community powers). We understand that there may be other recommendations that can benefit from information sharing purposes as well, but wanted to flag these specific recommendations
to you as those that require cross-community coordination. <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt">For quick reference, we have attached the most recent version of the WS2 Community Coordination Group Proposal for your easy reference. <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:12.0pt">Next steps</span></b><span lang="EN-US" style="font-size:12.0pt"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt">Given the time that has elapsed since the proposal for a WS2 Community Coordination Group was first raised with you as SOAC Chairs, we would like to ask that each SO, AC, RALO, and GNSO Stakeholder
Group confirm their representative, and if appropriate, alternate, to the Group by no later than
<b>Friday, 11 February 2022. </b>Please share the name(s) with everyone on this list, and also with your respective support staff for coordination purposes. <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt">Going forward, we envision that the work of this group will be transparent and available to the public. This means that call materials (recordings, action items, etc.), reports, and any decisions
will be made available via a wiki space being created for record keeping purposes.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt">Please let us know if you have any questions or concerns. We look forward to hearing from you.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt">Best,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt">Mary and Chantelle
<u></u><u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt">_______________________________<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt">Chantelle Doerksen<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt">Policy Development Support Specialist<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt">Internet Corporation for Assigned Names and Numbers (ICANN)<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><u></u> <u></u></span></p>
</div>
<pre>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</pre></div>
</div></div></div>