<div dir="ltr"><div>Hi Rafik,</div><div><br></div><div>To clarify, I am not seeking restitution or remedy for the situation. NPOC EC has chosen and that's all good by me.</div><div>My contention is how all of this has happened as the acceptance of the seat had commitment and work consequences + how things have been handled.</div><div>Following the procedures is not an issue to me, being treated like a pawn that I take issue with.</div><div><br></div><div>It is of my opinion this is to be addressed by NPOC and hopefully this doesn't occur again with other members.</div><div>I agree that ICANN has no beef in these internal matters (nor the Ombudsman).</div><div><br></div><div>Best,</div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div></div><div>Jean F. Queralt</div><div>Founder & CEO - <a href="https://TheIOFoundation.org" target="_blank">The IO Foundation</a></div><div><a href="https://TIOF.Click/BookJFQ" target="_blank">Book a meeting</a> (30 minutes)<br></div></div></div></div><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, 21 Jan 2025 at 14:08, Rafik Dammak <<a href="mailto:rafik.dammak@gmail.com">rafik.dammak@gmail.com</a>> wrote:<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>With regard to the mandate, this is an NPOC internal matter. NCSG charter covers NCSG matters such as membership, committees etc but each constituency has its own charter/bylaw and operating procedures for appointing representatives to NCSG committees. We can only offer support to help parties to resolve this and find an acceptable agreement.</div><div><br></div><div>ICANN org has nothing to do with this and I don't see why it would get involved. What I might propose or suggest as possible options for consideration by the impacted parties:</div><div>1- if all parties agree, I can as NCSG chair volunteer to be a mediator and do a fact seeking mission first to clarify the situation.</div><div>2- or a group of 3 people including NCSG chair, 1 member from NCUC and another from NPOC that all parties can trust to do the mediation and fact seeking</div></div>3- or all parties can go to ICANN Ombudsman instead and leverage them as more experienced mediator and someone external from our community. Ombudsman is supposedly independent from ICANN org.<div><div><div><br></div><div>Best regards,</div><div><br></div><div>Rafik</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mar. 21 janv. 2025 à 00:52, Johan Helsingius <<a href="mailto:00001963cc94b85a-dmarc-request@listserv.syr.edu" target="_blank">00001963cc94b85a-dmarc-request@listserv.syr.edu</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">On 20/01/2025 16:35, Arsène Tungali wrote:<br>
> I am wondering who has the responsibility to make sure NPOC leadership <br>
> is held to account? The NCSG? ICANN org? I know the answer is somewhere <br>
> in the charter, or maybe not.<br>
<br>
Basically the members (who elect the EC and Chair). ICANN org definitely<br>
doesn't have any (formal) way to do anything, and NCSG has traditionally<br>
tried to leave the two constituencies to do their own thing.<br>
<br>
Julf<br>
</blockquote></div></div></div></div></div>
</blockquote></div>
<br>
<div><i><font size="2" color="#808080"><b>DISCLAIMER</b></font></i></div><div><i><font size="2" color="#808080">The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.</font></i></div>