[NCUC-EC] NomCom changes
Hfaiedh Ines
hfaiedh.ines2 at gmail.com
Wed Jun 5 11:08:03 CEST 2024
Hi Julf
Regarding membership I reached out to staff and here s the answer
Hello Ines,
Thank you for reaching out - the work of the NomCom Review Implementation
Working Group (NomComRIWG) completed in June 2022, with the submission of
the final report
<https://www.icann.org/en/system/files/files/nomcom2-review-final-report-30jun22-en.pdf>
. The ICANN Board took action on 16 March 2023
<https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-16-03-2023-en#section2.b>
to accept the status of the NomCom2 Review implementation and initiate an
ICANN Bylaws Amendment process. On 10 September 2023
<https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-10-09-2023-en#section2.b>
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.
Thank you again for reaching out.
Basically the nomcom review team finshed their work in June 2022 so exactly
two years ago.
To answer your question on NCSG or NCUC I attached the final report where
there is no mention of either. So we are speaking here of a board
resolution and my understanding is that they are leaving the floor open to
all constituencies to decide on how to proceed.
On Tue, Jun 4, 2024, 21:31 Benjamin Akinmoyeje <benakin at gmail.com> wrote:
> I got your email. It was just that the GNSO chair , did not copy NCUC
> chair.
>
>
> That it is worthwhile noting for future, although in his email he made
> references to stakeholder group an constituencies.
>
> I hope you see my point.
>
> Kind regards,
> Benjamin
>
>
>
>
> On Tue, Jun 4, 2024, 9:35 PM Johan Helsingius <julf at julf.com> wrote:
>
>> I did copy ncuc-ec, assuming the chair would be part of it.
>>
>> Julf
>>
>> On 04/06/2024 18:59, Benjamin Akinmoyeje wrote:
>> > Hi Julf,
>> > Thank you for this email....but it is strange that the GNSO chair has
>> > chosen not to copy the NCUC Chair in this email.
>> >
>> > NCUC appointed Pascal, our current Nomcom representative if I am
>> correct.
>> >
>> > It would be great if the GNSO chair could be pointed to this omission.
>> >
>> > Just checking if things have changed.
>> >
>> >
>> > Kind regards,
>> > Benjamin
>> >
>> > On Sat, Jun 1, 2024 at 9:32 AM Johan Helsingius <julf at julf.com
>> > <mailto:julf at julf.com>> wrote:
>> >
>> >
>> >
>> >
>> > -------- Forwarded Message --------
>> > Subject: NomCom changes
>> > Date: Fri, 31 May 2024 14:41:19 +0000
>> > From: DiBiase, Gregory <dibiase at amazon.com
>> > <mailto:dibiase at amazon.com>>
>> > To: aheineman at godaddy.com <mailto:aheineman at godaddy.com>
>> > <aheineman at godaddy.com <mailto:aheineman at godaddy.com>>, Lori
>> Schulman
>> > <lschulman at inta.org <mailto:lschulman at inta.org>>, Cole, Mason (POR)
>> > <MCole at perkinscoie.com <mailto:MCole at perkinscoie.com>>, Johan
>> > Helsingius <julf at Julf.com>, sdemetriou at verisign.com
>> > <mailto:sdemetriou at verisign.com>
>> > <sdemetriou at verisign.com <mailto:sdemetriou at verisign.com>>,
>> > philippe.fouquart at orange.com <mailto:philippe.fouquart at orange.com>
>> > <philippe.fouquart at orange.com <mailto:philippe.fouquart at orange.com
>> >>
>> > CC: Steve Chan <steve.chan at icann.org
>> > <mailto:steve.chan at icann.org>>, gnso-secs at icann.org
>> > <mailto:gnso-secs at icann.org>
>> > <gnso-secs at icann.org <mailto:gnso-secs at icann.org>>
>> >
>> >
>> >
>> > Dear Ashley, Julf, Lori, Mason, Philippe, and Samantha,
>> >
>> > I am writing to you all in your roles as Chairs of Stakeholder
>> > Groups or
>> > Constituencies that appoint delegates to ICANN’s Nominating
>> Committee
>> > (NomCom).
>> >
>> > You may recall that the NomCom2 Review produced 27 recommendations,
>> > several of which relate to the composition and terms of the NomCom.
>> In
>> > order to effectuate these particular recommendations, the ICANN
>> Board
>> > approved Standard Bylaws Amendments in Articles 8, 12, and 27.
>> >
>> > The Bylaws amendments made no change to the number and nature of
>> > delegates from the GNSO (i.e., 1 each from the RySG, RrSG, ISPCP,
>> IPC,
>> > NCSG, and 2 from the BC), though the length of terms were extended
>> to
>> > two years (see Section 8.3 of the Bylaws). However, from Article
>> 27, in
>> > order to, “effectuate the introduction of the two-year terms and
>> > support
>> > the goal of staggering delegate terms…”, three of the GNSO delegates
>> > shall serve a one-year term. ARTICLE 27 TRANSITION ARTICLE states
>> that
>> > the GNSO is responsible for determining which three of the seven
>> > delegates shall initially serve one-year terms.
>> >
>> > Unfortunately, no guidance was provided on how to identify the
>> three of
>> > seven GNSO delegates to serve one-year terms. For reference, the
>> ALAC
>> > was also in the position of having to identify a subset of
>> delegates to
>> > serve one-year terms. They elected to rely on random selection
>> during a
>> > live call.
>> >
>> > The GNSO may want to rely on a similarly simple approach. An
>> important
>> > point in considering the approach is that the level of
>> > representation on
>> > the NomCom is not affected by the term-length. However, the SG/Cs
>> with
>> > one-year terms will have to replace those delegates after one year
>> > rather than two.
>> >
>> > *Question: Do you believe there would be any objections from your
>> > groups, and potentially delegates that you have already identified,
>> to
>> > proceeding with a simple path forward in which we randomly select
>> three
>> > of seven GNSO delegates to serve one-year terms?*
>> >
>> > If you believe that there may be concerns (e.g., we may want to
>> avoid
>> > having the one-year terms concentrated in particular areas), please
>> > share them with Council leadership no later than 31 May 2024.
>> >
>> > If however there are no concerns, Council leadership can perform the
>> > random selection process with staff or if you prefer, on a Zoom call
>> > with all of you.
>> >
>> > Thanks,
>> >
>> > Greg DiBiase, GNSO Chair
>> >
>>
> _______________________________________________
> NCUC-EC mailing list
> NCUC-EC at lists.ncuc.org
> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-ec/attachments/20240605/e29b358c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nomcom2-review-final-report-30jun22-en.pdf
Type: application/pdf
Size: 223367 bytes
Desc: not available
URL: <http://lists.ncuc.org/pipermail/ncuc-ec/attachments/20240605/e29b358c/attachment-0001.pdf>
More information about the NCUC-EC
mailing list