<div dir="auto">I got your email. It was just that the GNSO chair , did not copy NCUC chair.<div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">That it is worthwhile noting for future, although in his email he made references to stakeholder group an constituencies. </div><div dir="auto"><br></div><div dir="auto">I hope you see my point.</div><div dir="auto"><br></div><div dir="auto">Kind regards,</div><div dir="auto">Benjamin </div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 4, 2024, 9:35 PM Johan Helsingius <<a href="mailto:julf@julf.com">julf@julf.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I did copy ncuc-ec, assuming the chair would be part of it.<br>
<br>
Julf<br>
<br>
On 04/06/2024 18:59, Benjamin Akinmoyeje wrote:<br>
> Hi Julf,<br>
> Thank you for this email....but it is strange that the GNSO chair has <br>
> chosen not to copy the NCUC Chair in this email.<br>
> <br>
> NCUC appointed Pascal, our current Nomcom representative if I am correct.<br>
> <br>
> It would be great if the GNSO chair could be pointed to this omission.<br>
> <br>
> Just checking if things have changed.<br>
> <br>
> <br>
> Kind regards,<br>
> Benjamin<br>
> <br>
> 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> <br>
> <mailto:<a href="mailto:julf@julf.com" target="_blank" rel="noreferrer">julf@julf.com</a>>> wrote:<br>
> <br>
> <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>
> <mailto:<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> <mailto:<a href="mailto:aheineman@godaddy.com" target="_blank" rel="noreferrer">aheineman@godaddy.com</a>><br>
> <<a href="mailto:aheineman@godaddy.com" target="_blank" rel="noreferrer">aheineman@godaddy.com</a> <mailto:<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> <mailto:<a href="mailto:lschulman@inta.org" target="_blank" rel="noreferrer">lschulman@inta.org</a>>>, Cole, Mason (POR)<br>
> <<a href="mailto:MCole@perkinscoie.com" target="_blank" rel="noreferrer">MCole@perkinscoie.com</a> <mailto:<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>
> <mailto:<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> <mailto:<a href="mailto:sdemetriou@verisign.com" target="_blank" rel="noreferrer">sdemetriou@verisign.com</a>>>,<br>
> <a href="mailto:philippe.fouquart@orange.com" target="_blank" rel="noreferrer">philippe.fouquart@orange.com</a> <mailto:<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> <mailto:<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><br>
> <mailto:<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>
> <mailto:<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> <mailto:<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<br>
> 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<br>
> 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<br>
> 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>