<div dir="auto">Thanks Julf. Michele confirmed. He will be remote so can’t do hands on stuff. </div><div dir="auto"><br></div><div dir="auto"><br clear="all"><br clear="all"><div dir="auto"><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font face="verdana, sans-serif" style="font-family:verdana,sans-serif;color:rgb(0,0,0)">Farzaneh </font></div></div></div></div></div><div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jun 3, 2024 at 3:33 PM Johan Helsingius <<a href="mailto:julf@julf.com">julf@julf.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">Unfortunately it seems there is a conflict with a RrSG "all hands<br>
on deck" session.<br>
<br>
Was there any contact with the RrSG before I contacted their<br>
leadership? I would have expected them to flag the conflict...<br>
<br>
        Julf<br>
<br>
<br>
On 29/05/2024 17:28, Benjamin Akinmoyeje wrote:<br>
> Dear Julf,<br>
> Thank you for offering to help invite RrSG leadership. Any assistance <br>
> would be greatly appreciated in getting the audience and speakers to <br>
> participate.<br>
> <br>
> Farzii is also reaching out to some stakeholders as well.<br>
> <br>
> All hands are needed here.<br>
> <br>
> <br>
> Kind regards,<br>
> Benjamin<br>
> <br>
> On Wed, May 29, 2024 at 1:20 PM Johan Helsingius via NCUC-EC <br>
> <<a href="mailto:ncuc-ec@lists.ncuc.org" target="_blank">ncuc-ec@lists.ncuc.org</a> <mailto:<a href="mailto:ncuc-ec@lists.ncuc.org" target="_blank">ncuc-ec@lists.ncuc.org</a>>> wrote:<br>
> <br>
>     Benjamin, Ken,<br>
> <br>
>     Let me know if you need me to talk to the RrSG leadership.<br>
> <br>
>              Julf<br>
> <br>
> <br>
>     On 29/05/2024 05:13, Ken Herman wrote:<br>
>      > Dear Benjamin, Thank you.<br>
>      ><br>
>      > As one of the participants, I remain available to provide additional<br>
>      > input, beyond the input I already provided. However, since the theme<br>
>      > seems to require participation by registrars, I ask, again, if<br>
>     you, in<br>
>      > your capacity as Chair of the NCUC, will be reaching out to the RrSG<br>
>      > requesting their participation. We can work out the details, but it<br>
>      > would be good to know whom we can call upon. If you have some other<br>
>      > approach, then please let us know.<br>
>      ><br>
>      > Mili and Pedro, perhaps we can speak in the next day or so to<br>
>     work on<br>
>      > those details.<br>
>      ><br>
>      > Ken<br>
>      ><br>
>      > *From:*Benjamin Akinmoyeje <<a href="mailto:benakin@gmail.com" target="_blank">benakin@gmail.com</a><br>
>     <mailto:<a href="mailto:benakin@gmail.com" target="_blank">benakin@gmail.com</a>>><br>
>      > *Sent:* Tuesday, May 28, 2024 5:12 PM<br>
>      > *To:* Ken Herman <<a href="mailto:ken@kherman.com" target="_blank">ken@kherman.com</a> <mailto:<a href="mailto:ken@kherman.com" target="_blank">ken@kherman.com</a>>><br>
>      > *Cc:* Exec. Comm <<a href="mailto:ncuc-ec@lists.ncuc.org" target="_blank">ncuc-ec@lists.ncuc.org</a><br>
>     <mailto:<a href="mailto:ncuc-ec@lists.ncuc.org" target="_blank">ncuc-ec@lists.ncuc.org</a>>><br>
>      > *Subject:* Re: issue Forum Status?<br>
>      ><br>
>      > Dear Ken,<br>
>      ><br>
>      > Thank you for your email. The NCUC Issue Forum and NCUC membership<br>
>      > meeting require the input of NCUC  official representatives to<br>
>     the ICANN<br>
>      > meeting.<br>
>      ><br>
>      > I have asked and requested topics and speakers; below is what I<br>
>     have so<br>
>      > far; the process is open to those of us attending ICANN80 to organize<br>
>      ><br>
>      > NCUC Issue forum<br>
>      ><br>
>      ><br>
>     <a href="https://docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing</a> <<a href="https://docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing</a>> <<a href="https://docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing</a> <<a href="https://docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1gQA5Jv7zLkMSJx1-oDAxBXfuqx_cs9t4-7KrnArilPA/edit?usp=sharing</a>>><br>
>      ><br>
>      > NCUC membership meeting<br>
>      ><br>
>      ><br>
>     <a href="https://docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit</a> <<a href="https://docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit</a>> <<a href="https://docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit</a> <<a href="https://docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1qdHd3_NQJK5FR-spDQF3zOexHbeHHE0wJJtnlZYPZ-Q/edit</a>>><br>
>      ><br>
>      > Additionally, contributions from you and Mili will go a long way in<br>
>      > finalizing the events.<br>
>      ><br>
>      > Kind regards,<br>
>      ><br>
>      > Benjamin<br>
>      ><br>
>      > On Tue, May 28, 2024 at 6:21 PM Ken Herman <<a href="mailto:ken@kherman.com" target="_blank">ken@kherman.com</a><br>
>     <mailto:<a href="mailto:ken@kherman.com" target="_blank">ken@kherman.com</a>><br>
>      > <mailto:<a href="mailto:ken@kherman.com" target="_blank">ken@kherman.com</a> <mailto:<a href="mailto:ken@kherman.com" target="_blank">ken@kherman.com</a>>>> wrote:<br>
>      ><br>
>      >     Benjamin, I’m wondering where we are with the issue forum<br>
>     planning.<br>
>      >     Last I recall there were some ideas around registrant<br>
>      >     rights/security, and the need to reach out to the Registrar<br>
>     SG, but<br>
>      >     haven’t heard if anything has developed.<br>
>      ><br>
>      >     Where do we stand, please?<br>
>      ><br>
>      >     Thanks<br>
>      ><br>
>      >     Ken<br>
>      ><br>
>      ><br>
>      > _______________________________________________<br>
>      > NCUC-EC mailing list<br>
>      > <a href="mailto:NCUC-EC@lists.ncuc.org" target="_blank">NCUC-EC@lists.ncuc.org</a> <mailto:<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" rel="noreferrer" target="_blank">https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec</a><br>
>     <<a href="https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec" rel="noreferrer" target="_blank">https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec</a>><br>
>     _______________________________________________<br>
>     NCUC-EC mailing list<br>
>     <a href="mailto:NCUC-EC@lists.ncuc.org" target="_blank">NCUC-EC@lists.ncuc.org</a> <mailto:<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" rel="noreferrer" target="_blank">https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec</a><br>
>     <<a href="https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec" rel="noreferrer" target="_blank">https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec</a>><br>
> <br>
</blockquote></div></div>