<div dir="ltr"><div>Hi Rafik!</div><div><br></div><div>Sorry for the delayed answer - yes I can! As a starter:</div><div><br></div><div><span><table cellspacing="0" cellpadding="0" dir="ltr" border="1" style="table-layout:fixed;font-size:10pt;font-family:Arial;width:0px;border-collapse:collapse;border:medium"><colgroup><col width="97"><col width="559"></colgroup><tbody><tr style="height:21px"><td style="overflow:hidden;padding:2px 3px;vertical-align:top;white-space:normal;border:1px solid rgb(204,204,204)">Rec 06.1.3</td><td style="overflow:hidden;padding:2px 3px;vertical-align:top;font-size:9pt;white-space:normal;border:1px solid rgb(204,204,204)">SO/AC/Groups should document their procedures for non-members to challenge decisions regarding their eligibility to become a member.<br><i><u>Comment: This can be added in the NCSG Operating Procedures review, and it is relatively easy to do.</u></i></td></tr><tr style="height:21px"><td style="overflow:hidden;padding:2px 3px;vertical-align:top;white-space:normal;border:1px solid rgb(204,204,204)">Rec 06.1.4</td><td style="overflow:hidden;padding:2px 3px;vertical-align:top;font-size:9pt;white-space:normal;border:1px solid rgb(204,204,204)">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.<br>
<span><i><u>Comment: This is a hard one - we actually do that when we update the Operating Procedures, so I believe we can say this is complete after reaching out to previous EC members about non-written practices, adding the ones that we think are relevant to the Operating Procedures, then mark as complete.</u></i></span></td></tr><tr style="height:21px"><td style="overflow:hidden;padding:2px 3px;vertical-align:top;white-space:normal;border:1px solid rgb(204,204,204)">Rec 06.1.5</td><td style="overflow:hidden;padding:2px 3px;vertical-align:top;font-size:9pt;white-space:normal;border:1px solid rgb(204,204,204)">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.<br>
<span><i><u>Comment: We started to do this at the NCUC EC. We can do something similar here, a simplified </u></i></span><u><i>report that is updated recurrently with what the EC members are doing or following. It doesn't encompass all NCSG activities, but will encompass a lot of them</i></u></td></tr><tr style="height:21px"><td style="overflow:hidden;padding:2px 3px;vertical-align:top;white-space:normal;border:1px solid rgb(204,204,204)">Rec 06.3.3</td><td style="overflow:hidden;padding:2px 3px;vertical-align:top;font-size:9pt;white-space:normal;border:1px solid rgb(204,204,204)">Where membership must be applied for, there should be a process of appeal when application for membership is rejected.<br>
<span><i><u>Comment: Same as Rec 06.1.3</u></i></span></td></tr><tr style="height:21px"><td style="overflow:hidden;padding:2px 3px;vertical-align:top;white-space:normal;border:1px solid rgb(204,204,204)">Rec 06.4.3</td><td style="overflow:hidden;padding:2px 3px;vertical-align:top;font-size:9pt;white-space:normal;border:1px solid rgb(204,204,204)">Each SO/AC/Group should create a committee (of appropriate size) to manage outreach programs to attract additional eligible members, particularly from parts of their targeted community that may not be adequately participating.<br>
<span><i><u>Comment: I don't think creating a new one is really necessary. I believe this should be a task of EC members, and, in our case, mostly from the NCUC and NPOC EC, and we already have this in our governance documents. I would mark this is as complete</u></i></span></td></tr><tr style="height:21px"><td style="overflow:hidden;padding:2px 3px;vertical-align:top;white-space:normal;border:1px solid rgb(204,204,204)">Rec 06.4.4</td><td style="overflow:hidden;padding:2px 3px;vertical-align:top;font-size:9pt;white-space:normal;border:1px solid rgb(204,204,204)">Outreach objectives and potential activities should be mentioned in SO/AC/Group bylaws, charter, or procedures.<br>
<span><i><u>Comment: We already have this at the beginning of our Charter. Already complete.</u></i></span></td></tr><tr style="height:21px"><td style="overflow:hidden;padding:2px 3px;vertical-align:top;white-space:normal;border:1px solid rgb(204,204,204)">Rec 06.4.5</td><td style="overflow:hidden;padding:2px 3px;vertical-align:top;font-size:9pt;white-space:normal;border:1px solid rgb(204,204,204)">Each SO/AC/Group should have a strategy for outreach to parts of their targeted community that may not be significantly participating at the time, while also seeking diversity within membership.<br>
<span><i><u>Comment: See comment 06.4.3.</u></i></span></td></tr><tr style="height:21px"><td style="overflow:hidden;padding:2px 3px;vertical-align:top;white-space:normal;border:1px solid rgb(204,204,204)">Rec 06.5.1</td><td style="overflow:hidden;padding:2px 3px;vertical-align:top;font-size:9pt;white-space:normal;border:1px solid rgb(204,204,204)">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.<br>
<span><i><u>Comment: We could add this to the operating procedures, but I think the best place for it would be the charter. And I am not sure if changing the charter because of this (it is really hard to to this change) would be a good idea.</u></i></span></td></tr><tr style="height:21px"><td style="overflow:hidden;padding:2px 3px;vertical-align:top;white-space:normal;border:1px solid rgb(204,204,204)">Rec 06.5.2</td><td style="overflow:hidden;padding:2px 3px;vertical-align:top;font-size:9pt;white-space:normal;border:1px solid rgb(204,204,204)">Members of SO/AC/Groups should be involved in reviews of policies and procedures and should approve any revisions.<br>
<span><i><u>Comment: Already complete for the charter. We, however, do not have any disposition about it in the Operating Procedures. Maybe adding one? (It shouldn't be as complex as one of the NCUC Operating Procedures; however, one public consultation for members to give their input <a class="gmail_plusreply" id="plusReplyChip-0">+</a> another simplified public consultation to get feedback on the final version is more than enough)</u></i></span></td></tr><tr style="height:21px"><td style="overflow:hidden;padding:2px 3px;vertical-align:top;white-space:normal;border:1px solid rgb(204,204,204)">Rec 06.5.3</td><td style="overflow:hidden;padding:2px 3px;vertical-align:top;font-size:9pt;white-space:normal;border:1px solid rgb(204,204,204)">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.<br>
<span><i><u>Comment: We don't have any rules limiting the period of review. Maybe adding something to the Operating Procedures? I don't believe this is deeply necessary; however, in practice, we rarely will prolong the process for more than one year because that would mean a change in the EC and a possibility of restarting the whole process.</u></i></span></td></tr></tbody></table></span></div><div><br></div><div><a class="gmail_plusreply" id="plusReplyChip-1" href="mailto:rafik.dammak@gmail.com" tabindex="-1">@Rafik Dammak</a> , shall we use the doc Jean created before (that Google Sheets file) for continuing the OP review? If yes, we can check who from the new EC would like to join us (we will select the new NCUC reps to the EC now, and I think they can already be invited as a transition period, since the new NPOC reps are already with us) and start this ASAP.</div><div><br></div><div>Cordially,</div><div><br clear="all"></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><b>Pedro de Perdigão Lana</b><br></font></font></span><div><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><a href="https://www.nic.br/" target="_blank">Lawyer</a>, </font></font></span><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><a href="https://www.gedai.com.br/" target="_blank">GEDAI/UFPR</a> Researcher</font></font></span></font></font></span></font></font></span></div><div><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2">PhD Candidate (UFPR), LLM in Business Law (UCoimbra)</font></font></span><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"> </font></font></span></font></font></span></div><div><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><span style="font-family:garamond,times new roman,serif"></span></font></font></span></div><div><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2">Coordination/Board/EC @</font></font></span><span style="font-family:times new roman,serif"><font size="1"><font size="2"> </font></font></span><span style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><a href="https://www.isoc.org.br/" target="_blank">ISOC Brazil</a>,</span><span style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><font size="1"><font size="2"> </font></font><font size="2"><a href="https://www.ncuc.org/" target="_blank">NCUC</a> & <a href="https://community.icann.org/display/gnsononcomstake/Home" target="_blank">NCSG </a>(ICANN) and </font></span><span style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><font size="1"><font size="2"><a href="https://br.creativecommons.net/" target="_blank">CC Brazil</a></font></font></span><span style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)">.</span><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><br></font></font></span></div><div><span style="font-family:garamond,times new roman,serif"></span></div><div><font size="1"><span style="font-family:garamond,times new roman,serif">This message is restricted to the sender and recipient(s). If received by mistake, please reply informing it.</span></font></div></div></div></div><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">Em sex., 5 de dez. de 2025 às 03:22, Rafik Dammak <<a href="mailto:rafik.dammak@gmail.com">rafik.dammak@gmail.com</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div>Hi all,</div><div><br></div><div>ICANN staff reached me again to remind me about those recommendations and follow-up. I responded that either they are planned for implementation or internal discussion and they can change status in their status to complete. </div><div>We discussed previously having those as part of actions in addition to operation procedures review including also those about the election process. I know we are in the middle of EC change but there should be some continuity and we will try to share with membership for input.</div><div><br></div><div><a class="gmail_plusreply" id="m_8814315589807691695plusReplyChip-0" href="mailto:pedrodeperdigaolana@gmail.com" target="_blank">@Pedro de Perdigão Lana</a> I know you are keen to work on this, can you kick off separate discussion/doc for OP review including those recommendations when relevant and also about election.<br></div><div><br></div><div>Best,</div><div><br></div><div>Rafik</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le lun. 11 août 2025 à 07:33, Pedro de Perdigão Lana <<a href="mailto:pedrodeperdigaolana@gmail.com" target="_blank">pedrodeperdigaolana@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi EC,</div><div><br></div><div><ul><li>6.1.3: SO/AC/Groups should document their procedures for non-members to challenge decisions regarding their eligibility to become a member:</li><ul><li>We don't have an appeal option. Maybe it would be interesting to think of one.</li></ul><li>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:</li><ul><li>Our Operating Procedures are kind of this, but probably we need a more in-depth analysis if other practices that are not written down remain.</li></ul><li>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.</li><ul><li>We don't have a requirement like this, and we need to do this urgently, making this an obligation, especially to EC members.</li></ul><li>6.3.3: Where membership must be applied for, there should be a process of appeal when application for membership is rejected.</li><ul><li>See reply to 6.1.3.</li></ul><li>6.4.3: Each SO/AC/Group should create a committee (of appropriate size) to manage outreach programs to attract additional eligible members, particularly from parts of their targeted community that may not be adequately participating.</li><ul><li>This would be important to do, but we do not have enough manpower to do it while we remain with the other issues (such as the lack of engagement and dedication even within the leadership)</li></ul><li>6.4.4: Outreach objectives and potential activities should be mentioned in SO/AC/Group bylaws, charter, or procedures.</li><ul><li>We kind of already have this (see NCSG Charter, 2.2.10), but very superficial. NCUC already has it more detailed, I don't know what the situation is in NPOC. I think that, reading the SG and C documentation together, we already have this covered.</li></ul><li>6.4.5: Each SO/AC/Group should have a strategy for outreach to parts of their targeted community that may not be significantly participating at the time, while also seeking diversity within membership.</li><ul><li>See previous comment. I think we already have it solved, at least "on paper".</li></ul><li>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.</li><ul><li>Agree, we should have one for the OP at least. We are trying to review the NCSG Operating Procedures, but not enough time available. NCUC already has an obligation like this for its OP, although it wasn't being followed until we noticed it in this current term.</li></ul><li>6.5.2: Members of SO/AC/Groups should be involved in reviews of policies and procedures and should approve any revisions.</li><ul><li>Agree. We already have this for the charter, but not for the OP. However, I think a dialogue between the EC and the community is the best way to go, instead of just a community vote (for the charter, however, a community vote as the final decision seems to be the correct way to go).</li></ul><li>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.</li><ul><li>We may need to add this limitation to the Operating Procedures. Not sure if I agree with this for the charter, because, with the interaction with the ICANN Board, this could take more than a year.</li></ul></ul></div><div><br></div><div>Cordially,</div><div><br clear="all"></div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><span style="font-family:garamond,"times new roman",serif"><font size="1"><font size="2"><b>Pedro de Perdigão Lana</b><br></font></font></span><div><span style="font-family:garamond,"times new roman",serif"><font size="1"><font size="2"><a href="https://www.nic.br/" target="_blank">Lawyer</a>, </font></font></span><span style="font-family:garamond,"times new roman",serif"><font size="1"><font size="2"><span style="font-family:garamond,"times new roman",serif"><font size="1"><font size="2"><span style="font-family:garamond,"times new roman",serif"><font size="1"><font size="2"><a href="https://www.gedai.com.br/" target="_blank">GEDAI/UFPR</a> Researcher</font></font></span></font></font></span></font></font></span></div><div><span style="font-family:garamond,"times new roman",serif"><font size="1"><font size="2">PhD Candidate (UFPR), LLM in Business Law (UCoimbra)</font></font></span><span style="font-family:garamond,"times new roman",serif"><font size="1"><font size="2"><span style="font-family:garamond,"times new roman",serif"><font size="1"><font size="2"> </font></font></span></font></font></span></div><div><span style="font-family:garamond,"times new roman",serif"><font size="1"><font size="2"><span style="font-family:garamond,"times new roman",serif"></span></font></font></span></div><div><span style="font-family:garamond,"times new roman",serif"><font size="1"><font size="2">Coordination/Board/EC @</font></font></span><span style="font-family:"times new roman",serif"><font size="1"><font size="2"> </font></font></span><span style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><a href="https://www.isoc.org.br/" target="_blank">ISOC Brazil</a>,</span><span style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><font size="1"><font size="2"> </font></font><font size="2"><a href="https://www.ncuc.org/" target="_blank">NCUC</a> & <a href="https://community.icann.org/display/gnsononcomstake/Home" target="_blank">NCSG </a>(ICANN) and </font></span><span style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><font size="1"><font size="2"><a href="https://br.creativecommons.net/" target="_blank">CC Brazil</a></font></font></span><span style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)">.</span><span style="font-family:garamond,"times new roman",serif"><font size="1"><font size="2"><br></font></font></span></div><div><span style="font-family:garamond,"times new roman",serif"></span></div><div><font size="1"><span style="font-family:garamond,"times new roman",serif">This message is restricted to the sender and recipient(s). If received by mistake, please reply informing it.</span></font></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em ter., 5 de ago. de 2025 às 04:39, Rafik Dammak via NCSG-EC <<a href="mailto:ncsg-ec@lists.ncsg.is" target="_blank">ncsg-ec@lists.ncsg.is</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>hi all,</div><div><br></div><div>We got this from ICANN org with regard to implementation of workstream 2 implementation for recommendation #6 . I believe we responded to this a while ago, in the previous EC , <a class="gmail_plusreply" id="m_8814315589807691695m_5862085720444154256m_5125095272612552860plusReplyChip-0" href="mailto:andrea.glandon@icann.org" target="_blank">@Andrea Glandon</a> can you please confirm what was done and covered previously on the matter.</div><div>We have to review the spreadsheet and make a decision, possibly a topic for the next EC meeting while we should review those items beforehand. any agreed item in the recommendation means we have to implement that with relevant procedure.</div><div><br></div><div>Best,</div><div><br></div><div>Rafik</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br><br></div><br><br><div>
<div lang="EN-US">
<div>
<p style="margin:0in"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">Dear Rafik, </span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">Implementation on Work Stream 2 Recommendation 6 was addressed to all ICANN Community groups, and implementation work is still ongoing. </span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">It is important to note that recommendation 6 are good practice recommendations, so they are not mandatory.</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">If your group chooses not to implement any part of the recommendation, please note "Won't be Implemented" in column C of your group’s inventory so that we may consider
the work complete.</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">WS2 inventory:
</span><a href="https://docs.google.com/spreadsheets/d/1xxPZjIjrjLBiKjcgWKbhhxWhbsBdcRudCqRDl4W5UlY/edit?gid=0#gid=0" target="_blank"><span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(17,85,204)">https://docs.google.com/spreadsheets/d/1xxPZjIjrjLBiKjcgWKbhhxWhbsBdcRudCqRDl4W5UlY/edit?gid=0#gid=0</span></a><span style="font-size:11pt;font-family:Arial,sans-serif;color:black"> </span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">The following recommendations require an action or decision:</span><u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif">6.1.3<u></u><u></u></span></li><li class="MsoNormal" style="color:black;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif">6.1.4<u></u><u></u></span></li><li class="MsoNormal" style="color:black;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif">6.1.5<u></u><u></u></span></li><li class="MsoNormal" style="color:black;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif">6.3.3<u></u><u></u></span></li><li class="MsoNormal" style="color:black;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif">6.4.3<u></u><u></u></span></li><li class="MsoNormal" style="color:black;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif">6.4.4<u></u><u></u></span></li><li class="MsoNormal" style="color:black;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif">6.4.5<u></u><u></u></span></li><li class="MsoNormal" style="color:black;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif">6.5.1<u></u><u></u></span></li><li class="MsoNormal" style="color:black;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif">6.5.2<u></u><u></u></span></li><li class="MsoNormal" style="color:black;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif">6.5.3<u></u><u></u></span></li></ul>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">More information on WS2 can be found here:
</span><a href="https://icann-community.atlassian.net/wiki/x/TxwIBg" target="_blank"><span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(17,85,204)">https://icann-community.atlassian.net/wiki/x/TxwIBg</span></a><span style="font-size:11pt;font-family:Arial,sans-serif;color:black"> </span></p>
<p style="margin:0in"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">SO/AC Accountability sub-group Final Report and Recommendations:
</span><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="font-size:11pt;font-family:Arial,sans-serif;color:rgb(17,85,204)">https://www.icann.org/en/system/files/files/ccwg-acct-ws2-annex-6-soac-final-recs-27mar18-en.pdf</span></a><span style="font-size:11pt;font-family:Arial,sans-serif;color:black"> </span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">Please reach out if you would like to schedule a call to discuss this further.</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">Thank you for your time.</span></p>
<p style="margin:0in"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">Kind regards,</span></p>
<p style="margin:0in"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">Nathalie and Devan</span></p>
<p style="margin:0in"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">On behalf of the team supporting WS2 community implementation efforts</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div></div></div>
_______________________________________________<br>
NCSG-EC mailing list<br>
<a href="mailto:NCSG-EC@lists.ncsg.is" target="_blank">NCSG-EC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-ec" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-ec</a><br>
</blockquote></div>
</blockquote></div></div>
</blockquote></div>