[NCSG-PC] [council] Supporting Document for November Council Meeting Agenda Item 4: Revised GNSO Councilor Job Description for the Nominating Committee

Stephanie E Perrin stephanie at digitaldiscretion.ca
Thu Nov 18 00:21:27 EET 2021

Thanks Steve, I was doing markup on the redline version, but apparently 
the changes dont show clearly.  I have copy pasted it below, but you 
have captured the sense of it.


The NomCom is seeking accomplished persons of integrity, objectivity, 
and intelligence with *e**xperience*[SP1] <#_msocom_1>in the 
multistakeholder policymaking process and within the GNSO community. 
While GNSO Council members should have a deep understanding of the GNSO 
structure, existing ICANN consensus policies, and contracts 
between ICANN and registries and registrars, preference will be given to 
candidates with a demonstrable ability to manage the policy development 
process towards the best interests of the entire GNSO community rather 
than solely for a specific GNSO Stakeholder Group or Constituency. 
NomCom appointed members are expected to act with integrity and 
independently. Voting NomCom appointed members are encouraged to engage 
with the Council representatives of their appointed House and all NomCom 
appointed member are encouraged to engage with the GNSO community more 
broadly, [SP2] <#_msocom_2>to understand their concerns and views, so 
that the NomCom appointee may be an informed and effective councilor.

NomCom appointed members who are affiliated with an ICANN community 
group at the time of application are not meant to represent their 
current or previously affiliated group and are expected to observe the 
principles and intent of the ICANN’s Conflicts of Interest Policy.


[SP1] <#_msoanchor_1>NCSG rejects the word “ experience” and “within the 
GNSO community.”Already we have an issue with burnout of existing 
members, and a “revolving door” of the same people running for office, 
year after year.We need fresh eyes on our work, to ensure that there is 
no capture by a small group of stakeholders.Please revert to previous 

[SP2] <#_msoanchor_2>With respect to the language that has been deleted 
here, starting with “balance the interests” and ending with their 
appointed House”, please revert and return this important language.WE 
want neutrality on the part of Nomcom appointees, and fresh eyes…in the 
event that Nomcom selects members who have been active in the 
stakeholder community at ICANN already, we absolutely need to emphasis 
the need for neutrality and non-representation on the part of their 
previous or current constituency.Repetition in the new paragraph below 
is fine, we cannot over-emphasize the importance of this aspect of the role.

On 2021-11-17 4:45 p.m., Steve Chan wrote:
> Dear Stephanie,
> It took me a moment to see what you were suggesting, as I saw no 
> redlines. I’ve since seen your comment in the Word doc and thought it 
> might be helpful to make clear what specific change you are 
> suggesting. For the first sentence under Job Description:
>   * /As currently shared/: The NomCom is seeking accomplished persons
>     of integrity, objectivity, and intelligence *with experience* in
>     the multistakeholder policymaking process *and within the GNSO
>     community*.
>   * /Suggested change, which reverts to previous language/: The NomCom
>     is seeking accomplished persons of integrity, objectivity, and
>     intelligence with *an interest* in the multistakeholder
>     policymaking process.
> I have tried to highlight the difference between the two versions by 
> bolding the relevant elements, and hope Councilors find this helpful.
> Best,
> Steve
> *From: *council <council-bounces at gnso.icann.org> on behalf of 
> Stephanie E Perrin via council <council at gnso.icann.org>
> *Reply-To: *Stephanie E Perrin <stephanie.perrin at mail.utoronto.ca>
> *Date: *Wednesday, November 17, 2021 at 10:02 AM
> *To: *"council at gnso.icann.org" <council at gnso.icann.org>
> *Cc: *NCSG PC <ncsg-pc at lists.ncsg.is>
> *Subject: *Re: [council] Supporting Document for November Council 
> Meeting Agenda Item 4: Revised GNSO Councilor Job Description for the 
> Nominating Committee
> Thanks for your hard work on this job description.  NCSG has had a 
> brief discussion on this topic, and believes that we have taken a 
> slight wrong turn in some of the revisions.  We believe that it is 
> important for Nomcom to seek fresh eyes and talent for the Nomcom 
> representatives on Council.  The job description should therefore not 
> insist, as this new version does, on the importance of experience.  
> Understanding of the role of the GNSO, certainly, but experience in 
> the ICANN MS model and its structures is certainly NOT necessary or 
> even desireable.  WE want fresh eyes, different experience and ideas 
> that can help us improve.
> There is obviously an issue if former Councillors start to apply for a 
> Nomcom seat on Council when their terms are up, in terms of upsetting 
> the balance of stakeholder group/constituency representation.  We are 
> not looking for a prohibition of Councillors coming back as Nomcom, 
> just to remove the emphasis on previous GNSO/ICANN experience.
> I hope that I have expressed the views of my SG adequately in these 
> comments and the attached markup, and suggest we have a thorough 
> discussion of this topic in our meeting this week.
> Stephanie Perrin
> On 2021-11-15 8:00 p.m., Steve Chan via council wrote:
>     Dear Councilors,
>     On behalf of the small team (Flip Petillion, Mark Datysgeld, Maxim
>     Alzoba, Olga Cavalli, and Tomslin Samme-Nlar) that worked on the
>     revised NomCom job description, please find their proposed final
>     draft attached in both redline and clean. This version attempts to
>     take into account the initial edits proposed initially by the
>     previous Council leadership team, discussion both on list and
>     during the previous Council call, as well as subsequent email
>     dialogue amongst the small team.
>     Best,
>     Steve
>     *Steven Chan**
>     Senior Director, GNSO Support
>     Internet Corporation for Assigned Names and Numbers (ICANN)
>     12025 Waterfront Drive, Suite 300
>     Los Angeles, CA 90094-2536

>     Email: steve.chan at icann.org <mailto:steve.chan at icann.org>
>     Skype: steve.chan55
>     Mobile: +1.310.339.4410
>     Find out more about the GNSO by visiting: https://learn.icann.org/
>     <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=>
>     Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO
>     <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=>
>     Transcripts and recordings of GNSO Working Group and Council
>     events are located on the GNSO Master
>     Calendar<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e=>
>     _______________________________________________
>     council mailing list
>     council at gnso.icann.org
>     https://mm.icann.org/mailman/listinfo/council
>     _______________________________________________
>     By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20211117/6a27fea9/attachment-0001.htm>

More information about the NCSG-PC mailing list