<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>My comments below. Apologies for the delay. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Ken<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> NCUC-EC <ncuc-ec-bounces@lists.ncuc.org> <b>On Behalf Of </b>Benjamin Akinmoyeje<br><b>Sent:</b> Thursday, September 30, 2021 11:06 PM<br><b>To:</b> Raphael Beauregard-Lacroix <rbeauregardlacroix@gmail.com><br><b>Cc:</b> Exec. Comm <ncuc-ec@lists.ncuc.org><br><b>Subject:</b> Re: [NCUC-EC] [TIME SENSITIVE] Fwd: WS2 Mapping Inventory and Next Steps for the NCUC<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Dear Raphael,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Kindly find my responses below.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>On Wed, Sep 29, 2021 at 11:15 AM Raphael Beauregard-Lacroix <<a href="mailto:rbeauregardlacroix@gmail.com">rbeauregardlacroix@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><p class=MsoNormal>Dear all,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Please have a look at what's below and give me your thoughts/opinions/suggestions<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>We'd need to provide our reply by Sunday 3rd 2359 (got an extension) so I would kindly ask you to have a look at this and provide your suggestions/ideas in this thread by <b><u>Friday 1 Oct 2359</u></b> <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>thank you,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>***<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><span lang=EN-CA style='font-size:10.0pt;font-family:Symbol'>·</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><b><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>6.1.3: SO/AC/Groups should document their procedures for non-members to challenge decisions regarding their eligibility to become a member.</span></b><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in'><span lang=EN-CA style='font-size:10.0pt;font-family:"Courier New"'>o</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>Could be implemented in coordination with NCSG. NCSG handles membership requests at the SG level and SG membership is required for C membership. Existing procedures concern only existing members (Operating Procedures, IX). Would require an Operating Procedures amendment.</span><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p></div></div></blockquote><div><p class=MsoNormal><span style='color:blue'>I agree to a certain extent to this recommendation however the operating procedure should include consultation with the EC.</span><o:p></o:p></p><p class=MsoNormal>KH: I agree with both Olga and Ben.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><span lang=EN-CA style='font-size:10.0pt;font-family:Symbol'>·</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><b><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>6.1.4: SO/AC/Groups should document unwritten procedures and customs that have been developed in the course of practice, and make them part of their procedural operation documents, charters, and/or bylaws</span></b><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in'><span lang=EN-CA style='font-size:10.0pt;font-family:"Courier New"'>o</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>Could be implemented</span><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p></div></div></blockquote><div><p class=MsoNormal><span style='color:blue'>I believe we should review and implement. I agree </span><o:p></o:p></p><p class=MsoNormal>KH: Agree that this makes sense to implement.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><span lang=EN-CA style='font-size:10.0pt;font-family:Symbol'>·</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><b><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>6.1.5: Each year, SO/AC/Groups should publish a brief report on what they have done during the prior year to improve accountability, transparency, and participation, describe where they might have fallen short, and any plans for future improvements</span></b><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in'><span lang=EN-CA style='font-size:10.0pt;font-family:"Courier New"'>o</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>Could be implemented. Formalizing such reporting as part of the task of the executive committee would require a Bylaws amendment.</span><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p></div></div></blockquote><div><p class=MsoNormal><span style='color:blue'>This is tricky, and may be subjective, it will depend on the Key deliverables on Accountability, transparency and participation, this will help decide if we met the target or fell short. We just have to set up a system of evaluation, then we can report appropriately. </span><o:p></o:p></p><p class=MsoNormal>KH: I agree in general that it would be useful, but it’s not as if we need more to do. Imagine, a “brief” report on all these topics? I don’t think so. I agree with Olga that formalizing this level of reporting is a bit unsustainable.<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in'><span style='font-size:12.0pt;font-family:"Arial",sans-serif'> </span><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p></div></div></blockquote><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><span lang=EN-CA style='font-size:10.0pt;font-family:Symbol'>·</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><b><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>6.2.4: Meetings and calls of SO/AC/Groups should normally be open to public observation. When a meeting is determined to be members-only, that should be explained publicly, giving specific reasons for holding a closed meeting…</span></b><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in'><span lang=EN-CA style='font-size:10.0pt;font-family:"Courier New"'>o</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>Uncertain as to what kind of action is contemplated (“public explanation and reasons”)</span><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p></div></div></blockquote><div><p class=MsoNormal><span style='color:blue'>Meetings during ICANN events are always open, except if this is required for EC monthly calls, there is need for clarification here. The NCUC meetings should be open to the public I believe.</span><o:p></o:p></p><p class=MsoNormal>KH: IMO, this only applies if and when the EC decides to conduct a “closed” meeting, and I cannot imagine this happening. Are there times when it does? If so, I am not sure I agree that it needs to be justified publicly. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><span lang=EN-CA style='font-size:10.0pt;font-family:Symbol'>·</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><b><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>6.4.2: Each SO/AC/Group should maintain a publicly accessible website/wiki page to advertise their outreach events and opportunities.</span></b><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in'><span lang=EN-CA style='font-size:10.0pt;font-family:"Courier New"'>o</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>Outreach is handled on a case-by-case basis and given the characteristics of our membership and executive committee we do not believe it is warranted for us to create a standing outreach committee. Outreach activities are already generally governed by Operating Procedures, VI.</span><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p></div></div></blockquote><div><p class=MsoNormal><span style='color:blue'>If this will help increase the effectiveness of our outreach activities. Advertising our outreach opportunities and activities is a welcome idea, so that members know what is currently happening and who is engaged in it. I support the recommendation. </span><o:p></o:p></p><p class=MsoNormal>KH: I agree with Olga that I do not see this as requiring any additional mechanism but rather communication and documentation of outreach activities. This I believe the EC already does, so I support the response as it is drafted. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><span lang=EN-CA style='font-size:10.0pt;font-family:Symbol'>·</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><b><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>6.5.1: Each SO/AC/Group should review its policies and procedures at regular intervals and make changes to operational procedures and charter as indicated by the review.</span></b><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in'><span lang=EN-CA style='font-size:10.0pt;font-family:"Courier New"'>o</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>Implemented (Bylaws, IV.G.2)</span><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><span lang=EN-CA style='font-size:10.0pt;font-family:Symbol'>·</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><b><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>6.5.2: Members of SO/AC/Groups should be involved in reviews of policies and procedures and should approve any revisions.</span></b><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in'><span lang=EN-CA style='font-size:10.0pt;font-family:"Courier New"'>o</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>Implemented (Operating Procedures, XV)</span><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><span lang=EN-CA style='font-size:10.0pt;font-family:Symbol'>·</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><b><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>6.5.3: Internal reviews of SO/AC/Group policies and procedures should not be prolonged for more than one year, and temporary measures should be considered if the review extends longer.</span></b><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in'><span lang=EN-CA style='font-size:10.0pt;font-family:"Courier New"'>o</span><span lang=EN-CA style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial",sans-serif'>Could be implemented, to the extent of the maximum period and temporary measures. Would require an Operating Procedures amendment. </span><span style='font-size:10.0pt;font-family:"Arial",sans-serif'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:blue'>I agree as well.</span><o:p></o:p></p><p class=MsoNormal>KH: I agree also.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></blockquote><div><p class=MsoNormal>Kind regards,<o:p></o:p></p></div><div><p class=MsoNormal>Benjamin<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Tue, Sep 28, 2021 at 4:34 PM Raphael Beauregard-Lacroix <<a href="mailto:rbeauregardlacroix@gmail.com" target="_blank">rbeauregardlacroix@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><p class=MsoNormal>Dear all,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Like many other things, this has flown under the radar for me this summer, but we need to decide whether and how we want to implement certain WS2 recommendations at the level of NCUC. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I would thus kindly ask you <b><u>to familiarize yourself with the attached PDF</u></b>, especially all those recs flagged in red, and make up your mind about what you think should be done in that regard. Do note that we do not need to implement by Thursday, but we need to decide whether we want to implement, and have an idea how. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I will be back to you <b><u>tomorrow morning eurotime</u></b> with more detailed suggestions as to what should be done for each rec, and I would then ask you to react to such suggestions, with your own, comments, approval (as the case may be,) etc. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thank you and have a nice day<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><div><p class=MsoNormal>---------- Forwarded message ---------<br>From: <strong><span style='font-family:"Calibri",sans-serif'>Chantelle Doerksen</span></strong> <<a href="mailto:chantelle.doerksen@icann.org" target="_blank">chantelle.doerksen@icann.org</a>><br>Date: Mon, Aug 16, 2021 at 7:38 PM<br>Subject: WS2 Mapping Inventory and Next Steps for the NCUC | Requested response by Thursday, 30 September<br>To: Raphaël Beauregard-Lacroix <<a href="mailto:rbeauregardlacroix@gmail.com" target="_blank">rbeauregardlacroix@gmail.com</a>>, Maryam Bakoshi <<a href="mailto:maryam.bakoshi@icann.org" target="_blank">maryam.bakoshi@icann.org</a>>, Brenda Brewer <<a href="mailto:brenda.brewer@icann.org" target="_blank">brenda.brewer@icann.org</a>><br>Cc: Jamal LeBlanc <<a href="mailto:jamal.leblanc@icann.org" target="_blank">jamal.leblanc@icann.org</a>>, Carlos Reyes <<a href="mailto:carlos.reyes@icann.org" target="_blank">carlos.reyes@icann.org</a>>, Mary Wong <<a href="mailto:mary.wong@icann.org" target="_blank">mary.wong@icann.org</a>><o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><div><p style='margin:0in'><span style='color:black'>Dear Raphael,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'> </span><o:p></o:p></p><p style='margin:0in;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'>As follow-up from our call with you and the other GNSO SG/C leaders on Thursday, 5 August (<a href="https://icann.zoom.us/rec/play/EC2J_MnLICCtKMZ3njiez8gmT8-vd8f5KKoD7hMTx685J0yTFOcnGkCZSXKn4qWUaYZ9fEeyFG8J7E37.qjzfrfKY8hlHzecV?startTime=1628168673000&_x_zm_rtaid=SELK-6DpQo-WAQybG5zoIw.1629124410352.da9182bfe280f00c43036bc28bd798ad&_x_zm_rhtaid=304" target="_blank"><span style='color:#1155CC'>call recording</span></a>), we are sharing the first part of an inventory of Work Stream 2 (WS2) recommendations that staff has mapped for the NCUC. Please note that the focus is on those WS2 recommendations directed at the community and which are intended for each individual SO/AC/Group to decide whether to implement: viz. <u>Recommendations 1.2 - 1.6</u> (on <a href="https://www.icann.org/en/system/files/files/ccwg-acct-ws2-annex-1-diversity-final-recs-27mar18-en.pdf" target="_blank"><span style='color:#1155CC'>Diversity</span></a>), and <u>Recommendations 6.1 - 6.5</u> (on <a href="https://www.icann.org/en/system/files/files/ccwg-acct-ws2-annex-6-soac-final-recs-27mar18-en.pdf" target="_blank"><span style='color:#1155CC'>SOAC Accountability</span></a>). </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'> </span><o:p></o:p></p><p style='margin:0in;font-variant-caps:normal;text-align:start;word-spacing:0px'><b><span style='color:black'>Scope of the initial mapping inventory:</span></b><o:p></o:p></p><p style='margin:0in;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'>The inventory is intended to be a preliminary gap analysis of the above-noted WS2 recommendations, mapped to your group’s current governance documents (e.g. your Charter or group bylaws) and, where applicable, operating procedures. The attached document covers Recommendations 6.1 - 6.5. Staff is currently conducting a similar mapping exercise for Recommendations 1.2 - 1.6 that we will circulate when complete.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'> </span><o:p></o:p></p><p style='margin:0in;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'>For the other WS2 recommendations that were directed at the community (i.e. <a href="https://www.icann.org/en/system/files/files/ccwg-acct-ws2-annex-1-diversity-final-recs-27mar18-en.pdf" target="_blank" title="https://www.icann.org/en/system/files/files/ccwg-acct-ws2-annex-1-diversity-final-recs-27mar18-en.pdf"><span style='color:#1155CC'>Recommendations 1.1 & 1.7</span></a>; <a href="https://www.icann.org/en/system/files/files/ccwg-acct-ws2-annex-2-good-faith-guidelines-final-recs-27mar18-en.pdf" target="_blank"><span style='color:#1155CC'>Recommendation 2.3</span></a>; and <a href="https://www.icann.org/en/system/files/files/ccwg-acct-ws2-annex-3-hr-foi-final-recs-27mar18-en.pdf" target="_blank"><span style='color:#1155CC'>Recommendation 3</span></a>), these were the subject of discussion at the SOAC Chairs Roundtable meeting in June as they are recommendations for which either community coordination and prioritization may be required or information sharing beneficial. In this regard, we hope that your group will be able to provide your opinion as to whether you support the suggestion to have an ad-hoc group of community representatives perform that coordination, prioritization and information-sharing work. As we mentioned on last Thursday’s call, ICANN org has asked that the SOAC Chairs revert with their respective community’s feedback by the next Roundtable meeting (currently expected to take place in September.)</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'> </span><o:p></o:p></p><p style='margin:0in;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'>We wish to emphasize that the Cross-Community Working Group on Accountability for WS2 made it clear that decisions as to implementation and prioritization of these recommendations are voluntary. We are also mindful of the community’s workload, especially at this time and in consideration of the many important policy topics that your group is working on. We therefore hope that the staff-prepared inventory is helpful to your group’s review of the relevant recommendations. </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'> </span><o:p></o:p></p><p style='margin:0in;font-variant-caps:normal;text-align:start;word-spacing:0px'><b><span style='color:black'>Mapping inventory</span></b><span style='color:black'>: <a href="https://docs.google.com/spreadsheets/d/1yQoIjRZnBIbaxwY6CVlPMjrMrZaweJFifmFxrIeyafI/edit#gid=0" target="_blank">https://docs.google.com/spreadsheets/d/1yQoIjRZnBIbaxwY6CVlPMjrMrZaweJFifmFxrIeyafI/edit#gid=0</a> (attached in PDF format for reference) </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'> </span><o:p></o:p></p><p style='margin:0in;font-variant-caps:normal;text-align:start;word-spacing:0px'><b><span style='color:black'>Next Steps</span></b><o:p></o:p></p><p style='margin:0in;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'>As a first step, we hope that completing a review of the inventory will allow your group to decide which (if any) of the relevant recommendations it wishes to implement. To the extent that the decision is to implement any specific recommendation, the next step can be to determine the relative priority, timeline and implementation method for each such recommendation. </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'> </span><o:p></o:p></p><p style='margin:0in;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'>We will be happy to support your group in this effort. If there is a specific point of contact or any particular members of your group that we should be working with, we will be grateful if you can let us know who they are. We would also like to suggest <b>Thursday, 30 September </b>as a possible due date to aim for completing the initial inventory review for Recommendation 6. <b><u>Please let us know if you would like us to schedule a call with you or your group’s representatives to discuss the inventory</u></b>. Thank you.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'> </span><o:p></o:p></p><p style='margin:0in;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'>Best regards,</span><o:p></o:p></p><p style='margin:0in;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'>Chantelle, Carlos, and Mary</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px'><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div></div></div></div></blockquote></div></div><p class=MsoNormal>_______________________________________________<br>NCUC-EC mailing list<br><a href="mailto:NCUC-EC@lists.ncuc.org" target="_blank">NCUC-EC@lists.ncuc.org</a><br><a href="https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec" target="_blank">https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec</a><o:p></o:p></p></blockquote></div></div></div></body></html>