<div dir="auto"><div>Dear Julf</div><div dir="auto"><br></div><div dir="auto">Thank you for your email. Just a note that it s been some time, maybe a year that I didn't receive nomcom review emails so thought either there was an update in the memberhip or I didnot reconfirm my subscription. Hence, I was not part of this review and heard about it recently as everyone else .</div><div dir="auto"><br></div><div dir="auto">I will check with staff if I am still part of this review team although no longer receiving emails.</div><div dir="auto"><br></div><div dir="auto">That said, thank you for updating us on the deadline and if you have information on how GNSO constituencies want to proceed about selecting those 3 nomcom reps out of 7 to serve for one year.<br><div dir="auto"><br></div><div dir="auto"><br></div><br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Tue, Jun 4, 2024, 18:06 Benjamin Akinmoyeje <<a href="mailto:benakin@gmail.com">benakin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"> Hi Julf, <div dir="auto">Thank you for this email....but it is strange that the GNSO chair has chosen not to copy the NCUC Chair in this email.</div><div dir="auto"><br></div><div dir="auto">NCUC appointed Pascal, our current Nomcom representative if I am correct.</div><div dir="auto"><br></div><div dir="auto">It would be great if the GNSO chair could be pointed to this omission.</div><div dir="auto"><br></div><div dir="auto">Just checking if things have changed.<br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">Kind regards,</div><div dir="auto">Benjamin </div><div dir="auto"></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jun 1, 2024 at 9:32 AM Johan Helsingius <<a href="mailto:julf@julf.com" target="_blank" rel="noreferrer">julf@julf.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"><br>
<br>
<br>
-------- Forwarded Message --------<br>
Subject: NomCom changes<br>
Date: Fri, 31 May 2024 14:41:19 +0000<br>
From: DiBiase, Gregory <<a href="mailto:dibiase@amazon.com" target="_blank" rel="noreferrer">dibiase@amazon.com</a>><br>
To: <a href="mailto:aheineman@godaddy.com" target="_blank" rel="noreferrer">aheineman@godaddy.com</a> <<a href="mailto:aheineman@godaddy.com" target="_blank" rel="noreferrer">aheineman@godaddy.com</a>>, Lori Schulman <br>
<<a href="mailto:lschulman@inta.org" target="_blank" rel="noreferrer">lschulman@inta.org</a>>, Cole, Mason (POR) <<a href="mailto:MCole@perkinscoie.com" target="_blank" rel="noreferrer">MCole@perkinscoie.com</a>>, Johan <br>
Helsingius <julf@Julf.com>, <a href="mailto:sdemetriou@verisign.com" target="_blank" rel="noreferrer">sdemetriou@verisign.com</a> <br>
<<a href="mailto:sdemetriou@verisign.com" target="_blank" rel="noreferrer">sdemetriou@verisign.com</a>>, <a href="mailto:philippe.fouquart@orange.com" target="_blank" rel="noreferrer">philippe.fouquart@orange.com</a> <br>
<<a href="mailto:philippe.fouquart@orange.com" target="_blank" rel="noreferrer">philippe.fouquart@orange.com</a>><br>
CC: Steve Chan <<a href="mailto:steve.chan@icann.org" target="_blank" rel="noreferrer">steve.chan@icann.org</a>>, <a href="mailto:gnso-secs@icann.org" target="_blank" rel="noreferrer">gnso-secs@icann.org</a> <br>
<<a href="mailto:gnso-secs@icann.org" target="_blank" rel="noreferrer">gnso-secs@icann.org</a>><br>
<br>
<br>
<br>
Dear Ashley, Julf, Lori, Mason, Philippe, and Samantha,<br>
<br>
I am writing to you all in your roles as Chairs of Stakeholder Groups or <br>
Constituencies that appoint delegates to ICANN’s Nominating Committee <br>
(NomCom).<br>
<br>
You may recall that the NomCom2 Review produced 27 recommendations, <br>
several of which relate to the composition and terms of the NomCom. In <br>
order to effectuate these particular recommendations, the ICANN Board <br>
approved Standard Bylaws Amendments in Articles 8, 12, and 27.<br>
<br>
The Bylaws amendments made no change to the number and nature of <br>
delegates from the GNSO (i.e., 1 each from the RySG, RrSG, ISPCP, IPC, <br>
NCSG, and 2 from the BC), though the length of terms were extended to <br>
two years (see Section 8.3 of the Bylaws). However, from Article 27, in <br>
order to, “effectuate the introduction of the two-year terms and support <br>
the goal of staggering delegate terms…”, three of the GNSO delegates <br>
shall serve a one-year term. ARTICLE 27 TRANSITION ARTICLE states that <br>
the GNSO is responsible for determining which three of the seven <br>
delegates shall initially serve one-year terms.<br>
<br>
Unfortunately, no guidance was provided on how to identify the three of <br>
seven GNSO delegates to serve one-year terms. For reference, the ALAC <br>
was also in the position of having to identify a subset of delegates to <br>
serve one-year terms. They elected to rely on random selection during a <br>
live call.<br>
<br>
The GNSO may want to rely on a similarly simple approach. An important <br>
point in considering the approach is that the level of representation on <br>
the NomCom is not affected by the term-length. However, the SG/Cs with <br>
one-year terms will have to replace those delegates after one year <br>
rather than two.<br>
<br>
*Question: Do you believe there would be any objections from your <br>
groups, and potentially delegates that you have already identified, to <br>
proceeding with a simple path forward in which we randomly select three <br>
of seven GNSO delegates to serve one-year terms?*<br>
<br>
If you believe that there may be concerns (e.g., we may want to avoid <br>
having the one-year terms concentrated in particular areas), please <br>
share them with Council leadership no later than 31 May 2024.<br>
<br>
If however there are no concerns, Council leadership can perform the <br>
random selection process with staff or if you prefer, on a Zoom call <br>
with all of you.<br>
<br>
Thanks,<br>
<br>
Greg DiBiase, GNSO Chair<br>
<br>
</blockquote></div>
_______________________________________________<br>
NCUC-EC mailing list<br>
<a href="mailto:NCUC-EC@lists.ncuc.org" target="_blank" rel="noreferrer">NCUC-EC@lists.ncuc.org</a><br>
<a href="https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec" rel="noreferrer noreferrer" target="_blank">https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec</a><br>
</blockquote></div></div></div>