[NCUC-EC] NomCom changes

[Johan Helsingius]

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
>