<div dir="ltr"><div>Hi,</div><div><br></div><div>I also got curious about the whole situation, so I went through transcripts and the wiki. Here is a summary of the last relevant movements, which may be useful for others:</div><div><br></div><div><a href="https://community.icann.org/display/OR/Decisions+Reached+%7C+Action+Items%3A+Tracking+Tool" target="_blank">Decision Reached </a>#87: <br></div><div>
<table style="padding:0px" role="grid"><tbody><tr role="row"><td colspan="1">10</td><td colspan="1"><a href="https://community.icann.org/x/xwEuCg" rel="nofollow" target="_blank">#87</a></td><td colspan="1"><div><p>23/09/2021 </p></div></td><td colspan="1"><p><span style="color:rgb(0,0,0)"><b>The NomComRIWG considered its extensive efforts toward Rec. 10</b>,
noting that their proposed solution provided a streamlined approach as
compared to a more fundamental restructuring of the NomCom. Recognizing
that the GNSO continues to express strong opposition to the NomComRIWG
proposal, rather considering a more fundamental assessment of the NomCom
as more appropriate, the NomComRIWG plans to withdraw its proposed
Bylaws changes on Rec.10 rebalancing. This will help progress the
package of proposed Bylaws changes and other important implementation
work.</span></p></td></tr></tbody></table>
</div><div>There was a Webinar about it in mid-2022 (<a href="https://community.icann.org/display/OR/Decisions+Reached+%7C+Action+Items%3A+Tracking+Tool" target="_blank">Closed Action Items</a>):</div><div><br></div><div>
<table style="width:88.2045%;padding:0px" role="grid"><tbody><tr role="row"><td colspan="1">127</td><td colspan="1"><a href="https://community.icann.org/x/4oH3Cg" rel="nofollow" target="_blank">#92</a></td><td colspan="1"><div><p>10/02/2022 </p></div></td><td colspan="1"><b><a href="https://icann.zoom.us/rec/play/ljUiLGnJAFgDh-ObO9kka40ITzfxuvCAsUvxUv_jNtlhSzRnVJB_8O5FUXTkCjBtgpthLreSnxbWtMs.8ltosWFdyUaM_Pe1?canPlayFromShare=true&from=share_recording_detail&continueMode=true&componentName=rec-play&originRequestUrl=https%3A%2F%2Ficann.zoom.us%2Frec%2Fshare%2FpnqvveOxGt05WU5JqT6W5B7mI5VxuwYtdpkTAEtwOf4VrI0pYsszs76SsDA6zNgZ.GlFYZ6OZlV-WX6_H" target="_blank">ICANN73 Prep Week Webinar</a></b><br>Q&A Slides to be added in between agenda items. <br>Work plan slide to be added under agenda item 6. <br>Additional slide on Rec. 10 to be added. </td><td colspan="1">NomCom Support Staff</td><td colspan="1">NA</td><td colspan="1"><div><p>23/02/2022 </p></div></td><td colspan="1"><div><p>23/02/2022 </p></div></td></tr></tbody></table>
</div><div><br></div><div>Two people from the Non-Commercial were apparently responsible for Rec.10 in <a href="https://community.icann.org/display/OR/Webinar+-+ICANN73+Prep+Week+NomCom+Review+Update+%7C+Thursday%2C+24+February+2022+@+18%3A30+UTC" target="_blank">this Webinar</a> (see 18m20 until 23m51 for a short summary of the reasoning behind the decision), as per the <a href="https://community.icann.org/pages/viewpage.action?pageId=186780719" target="_blank">Feb. 17th meeting</a>, but the record shows Cheryl and Tom doing this part.<br></div><div><br></div><div>Maybe the most relevant explanation is in <a href="https://community.icann.org/pages/viewpage.action?pageId=170787271" target="_blank">the transcripts of the September 23rd Meeting of 2021</a>, where the above-mentioned decision was taken, in which only Remmy participated. Cheryl said some interesting things there (there is a comment from her that looks like a good summary of the whole thing "But because we thought we’d leave the GNSO alone and give it as much absolute autonomy as possible, we went down this particular and obviously failed and faulted pathway"). At that meeting, however, it looks like the doors were already closed because there was resistance from GNSO SGs <i>[it baffles me that the process was planned in such a way that the opinion of those who benefitted from the lack of balance determined the final decision]</i> and the OEC was, for some reason, deeply against this change - this is a topic I think it is useful to dig deeper to better understand what was going on. Another important insight from the transcript is that they were not withdrawing the proposal until the specific below, when Tom, who apparently wanted to proceed with the Recommendation even if it had no chance of going through, had a change of mind after a conversation between Cheryl and Larissa:</div><div><br></div><div style="margin-left:80px">TOM BARRETT: Yes. I understand the optics more—so you’re saying the OEC doesn’t want to make the decision. Absolutely. But we can certainly be open to withdrawing our proposal for Rec 10. I want to know if I speak for everyone. Can I have a thumbs up? Tracy, Jay, Dave, you all agree with that? Cheryl and I do. Okay. All right, so that’s fine. Let’s go ahead and withdraw the bylaw change for Rec 10. It’s just a matter of how we explain our rationale for doing that.</div><div><br></div><div>There were apparently no votes against the withdrawal, but, as far as one can understand from the documentation, the real battle was already lost in the GNSO consultations<br></div><div><br></div><div>However, there were many indications through the documents and webinars that the WG did not believe this ended the debate, so we may keep an eye up for our next window of opportunity. I would already like to volunteer to participate when the moment arrives.<br></div><div><br></div><div>Cordially,<br></div><div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><b>Pedro de Perdigão Lana</b><br></font></font></span><div><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><a href="https://www.nic.br/" target="_blank">Lawyer</a>, </font></font></span><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><a href="https://www.gedai.com.br/" target="_blank">GEDAI/UFPR</a> Researcher</font></font></span></font></font></span></font></font></span></div><div><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2">PhD Candidate (UFPR), LLM in Business Law (UCoimbra)</font></font></span><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"> </font></font></span></font></font></span></div><div><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><span style="font-family:garamond,times new roman,serif"></span></font></font></span></div><div><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2">Board Member @ </font></font></span><span style="font-family:times new roman,serif"><font size="2"><a href="https://www.ncuc.org/" target="_blank">NCUC (ICANN)</a>,</font><font size="1"><font size="2"> </font></font></span><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><a href="https://isoc.org.br/" target="_blank">ISOC BR</a></font></font></span>, </font></font></span><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"><a href="https://br.creativecommons.net/" target="_blank">CC Brasil</a></font></font></span><span style="font-family:garamond,times new roman,serif"><font size="1"><font size="2"> and <a href="https://ioda.org.br/" target="_blank">IODA</a></font></font></span></div><div><span style="font-family:garamond,times new roman,serif"></span></div><div><font size="1"><span style="font-family:garamond,times new roman,serif">This message is restricted to the sender and recipient(s). If received by mistake, please reply informing it.</span></font></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em qua., 5 de jun. de 2024 às 06:41, Johan Helsingius via NCUC-EC <<a href="mailto:ncuc-ec@lists.ncuc.org" target="_blank">ncuc-ec@lists.ncuc.org</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thanks Ines!<br>
<br>
There is a reference to a "transition article" (Article 27) that seems<br>
to be pretty crucial. Do you have any documents describing the<br>
transition article?<br>
<br>
I am also curious about the recommendation 10, "Representation on<br>
the NomCom should be rebalanced immediately and then be reviewed<br>
every 5 years." that was withdrawn. Can you help shed some light<br>
on the discussion that led to the withdrawal of the recommendation?<br>
<br>
Julf<br>
<br>
<br>
On 05/06/2024 11:08, Hfaiedh Ines wrote:<br>
> Hi Julf<br>
> <br>
> Regarding membership I reached out to staff and here s the answer<br>
> <br>
> Hello Ines,<br>
> <br>
> <br>
> Thank you for reaching out - the work of the NomCom Review <br>
> Implementation Working Group (NomComRIWG) completed in June 2022, with <br>
> the submission of the final report <br>
> <<a href="https://www.icann.org/en/system/files/files/nomcom2-review-final-report-30jun22-en.pdf" rel="noreferrer" target="_blank">https://www.icann.org/en/system/files/files/nomcom2-review-final-report-30jun22-en.pdf</a>>. The ICANN Board took action on 16 March 2023 <<a href="https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-16-03-2023-en#section2.b" rel="noreferrer" target="_blank">https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-16-03-2023-en#section2.b</a>>to accept the status of the NomCom2 Review implementation and initiate an ICANN Bylaws Amendment process. On 10 September 2023 <<a href="https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-10-09-2023-en#section2.b" rel="noreferrer" target="_blank">https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-10-09-2023-en#section2.b</a>>the Board took action on next steps in Bylaws Amendment Process. If you would like more information, please feel free to review the NomCom Review workspace or reach out to me for further updates.<br>
> <br>
> <br>
> Thank you again for reaching out.<br>
> <br>
> <br>
> Basically the nomcom review team finshed their work in June 2022 so <br>
> exactly two years ago.<br>
> <br>
> To answer your question on NCSG or NCUC I attached the final report <br>
> where there is no mention of either. So we are speaking here of a board <br>
> resolution and my understanding is that they are leaving the floor open <br>
> to all constituencies to decide on how to proceed.<br>
> <br>
> <br>
> On Tue, Jun 4, 2024, 21:31 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>>> wrote:<br>
> <br>
> I got your email. It was just that the GNSO chair , did not copy<br>
> NCUC chair.<br>
> <br>
> <br>
> That it is worthwhile noting for future, although in his email he<br>
> made references to stakeholder group an constituencies.<br>
> <br>
> I hope you see my point.<br>
> <br>
> Kind regards,<br>
> Benjamin<br>
> <br>
> <br>
> <br>
> <br>
> On Tue, Jun 4, 2024, 9:35 PM Johan Helsingius <<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a><br>
> <mailto:<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a>>> wrote:<br>
> <br>
> 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<br>
> chair has<br>
> > chosen not to copy the NCUC Chair in this email.<br>
> ><br>
> > NCUC appointed Pascal, our current Nomcom representative if I<br>
> am correct.<br>
> ><br>
> > It would be great if the GNSO chair could be pointed to this<br>
> 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<br>
> <<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a> <mailto:<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a>><br>
> > <mailto:<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a> <mailto:<a href="mailto:julf@julf.com" target="_blank">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">dibiase@amazon.com</a><br>
> <mailto:<a href="mailto:dibiase@amazon.com" target="_blank">dibiase@amazon.com</a>><br>
> > <mailto:<a href="mailto:dibiase@amazon.com" target="_blank">dibiase@amazon.com</a> <mailto:<a href="mailto:dibiase@amazon.com" target="_blank">dibiase@amazon.com</a>>>><br>
> > To: <a href="mailto:aheineman@godaddy.com" target="_blank">aheineman@godaddy.com</a> <mailto:<a href="mailto:aheineman@godaddy.com" target="_blank">aheineman@godaddy.com</a>><br>
> <mailto:<a href="mailto:aheineman@godaddy.com" target="_blank">aheineman@godaddy.com</a> <mailto:<a href="mailto:aheineman@godaddy.com" target="_blank">aheineman@godaddy.com</a>>><br>
> > <<a href="mailto:aheineman@godaddy.com" target="_blank">aheineman@godaddy.com</a> <mailto:<a href="mailto:aheineman@godaddy.com" target="_blank">aheineman@godaddy.com</a>><br>
> <mailto:<a href="mailto:aheineman@godaddy.com" target="_blank">aheineman@godaddy.com</a> <mailto:<a href="mailto:aheineman@godaddy.com" target="_blank">aheineman@godaddy.com</a>>>>,<br>
> Lori Schulman<br>
> > <<a href="mailto:lschulman@inta.org" target="_blank">lschulman@inta.org</a> <mailto:<a href="mailto:lschulman@inta.org" target="_blank">lschulman@inta.org</a>><br>
> <mailto:<a href="mailto:lschulman@inta.org" target="_blank">lschulman@inta.org</a> <mailto:<a href="mailto:lschulman@inta.org" target="_blank">lschulman@inta.org</a>>>>, Cole,<br>
> Mason (POR)<br>
> > <<a href="mailto:MCole@perkinscoie.com" target="_blank">MCole@perkinscoie.com</a> <mailto:<a href="mailto:MCole@perkinscoie.com" target="_blank">MCole@perkinscoie.com</a>><br>
> <mailto:<a href="mailto:MCole@perkinscoie.com" target="_blank">MCole@perkinscoie.com</a> <mailto:<a href="mailto:MCole@perkinscoie.com" target="_blank">MCole@perkinscoie.com</a>>>>,<br>
> Johan<br>
> > Helsingius <julf@Julf.com>, <a href="mailto:sdemetriou@verisign.com" target="_blank">sdemetriou@verisign.com</a><br>
> <mailto:<a href="mailto:sdemetriou@verisign.com" target="_blank">sdemetriou@verisign.com</a>><br>
> > <mailto:<a href="mailto:sdemetriou@verisign.com" target="_blank">sdemetriou@verisign.com</a><br>
> <mailto:<a href="mailto:sdemetriou@verisign.com" target="_blank">sdemetriou@verisign.com</a>>><br>
> > <<a href="mailto:sdemetriou@verisign.com" target="_blank">sdemetriou@verisign.com</a> <mailto:<a href="mailto:sdemetriou@verisign.com" target="_blank">sdemetriou@verisign.com</a>><br>
> <mailto:<a href="mailto:sdemetriou@verisign.com" target="_blank">sdemetriou@verisign.com</a> <mailto:<a href="mailto:sdemetriou@verisign.com" target="_blank">sdemetriou@verisign.com</a>>>>,<br>
> > <a href="mailto:philippe.fouquart@orange.com" target="_blank">philippe.fouquart@orange.com</a><br>
> <mailto:<a href="mailto:philippe.fouquart@orange.com" target="_blank">philippe.fouquart@orange.com</a>><br>
> <mailto:<a href="mailto:philippe.fouquart@orange.com" target="_blank">philippe.fouquart@orange.com</a><br>
> <mailto:<a href="mailto:philippe.fouquart@orange.com" target="_blank">philippe.fouquart@orange.com</a>>><br>
> > <<a href="mailto:philippe.fouquart@orange.com" target="_blank">philippe.fouquart@orange.com</a><br>
> <mailto:<a href="mailto:philippe.fouquart@orange.com" target="_blank">philippe.fouquart@orange.com</a>><br>
> <mailto:<a href="mailto:philippe.fouquart@orange.com" target="_blank">philippe.fouquart@orange.com</a><br>
> <mailto:<a href="mailto:philippe.fouquart@orange.com" target="_blank">philippe.fouquart@orange.com</a>>>><br>
> > CC: Steve Chan <<a href="mailto:steve.chan@icann.org" target="_blank">steve.chan@icann.org</a><br>
> <mailto:<a href="mailto:steve.chan@icann.org" target="_blank">steve.chan@icann.org</a>><br>
> > <mailto:<a href="mailto:steve.chan@icann.org" target="_blank">steve.chan@icann.org</a><br>
> <mailto:<a href="mailto:steve.chan@icann.org" target="_blank">steve.chan@icann.org</a>>>>, <a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a><br>
> <mailto:<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>><br>
> > <mailto:<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a> <mailto:<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>>><br>
> > <<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a> <mailto:<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>><br>
> <mailto:<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a> <mailto:<a href="mailto:gnso-secs@icann.org" target="_blank">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<br>
> Stakeholder<br>
> > Groups or<br>
> > Constituencies that appoint delegates to ICANN’s<br>
> Nominating Committee<br>
> > (NomCom).<br>
> ><br>
> > You may recall that the NomCom2 Review produced 27<br>
> recommendations,<br>
> > several of which relate to the composition and terms of<br>
> the NomCom. In<br>
> > order to effectuate these particular recommendations, the<br>
> ICANN Board<br>
> > approved Standard Bylaws Amendments in Articles 8, 12,<br>
> and 27.<br>
> ><br>
> > The Bylaws amendments made no change to the number and<br>
> nature of<br>
> > delegates from the GNSO (i.e., 1 each from the RySG,<br>
> RrSG, ISPCP, IPC,<br>
> > NCSG, and 2 from the BC), though the length of terms were<br>
> extended to<br>
> > two years (see Section 8.3 of the Bylaws). However, from<br>
> Article 27, in<br>
> > order to, “effectuate the introduction of the two-year<br>
> terms and<br>
> > support<br>
> > the goal of staggering delegate terms…”, three of the<br>
> GNSO delegates<br>
> > shall serve a one-year term. ARTICLE 27 TRANSITION<br>
> ARTICLE states that<br>
> > the GNSO is responsible for determining which three of<br>
> the seven<br>
> > delegates shall initially serve one-year terms.<br>
> ><br>
> > Unfortunately, no guidance was provided on how to<br>
> identify the three of<br>
> > seven GNSO delegates to serve one-year terms. For<br>
> reference, the ALAC<br>
> > was also in the position of having to identify a subset<br>
> of delegates to<br>
> > serve one-year terms. They elected to rely on random<br>
> selection during a<br>
> > live call.<br>
> ><br>
> > The GNSO may want to rely on a similarly simple approach.<br>
> 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,<br>
> the SG/Cs with<br>
> > one-year terms will have to replace those delegates after<br>
> one year<br>
> > rather than two.<br>
> ><br>
> > *Question: Do you believe there would be any objections<br>
> from your<br>
> > groups, and potentially delegates that you have already<br>
> identified, to<br>
> > proceeding with a simple path forward in which we<br>
> 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<br>
> want to avoid<br>
> > having the one-year terms concentrated in particular<br>
> 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<br>
> perform the<br>
> > random selection process with staff or if you prefer, on<br>
> a Zoom call<br>
> > with all of you.<br>
> ><br>
> > Thanks,<br>
> ><br>
> > Greg DiBiase, GNSO Chair<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>
_______________________________________________<br>
NCUC-EC mailing list<br>
<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>
</blockquote></div>