<div dir="auto"><div>Hi Juan,</div><div dir="auto"><br></div><div dir="auto">It might just be my brain having a slow start, but I didn't understand the complexity you described is introduces to NCSG.</div><div dir="auto"><br></div><div dir="auto"><span class="gmail_chip gmail_plusreply" dir="auto"><a href="mailto:julf@julf.com" style="color:#15c;text-decoration:underline">@Johan Helsingius</a></span><span> I feel like we should include the EC in this discussion. I believe that they would want to be part of the decision making?</span></div><div><br></div><div data-smartmail="gmail_signature">Warmly, <br>Tomslin</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, 2 June 2024, 03:26 Juan Manuel Rojas via NCSG-PC, <<a href="mailto:ncsg-pc@lists.ncsg.is">ncsg-pc@lists.ncsg.is</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:Helvetica Neue,Helvetica,Arial,sans-serif;font-size:13px"><div><div dir="ltr"> <div><div>Hi Julf and all,</div><div><br></div><div>I think the rotation from two years to one should apply to constituencies that have two representatives on the NomCom, such as the BC. We only have one seat, and it could add too much complexity to our election process to include one more position, despite this position being appointed in our case.</div></div><br></div><div><br></div><div><div style="font-size:13px;font-family:Helvetica,Arial,sans-serif"><div><div id="m_-6077332719291062321ydpbc80bd55yui_3_16_0_ym19_1_1467397914851_28423"><span style="font-size:small"><b>JUAN MANUEL ROJAS, M.Sc.</b><br style="color:rgb(69,69,69)"></span><div><span style="font-size:small"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#808080" style="background-color:inherit"><span id="m_-6077332719291062321ydpbc80bd55yui_3_16_0_ym19_1_1467397914851_29214">Director - MINKA DIGITAL Colombia</span></font></span></div></div><div id="m_-6077332719291062321ydpbc80bd55yui_3_16_0_ym19_1_1467397914851_28423" dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#808080"><span style="font-size:small">NPOC Chair - NCSG/GNSO<br></span></font></div><div id="m_-6077332719291062321ydpbc80bd55yui_3_16_0_ym19_1_1467397914851_28423" dir="ltr"><span style="font-size:small;color:rgb(128,128,128);font-family:Helvetica,Arial,sans-serif">M.Sc. Information Technology</span><br></div><div id="m_-6077332719291062321ydpbc80bd55yui_3_16_0_ym19_1_1467397914851_28423" dir="ltr"><br></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#808080"><span style="font-size:small"><span><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif" color="#808080" style="background-color:inherit"><span style="font-size:small">Registered Linux User No.<b><span>533108.</span></b></span></font></span><br></span></font></div><div dir="ltr"><a href="http://www.jmanurojas.com" rel="nofollow noreferrer" target="_blank">http://www.jmanurojas.com</a> <br></div><div id="m_-6077332719291062321ydpbc80bd55yui_3_16_0_ym19_1_1467397914851_28423" dir="ltr"><span style="font-size:small"><br></span></div><div id="m_-6077332719291062321ydpbc80bd55yui_3_16_0_ym19_1_1467397914851_28423" dir="ltr"><span style="font-size:small"><font face="Helvetica Neue, Helvetica, Arial, sans-serif" style="background-color:inherit"><i>Cel. +57 301 743 56 00<br>Instagram: jmanurojas</i></font><br id="m_-6077332719291062321ydpbc80bd55yui_3_16_0_ym19_1_1467397914851_29244" style="color:rgb(69,69,69)"></span></div></div><div dir="ltr"><br><div><tt>-----BEGIN GEEK CODE BLOCK-----<br>
Version: 3.1<br>
GIT d- s: a+ C+++ UL P+ L+++ !E !W+++ !N !o K+++ w-- !O M- V PS+ PE-- Y+
PGP+ t+ 5 X++ R tv+ b+ DI D G e+++(+++)>+++ h+ r++ y+
<br>
------END GEEK CODE BLOCK------
</tt></div><div><br></div></div><div style="font-size:13px;font-family:arial,helvetica,clean,sans-serif"><br><br><br><br></div> </div></div></div>
<div><br></div><div><br></div>
</div><div id="m_-6077332719291062321yahoo_quoted_7694236663">
<div style="font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;color:#26282a">
<div>
El sábado, 1 de junio de 2024, 06:07:16 a. m. GMT-5, Johan Helsingius via NCSG-PC <<a href="mailto:ncsg-pc@lists.ncsg.is" target="_blank" rel="noreferrer">ncsg-pc@lists.ncsg.is</a>> escribió:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr"> From Greg: Hi All- fixing small typo below. Feedback is requested by<br clear="none">Council leadership no later than 5 June 2024 (not 31 May).<br clear="none"><br clear="none"> Julf<br clear="none"><br clear="none">On 01/06/2024 12:30, Stephanie E Perrin via NCSG-PC wrote:<br clear="none">> Well they sure didnt give us long to think about that one....<br clear="none">> <br clear="none">> Seems ok in our case.<br clear="none">> <br clear="none">> cheers SP<br clear="none">> <br clear="none">> On 2024-05-31 1:56 pm, Johan Helsingius via NCSG-PC wrote:<br clear="none">>><br clear="none">>><br clear="none">>><br clear="none">>> -------- Forwarded Message --------<br clear="none">>> Subject: NomCom changes<br clear="none">>> Date: Fri, 31 May 2024 14:41:19 +0000<br clear="none">>> From: DiBiase, Gregory <<a shape="rect" href="mailto:dibiase@amazon.com" target="_blank" rel="noreferrer">dibiase@amazon.com</a>><br clear="none">>> To: <a shape="rect" href="mailto:aheineman@godaddy.com" target="_blank" rel="noreferrer">aheineman@godaddy.com</a> <<a shape="rect" href="mailto:aheineman@godaddy.com" target="_blank" rel="noreferrer">aheineman@godaddy.com</a>>, Lori Schulman <br clear="none">>> <<a shape="rect" href="mailto:lschulman@inta.org" target="_blank" rel="noreferrer">lschulman@inta.org</a>>, Cole, Mason (POR) <<a shape="rect" href="mailto:MCole@perkinscoie.com" target="_blank" rel="noreferrer">MCole@perkinscoie.com</a>>, Johan <br clear="none">>> Helsingius <<a shape="rect" href="mailto:julf@Julf.com" target="_blank" rel="noreferrer">julf@Julf.com</a>>, <a shape="rect" href="mailto:sdemetriou@verisign.com" target="_blank" rel="noreferrer">sdemetriou@verisign.com</a> <br clear="none">>> <<a shape="rect" href="mailto:sdemetriou@verisign.com" target="_blank" rel="noreferrer">sdemetriou@verisign.com</a>>, <a shape="rect" href="mailto:philippe.fouquart@orange.com" target="_blank" rel="noreferrer">philippe.fouquart@orange.com</a> <br clear="none">>> <<a shape="rect" href="mailto:philippe.fouquart@orange.com" target="_blank" rel="noreferrer">philippe.fouquart@orange.com</a>><br clear="none">>> CC: Steve Chan <<a shape="rect" href="mailto:steve.chan@icann.org" target="_blank" rel="noreferrer">steve.chan@icann.org</a>>, <a shape="rect" href="mailto:gnso-secs@icann.org" target="_blank" rel="noreferrer">gnso-secs@icann.org</a> <br clear="none">>> <<a shape="rect" href="mailto:gnso-secs@icann.org" target="_blank" rel="noreferrer">gnso-secs@icann.org</a>><br clear="none">>><br clear="none">>><br clear="none">>><br clear="none">>> Dear Ashley, Julf, Lori, Mason, Philippe, and Samantha,<br clear="none">>><br clear="none">>> I am writing to you all in your roles as Chairs of Stakeholder Groups <br clear="none">>> or Constituencies that appoint delegates to ICANN’s Nominating <br clear="none">>> Committee (NomCom).<br clear="none">>><br clear="none">>> You may recall that the NomCom2 Review produced 27 recommendations, <br clear="none">>> several of which relate to the composition and terms of the NomCom. In <br clear="none">>> order to effectuate these particular recommendations, the ICANN Board <br clear="none">>> approved Standard Bylaws Amendments in Articles 8, 12, and 27.<br clear="none">>><br clear="none">>> The Bylaws amendments made no change to the number and nature of <br clear="none">>> delegates from the GNSO (i.e., 1 each from the RySG, RrSG, ISPCP, IPC, <br clear="none">>> NCSG, and 2 from the BC), though the length of terms were extended to <br clear="none">>> two years (see Section 8.3 of the Bylaws). However, from Article 27, <br clear="none">>> in order to, “effectuate the introduction of the two-year terms and <br clear="none">>> support the goal of staggering delegate terms…”, three of the GNSO <br clear="none">>> delegates shall serve a one-year term. ARTICLE 27 TRANSITION ARTICLE <br clear="none">>> states that the GNSO is responsible for determining which three of the <br clear="none">>> seven delegates shall initially serve one-year terms.<br clear="none">>><br clear="none">>> Unfortunately, no guidance was provided on how to identify the three <br clear="none">>> of seven GNSO delegates to serve one-year terms. For reference, the <br clear="none">>> ALAC was also in the position of having to identify a subset of <br clear="none">>> delegates to serve one-year terms. They elected to rely on random <br clear="none">>> selection during a live call.<br clear="none">>><br clear="none">>> The GNSO may want to rely on a similarly simple approach. An important <br clear="none">>> point in considering the approach is that the level of representation <br clear="none">>> on the NomCom is not affected by the term-length. However, the SG/Cs <br clear="none">>> with one-year terms will have to replace those delegates after one <br clear="none">>> year rather than two.<br clear="none">>><br clear="none">>> *Question: Do you believe there would be any objections from your <br clear="none">>> groups, and potentially delegates that you have already identified, to <br clear="none">>> proceeding with a simple path forward in which we randomly select <br clear="none">>> three of seven GNSO delegates to serve one-year terms?*<br clear="none">>><br clear="none">>> If you believe that there may be concerns (e.g., we may want to avoid <br clear="none">>> having the one-year terms concentrated in particular areas), please <br clear="none">>> share them with Council leadership no later than 31 May 2024.<br clear="none">>><br clear="none">>> If however there are no concerns, Council leadership can perform the <br clear="none">>> random selection process with staff or if you prefer, on a Zoom call <br clear="none">>> with all of you.<br clear="none">>><br clear="none">>> Thanks,<br clear="none">>><br clear="none">>> Greg DiBiase, GNSO Chair<br clear="none">>><br clear="none">>> _______________________________________________<br clear="none">>> NCSG-PC mailing list<br clear="none">>> <a shape="rect" href="mailto:NCSG-PC@lists.ncsg.is" target="_blank" rel="noreferrer">NCSG-PC@lists.ncsg.is</a><br clear="none">>> <a shape="rect" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" target="_blank" rel="noreferrer">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><div id="m_-6077332719291062321yqtfd28050"><br clear="none">> _______________________________________________<br clear="none">> NCSG-PC mailing list<br clear="none">> <a shape="rect" href="mailto:NCSG-PC@lists.ncsg.is" target="_blank" rel="noreferrer">NCSG-PC@lists.ncsg.is</a><br clear="none">> <a shape="rect" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" target="_blank" rel="noreferrer">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br clear="none">_______________________________________________<br clear="none">NCSG-PC mailing list<br clear="none"><a shape="rect" href="mailto:NCSG-PC@lists.ncsg.is" target="_blank" rel="noreferrer">NCSG-PC@lists.ncsg.is</a><br clear="none"><a shape="rect" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" target="_blank" rel="noreferrer">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br clear="none"></div></div></div>
</div>
</div></div>_______________________________________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank" rel="noreferrer">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br>
</blockquote></div>