[NCSG-PC] Fwd: NomCom changes

Johan Helsingius julf at julf.com
Sat Jun 1 14:07:05 EEST 2024


 From Greg: Hi All- fixing small typo below.  Feedback is requested by
Council leadership no later than 5 June 2024 (not 31 May).

	Julf

On 01/06/2024 12:30, Stephanie E Perrin via NCSG-PC wrote:
> Well they sure didnt give us long to think about that one....
> 
> Seems ok in our case.
> 
> cheers SP
> 
> On 2024-05-31 1:56 pm, Johan Helsingius via NCSG-PC wrote:
>>
>>
>>
>> -------- Forwarded Message --------
>> Subject:     NomCom changes
>> Date:     Fri, 31 May 2024 14:41:19 +0000
>> From:     DiBiase, Gregory <dibiase at amazon.com>
>> To:     aheineman at godaddy.com <aheineman at godaddy.com>, Lori Schulman 
>> <lschulman at inta.org>, Cole, Mason (POR) <MCole at perkinscoie.com>, Johan 
>> Helsingius <julf at Julf.com>, sdemetriou at verisign.com 
>> <sdemetriou at verisign.com>, philippe.fouquart at orange.com 
>> <philippe.fouquart at orange.com>
>> CC:     Steve Chan <steve.chan at icann.org>, gnso-secs at icann.org 
>> <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
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc


More information about the NCSG-PC mailing list