<html><body><span style="display:block;" class="xfm_26837561"><div><span style="font-family:"Times New Roman";font-size:12pt;line-height:14pt;" class="xfmc1">Hi Raphael and All!</span></div>
<div><span style="font-size:12pt;line-height:14pt;font-family:"Times New Roman";" class="xfmc1"><br data-mce-bogus="1"/></span></div>
<div><span style="font-size:12pt;line-height:14pt;font-family:"Times New Roman";" class="xfmc1">Please, find my reactions and comments in red accross each recommendation in the body of your initial email.</span></div>
<div><span style="font-size:12pt;line-height:14pt;font-family:"Times New Roman";" class="xfmc1"><br data-mce-bogus="1"/></span></div>
<div><span style="font-size:12pt;line-height:14pt;font-family:"Times New Roman";" class="xfmc1">Best,</span></div>
<div><span style="font-size:12pt;line-height:14pt;font-family:"Times New Roman";" class="xfmc1">Olga</span></div>
<div></div>
<div><br/></div>
<div><br/></div>
<div><i><span style="font-size:10pt;line-height:12pt;"><span style="font-family:Arial;">29 сентября 2021, 12:15:50, от "Raphael Beauregard-Lacroix" <</span><a href="mailto:rbeauregardlacroix@gmail.com" target="_blank"><span style="font-family:Arial;">rbeauregardlacroix@gmail.com</span></a><span style="font-family:Arial;">>:</span></span></i></div>
<div><br/></div>
<blockquote style="border-left:1px solid #cccccc;margin:0px 0px 0px 0.8ex;padding-left:1ex;">
<div style="display:block;">
<div>Dear all,
<div><br/></div>
<div>Please have a look at what's below and give me your thoughts/opinions/suggestions</div>
<div><br/></div>
<div>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><span style="text-decoration:underline;">Friday 1 Oct 2359</span></b></div>
<div><br/></div>
<div>thank you,</div>
<div><br/></div>
<div>***</div>
<div><br/></div>
<div>
<div><span lang="EN-CA" style="font-size:10pt;font-family:Symbol;">·<span style="font-stretch:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman';">
</span></span><span style="font-size:10pt;font-family:Arial,sans-serif;"><b>6.1.3: SO/AC/Groups should
document their procedures for non-members to challenge decisions regarding
their eligibility to become a member.</b></span></div>
<div><span lang="EN-CA" style="font-size:10pt;font-family:'Courier New';">o<span style="font-stretch:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman';">
</span></span><span lang="EN-CA" style="font-size:10pt;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></div>
</div>
</div>
</div>
</blockquote>
<div><span style="font-size:10pt;font-family:Arial;line-height:12pt;color:rgb(255, 0, 0);" class="xfmc1">Agree it has to be decided at the NCSG level and some uniform procedure to be put in place.<br data-mce-bogus="1"/></span></div>
<div><span style="font-size:10pt;font-family:Arial;line-height:12pt;color:rgb(255, 0, 0);" class="xfmc1"><br data-mce-bogus="1"/></span></div>
<blockquote style="border-left:1px solid #cccccc;margin:0px 0px 0px 0.8ex;padding-left:1ex;">
<div style="display:block;">
<div>
<div>
<div><span lang="EN-CA" style="font-size:10pt;font-family:Arial, sans-serif;line-height:12pt;" class="xfmc1"> </span></div>
<div><span style="font-size:10pt;line-height:12pt;" class="xfmc1"><span lang="EN-CA" style="font-family:Symbol;">·<span style="font-stretch:normal;font-family:"Times New Roman";">
</span></span><span style="font-family:Arial, sans-serif;"><b>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</b></span></span></div>
<div><span style="font-size:10pt;line-height:12pt;" class="xfmc1"><span lang="EN-CA" style="font-family:"Courier New";">o<span style="font-stretch:normal;font-family:"Times New Roman";">
</span></span><span lang="EN-CA" style="font-family:Arial, sans-serif;">Could be implemented</span></span></div>
</div>
</div>
</div>
</blockquote>
<div><span style="font-size:10pt;font-family:Arial;line-height:12pt;color:rgb(255, 0, 0);" class="xfmc1">Why not? If we have some specific practice developed over time, it totally makes sense to integrate it in a more formal way. However, I can't recall anything in specific that isn't covered by our bylaws at this point.</span></div>
<div><span style="font-size:10pt;font-family:Arial;line-height:12pt;" class="xfmc1"><br data-mce-bogus="1"/></span></div>
<blockquote style="border-left:1px solid #cccccc;margin:0px 0px 0px 0.8ex;padding-left:1ex;">
<div style="display:block;">
<div>
<div>
<div><span style="font-size:10pt;line-height:12pt;" class="xfmc1"><span lang="EN-CA" style="font-family:Symbol;">·<span style="font-stretch:normal;font-family:"Times New Roman";">
</span></span><span style="font-family:Arial, sans-serif;"><b>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</b></span></span></div>
<div><span style="font-size:10pt;line-height:12pt;" class="xfmc1"><span lang="EN-CA" style="font-family:"Courier New";">o<span style="font-stretch:normal;font-family:"Times New Roman";">
</span></span><span lang="EN-CA" style="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></div>
</div>
</div>
</div>
</blockquote>
<div><span style="font-size:10pt;font-family:Arial;line-height:12pt;color:rgb(255, 0, 0);" class="xfmc1">Not sure formalising this would be helpful. In practice, this is done every year during the meet the candidate call before elections.</span></div>
<div><span style="font-size:10pt;font-family:Arial;line-height:12pt;" class="xfmc1"><br data-mce-bogus="1"/></span></div>
<blockquote style="border-left:1px solid #cccccc;margin:0px 0px 0px 0.8ex;padding-left:1ex;">
<div style="display:block;">
<div>
<div>
<div><span style="font-size:10pt;line-height:12pt;" class="xfmc1"><span lang="EN-CA" style="font-family:Symbol;">·<span style="font-stretch:normal;font-family:"Times New Roman";">
</span></span><span style="font-family:Arial, sans-serif;"><b>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…</b></span></span></div>
<div><span style="font-size:10pt;line-height:12pt;" class="xfmc1"><span lang="EN-CA" style="font-family:"Courier New";">o<span style="font-stretch:normal;font-family:"Times New Roman";">
</span></span><span lang="EN-CA" style="font-family:Arial, sans-serif;">Uncertain as to what kind of
action is contemplated (“public explanation and reasons”)</span></span></div>
</div>
</div>
</div>
</blockquote>
<div><span style="font-size:10pt;font-family:Arial;line-height:12pt;color:rgb(255, 0, 0);" class="xfmc1">Maybe it presumes explanation in the meeting announcement, wherever it is published - on website, mailing list, etc. It is fine to be implemented.</span></div>
<div><span style="font-size:10pt;font-family:Arial;line-height:12pt;" class="xfmc1"><br data-mce-bogus="1"/></span></div>
<blockquote style="border-left:1px solid #cccccc;margin:0px 0px 0px 0.8ex;padding-left:1ex;">
<div style="display:block;">
<div>
<div>
<div><span style="font-size:10pt;line-height:12pt;" class="xfmc1"><span lang="EN-CA" style="font-family:Symbol;">·<span style="font-stretch:normal;font-family:"Times New Roman";">
</span></span><span style="font-family:Arial, sans-serif;"><b>6.4.2: Each SO/AC/Group
should maintain a publicly accessible website/wiki page to advertise their
outreach events and opportunities.</b></span></span></div>
<div><span style="font-size:10pt;line-height:12pt;" class="xfmc1"><span lang="EN-CA" style="font-family:"Courier New";">o<span style="font-stretch:normal;font-family:"Times New Roman";">
</span></span><span lang="EN-CA" style="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></div>
</div>
</div>
</div>
</blockquote>
<div><span style="font-size:10pt;font-family:Arial;line-height:12pt;color:rgb(255, 0, 0);" class="xfmc1">I don't read it as presuming the creation of a separate committee, but rather as a call to publish info about outreach events on website and social media. It is already envisaged in our operating procedures. So I don't think it would require any extra steps from our side.</span></div>
<div><span style="font-size:10pt;font-family:Arial;line-height:12pt;" class="xfmc1"><br data-mce-bogus="1"/></span></div>
<blockquote style="border-left:1px solid #cccccc;margin:0px 0px 0px 0.8ex;padding-left:1ex;">
<div style="display:block;">
<div>
<div>
<div><span lang="EN-CA" style="font-size:10pt;font-family:Arial, sans-serif;line-height:12pt;" class="xfmc1"> </span></div>
<div><span style="font-size:10pt;line-height:12pt;" class="xfmc1"><span lang="EN-CA" style="font-family:Symbol;">·<span style="font-stretch:normal;font-family:"Times New Roman";">
</span></span><span style="font-family:Arial, sans-serif;"><b>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.</b></span></span></div>
<div><span style="font-size:10pt;line-height:12pt;" class="xfmc1"><span lang="EN-CA" style="font-family:"Courier New";">o<span style="font-stretch:normal;font-family:"Times New Roman";">
</span></span><span lang="EN-CA" style="font-family:Arial, sans-serif;">Implemented (Bylaws, IV.G.2)</span></span></div>
</div>
</div>
</div>
</blockquote>
<blockquote style="border-left:1px solid #cccccc;margin:0px 0px 0px 0.8ex;padding-left:1ex;">
<div style="display:block;">
<div>
<div>
<div><span style="font-size:10pt;line-height:12pt;" class="xfmc1"><span lang="EN-CA" style="font-family:Symbol;">·<span style="font-stretch:normal;font-family:"Times New Roman";">
</span></span><span style="font-family:Arial, sans-serif;"><b>6.5.2: Members of
SO/AC/Groups should be involved in reviews of policies and procedures and
should approve any revisions.</b></span></span></div>
<div><span style="font-size:10pt;line-height:12pt;" class="xfmc1"><span lang="EN-CA" style="font-family:"Courier New";">o<span style="font-stretch:normal;font-family:"Times New Roman";"> </span></span><span lang="EN-CA" style="font-family:Arial, sans-serif;">Implemented (Operating Procedures, XV)</span></span></div>
<div><span style="font-size:10pt;line-height:12pt;" class="xfmc1"><span lang="EN-CA" style="font-family:Symbol;">·<span style="font-stretch:normal;font-family:"Times New Roman";">
</span></span><span style="font-family:Arial, sans-serif;"><b>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.</b></span></span></div>
<div><span style="font-size:10pt;line-height:12pt;" class="xfmc1"><span lang="EN-CA" style="font-family:"Courier New";">o<span style="font-stretch:normal;font-family:"Times New Roman";">
</span></span><span lang="EN-CA" style="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></div>
</div>
</div>
</div>
</blockquote>
<div><span style="font-size:10pt;font-family:Arial;line-height:12pt;color:rgb(255, 0, 0);" class="xfmc1">Agree</span></div>
<blockquote style="border-left:1px solid #cccccc;margin:0px 0px 0px 0.8ex;padding-left:1ex;">
<div style="display:block;">
<div>
<div><br/></div>
<div><br/></div>
<br/><div>
<div>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:</div>
<blockquote style="border-left:1px solid #cccccc;margin:0px 0px 0px 0.8ex;padding-left:1ex;">
<div>Dear all,
<div><br/></div>
<div>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. </div>
<div><br/></div>
<div>I would thus kindly ask you <span style="text-decoration:underline;"><b>to familiarize yourself with the attached PDF</b></span>, 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. </div>
<div><br/></div>
<div>I will be back to you <b><span style="text-decoration:underline;">tomorrow morning eurotime</span></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. </div>
<div><br/></div>
<div>Thank you and have a nice day</div>
<div><br/></div>
<div>
<div>
<div>---------- Forwarded message ---------<br/>From: <b>Chantelle Doerksen</b> <<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>></div>
<br/><br/><div lang="EN-US">
<div>
<div><span style="color:#000000;">Dear Raphael,</span></div>
<div style="text-align:start;"><span style="color:#000000;"> </span></div>
<div style="text-align:start;"><span style="color:#000000;">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" rel="noreferrer noopener"><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. <span style="text-decoration:underline;">Recommendations 1.2 - 1.6</span> (on <a href="https://www.icann.org/en/system/files/files/ccwg-acct-ws2-annex-1-diversity-final-recs-27mar18-en.pdf" target="_blank" rel="noreferrer noopener"><span style="color:#1155cc;">Diversity</span></a>),
and <span style="text-decoration:underline;">Recommendations 6.1 - 6.5</span> (on <a href="https://www.icann.org/en/system/files/files/ccwg-acct-ws2-annex-6-soac-final-recs-27mar18-en.pdf" target="_blank" rel="noreferrer noopener"><span style="color:#1155cc;">SOAC
Accountability</span></a>). </span></div>
<div style="text-align:start;"><span style="color:#000000;"> </span></div>
<div style="text-align:start;"><b><span style="color:#000000;">Scope of the initial mapping inventory:</span></b></div>
<div style="text-align:start;"><span style="color:#000000;">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></div>
<div><span style="color:#000000;"> </span></div>
<div style="text-align:start;"><span style="color:#000000;">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" rel="noreferrer noopener"><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" rel="noreferrer noopener"><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" rel="noreferrer noopener"><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></div>
<div style="text-align:start;"><span style="color:#000000;"> </span></div>
<div style="text-align:start;"><span style="color:#000000;">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></div>
<div style="text-align:start;"><span style="color:#000000;"> </span></div>
<div style="text-align:start;"><b><span style="color:#000000;">Mapping inventory</span></b><span style="color:#000000;">: <a href="https://docs.google.com/spreadsheets/d/1yQoIjRZnBIbaxwY6CVlPMjrMrZaweJFifmFxrIeyafI/edit#gid=0" target="_blank" rel="noreferrer noopener">https://docs.google.com/spreadsheets/d/1yQoIjRZnBIbaxwY6CVlPMjrMrZaweJFifmFxrIeyafI/edit#gid=0</a>
(attached in PDF format for reference) </span></div>
<div style="text-align:start;"><span style="color:#000000;"> </span></div>
<div style="text-align:start;"><b><span style="color:#000000;">Next Steps</span></b></div>
<div style="text-align:start;"><span style="color:#000000;">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></div>
<div style="text-align:start;"><span style="color:#000000;"> </span></div>
<div style="text-align:start;"><span style="color:#000000;">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><span style="text-decoration:underline;">Please
let us know if you would like us to schedule a call with you or your group’s representatives to discuss the inventory</span></b>. Thank you.</span></div>
<div style="text-align:start;"><span style="color:#000000;"> </span></div>
<div style="text-align:start;"><span style="color:#000000;">Best regards,</span></div>
<div style="text-align:start;"><span style="color:#000000;">Chantelle, Carlos, and Mary</span></div>
<div style="text-align:start;"><span style="color:#000000;"> </span></div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<pre style="margin:5px 0;">_______________________________________________
NCUC-EC mailing list
<a href="mailto:NCUC-EC@lists.ncuc.org" target="_self" rel="noreferrer noopener">NCUC-EC@lists.ncuc.org</a><a href="https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec" target="_blank" rel="noreferrer noopener">https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec</a></pre>
</blockquote></span></body></html>