Nominating Committee Criteria for Appointing GNSO Councilors

Dear Councilors, The GNSO Council was invited to review the position description that the ICANN Nominating Committee uses in order to fulfill its appointments to the GNSO Council. You can find the position description for the 2020 cycle here: https://www.icann.org/resources/pages/nomcom2020-positions-2020-01-13-en#gns.... The position description is of course an important piece of guidance for the NomCom, to ensure that it appoints GNSO Councilors that will succeed in their role. Staff, in coordination with Council leadership, has taken that existing description and dropped it into a Google document, where it has undergone some preliminary redlines. A fair amount of those edits are mostly structural, to have the position description look more like a job description (e.g., separating out criteria and skillset and also separating out job responsibilities and time commitment). You can find that redline here, where you are invited to add in your own suggested edits: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCEy.... The target date to receive and integrate feedback as appropriate is early January. Finally and most importantly, happy holidays to you all! 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@icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar

Thanks Steve. I like the structural changes and inclusion of 'virtual' to reflect how expectations of the role has and is changing. Cheers, Tomslin On Thu., 24 Dec. 2020, 06:08 Steve Chan, <steve.chan@icann.org> wrote:
Dear Councilors,
The GNSO Council was invited to review the position description that the ICANN Nominating Committee uses in order to fulfill its appointments to the GNSO Council. You can find the position description for the 2020 cycle here: https://www.icann.org/resources/pages/nomcom2020-positions-2020-01-13-en#gns.... The position description is of course an important piece of guidance for the NomCom, to ensure that it appoints GNSO Councilors that will succeed in their role.
Staff, in coordination with Council leadership, has taken that existing description and dropped it into a Google document, where it has undergone some preliminary redlines. A fair amount of those edits are mostly structural, to have the position description look more like a job description (e.g., separating out criteria and skillset and also separating out job responsibilities and time commitment). You can find that redline here, where you are invited to add in your own suggested edits: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCEy....
The target date to receive and integrate feedback as appropriate is early January.
Finally and most importantly, happy holidays to you all!
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@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=DwMG...>
Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNS...>
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...> _______________________________________________ council mailing list council@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.

So far the text looks quite solid. Sincerely Yours, Maxim Alzoba Special projects manager, International Relations Department, FAITID Current UTC offset: +3.00 (.Moscow)
On 28 Dec 2020, at 02:40, Tomslin Samme-Nlar <mesumbeslin@gmail.com> wrote:
Thanks Steve.
I like the structural changes and inclusion of 'virtual' to reflect how expectations of the role has and is changing.
Cheers, Tomslin
On Thu., 24 Dec. 2020, 06:08 Steve Chan, <steve.chan@icann.org <mailto:steve.chan@icann.org>> wrote: Dear Councilors,
The GNSO Council was invited to review the position description that the ICANN Nominating Committee uses in order to fulfill its appointments to the GNSO Council. You can find the position description for the 2020 cycle here: https://www.icann.org/resources/pages/nomcom2020-positions-2020-01-13-en#gns... <https://www.icann.org/resources/pages/nomcom2020-positions-2020-01-13-en#gns...>. The position description is of course an important piece of guidance for the NomCom, to ensure that it appoints GNSO Councilors that will succeed in their role.
Staff, in coordination with Council leadership, has taken that existing description and dropped it into a Google document, where it has undergone some preliminary redlines. A fair amount of those edits are mostly structural, to have the position description look more like a job description (e.g., separating out criteria and skillset and also separating out job responsibilities and time commitment). You can find that redline here, where you are invited to add in your own suggested edits: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCEy... <https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCEy...>.
The target date to receive and integrate feedback as appropriate is early January.
Finally and most importantly, happy holidays to you all!
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@icann.org <mailto:steve.chan@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=DwMG...> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNS...> 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@gnso.icann.org <mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council <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 <https://www.icann.org/privacy/policy>) and the website Terms of Service (https://www.icann.org/privacy/tos <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. _______________________________________________ council mailing list council@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.

Thanks Steve for the good work. The text look good. Happy holidays to you all. On Wed, Dec 23, 2020, 19:08 Steve Chan <steve.chan@icann.org> wrote:
Dear Councilors,
The GNSO Council was invited to review the position description that the ICANN Nominating Committee uses in order to fulfill its appointments to the GNSO Council. You can find the position description for the 2020 cycle here: https://www.icann.org/resources/pages/nomcom2020-positions-2020-01-13-en#gns.... The position description is of course an important piece of guidance for the NomCom, to ensure that it appoints GNSO Councilors that will succeed in their role.
Staff, in coordination with Council leadership, has taken that existing description and dropped it into a Google document, where it has undergone some preliminary redlines. A fair amount of those edits are mostly structural, to have the position description look more like a job description (e.g., separating out criteria and skillset and also separating out job responsibilities and time commitment). You can find that redline here, where you are invited to add in your own suggested edits: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCEy....
The target date to receive and integrate feedback as appropriate is early January.
Finally and most importantly, happy holidays to you all!
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@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=DwMG...>
Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNS...>
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...> _______________________________________________ council mailing list council@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.

Thanks Tomslin, Maxim, and Wisdom for your review and feedback. If any other Councilors would like to review, it would be much appreciated. This criteria is super important in that it sets expectations for potential applicants and also guides the NomCom in its selection process. If I may, I’d like to set a deadline of this Friday, 8 January 2021 for any additional input? Best, Steve From: Wisdom Donkor <wisdom.dk@gmail.com> Date: Monday, December 28, 2020 at 4:14 AM To: Steve Chan <steve.chan@icann.org> Cc: "council@gnso.icann.org" <council@gnso.icann.org> Subject: [Ext] Re: [council] Nominating Committee Criteria for Appointing GNSO Councilors Thanks Steve for the good work. The text look good. Happy holidays to you all. On Wed, Dec 23, 2020, 19:08 Steve Chan <steve.chan@icann.org> wrote: Dear Councilors, The GNSO Council was invited to review the position description that the ICANN Nominating Committee uses in order to fulfill its appointments to the GNSO Council. You can find the position description for the 2020 cycle here: https://www.icann.org/resources/pages/nomcom2020-positions-2020-01-13-en#gns... [icann.org]. The position description is of course an important piece of guidance for the NomCom, to ensure that it appoints GNSO Councilors that will succeed in their role. Staff, in coordination with Council leadership, has taken that existing description and dropped it into a Google document, where it has undergone some preliminary redlines. A fair amount of those edits are mostly structural, to have the position description look more like a job description (e.g., separating out criteria and skillset and also separating out job responsibilities and time commitment). You can find that redline here, where you are invited to add in your own suggested edits: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCEy... [docs.google.com]. The target date to receive and integrate feedback as appropriate is early January. Finally and most importantly, happy holidays to you all! 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@icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar _______________________________________________ council mailing list council@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 [icann.org]) and the website Terms of Service (https://www.icann.org/privacy/tos [icann.org]). 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.

Thank you Steve. I have made some suggestions in the Google Doc. Tom From: council <council-bounces@gnso.icann.org> Date: Thursday, 7 January 2021 at 7:28 am To: Wisdom Donkor <wisdom.dk@gmail.com> Cc: council@gnso.icann.org <council@gnso.icann.org> Subject: Re: [council] [Ext] Re: Nominating Committee Criteria for Appointing GNSO Councilors Thanks Tomslin, Maxim, and Wisdom for your review and feedback. If any other Councilors would like to review, it would be much appreciated. This criteria is super important in that it sets expectations for potential applicants and also guides the NomCom in its selection process. If I may, I’d like to set a deadline of this Friday, 8 January 2021 for any additional input? Best, Steve From: Wisdom Donkor <wisdom.dk@gmail.com> Date: Monday, December 28, 2020 at 4:14 AM To: Steve Chan <steve.chan@icann.org> Cc: "council@gnso.icann.org" <council@gnso.icann.org> Subject: [Ext] Re: [council] Nominating Committee Criteria for Appointing GNSO Councilors Thanks Steve for the good work. The text look good. Happy holidays to you all. On Wed, Dec 23, 2020, 19:08 Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> wrote: Dear Councilors, The GNSO Council was invited to review the position description that the ICANN Nominating Committee uses in order to fulfill its appointments to the GNSO Council. You can find the position description for the 2020 cycle here: https://www.icann.org/resources/pages/nomcom2020-positions-2020-01-13-en#gns... [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/nomcom2020-...>. The position description is of course an important piece of guidance for the NomCom, to ensure that it appoints GNSO Councilors that will succeed in their role. Staff, in coordination with Council leadership, has taken that existing description and dropped it into a Google document, where it has undergone some preliminary redlines. A fair amount of those edits are mostly structural, to have the position description look more like a job description (e.g., separating out criteria and skillset and also separating out job responsibilities and time commitment). You can find that redline here, where you are invited to add in your own suggested edits: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCEy... [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1WzjvntnliTSZ4...>. The target date to receive and integrate feedback as appropriate is early January. Finally and most importantly, happy holidays to you all! 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@icann.org<mailto:steve.chan@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...> _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@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 [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/privacy/policy__;!!PtGJab4!...>) and the website Terms of Service (https://www.icann.org/privacy/tos [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/privacy/tos__;!!PtGJab4!tn7...>). 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.

Hello Steve, I have read the doc and I am quite in ligne with its actual shape. So, I have no particular comment. @__f_f__ Best regards ____________________________________ Farell FOLLY GNSO Councillor linkedin.com/in/farellf
On 6 Jan 2021, at 21:28, Steve Chan <steve.chan@icann.org> wrote:
Thanks Tomslin, Maxim, and Wisdom for your review and feedback.
If any other Councilors would like to review, it would be much appreciated. This criteria is super important in that it sets expectations for potential applicants and also guides the NomCom in its selection process. If I may, I’d like to set a deadline of this Friday, 8 January 2021 for any additional input?
Best, Steve
From: Wisdom Donkor <wisdom.dk@gmail.com <mailto:wisdom.dk@gmail.com>> Date: Monday, December 28, 2020 at 4:14 AM To: Steve Chan <steve.chan@icann.org <mailto:steve.chan@icann.org>> Cc: "council@gnso.icann.org <mailto:council@gnso.icann.org>" <council@gnso.icann.org <mailto:council@gnso.icann.org>> Subject: [Ext] Re: [council] Nominating Committee Criteria for Appointing GNSO Councilors
Thanks Steve for the good work. The text look good.
Happy holidays to you all.
On Wed, Dec 23, 2020, 19:08 Steve Chan <steve.chan@icann.org <mailto:steve.chan@icann.org>> wrote:
Dear Councilors,
The GNSO Council was invited to review the position description that the ICANN Nominating Committee uses in order to fulfill its appointments to the GNSO Council. You can find the position description for the 2020 cycle here: https://www.icann.org/resources/pages/nomcom2020-positions-2020-01-13-en#gns... [icann.org] <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/nomcom2020-...>. The position description is of course an important piece of guidance for the NomCom, to ensure that it appoints GNSO Councilors that will succeed in their role.
Staff, in coordination with Council leadership, has taken that existing description and dropped it into a Google document, where it has undergone some preliminary redlines. A fair amount of those edits are mostly structural, to have the position description look more like a job description (e.g., separating out criteria and skillset and also separating out job responsibilities and time commitment). You can find that redline here, where you are invited to add in your own suggested edits: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCEy... [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/1WzjvntnliTSZ4...>.
The target date to receive and integrate feedback as appropriate is early January.
Finally and most importantly, happy holidays to you all!
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@icann.org <mailto:steve.chan@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=DwMG...> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNS...> 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...> _______________________________________________ council mailing list council@gnso.icann.org <mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council <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 [icann.org] <https://urldefense.com/v3/__https:/www.icann.org/privacy/policy__;!!PtGJab4!...>) and the website Terms of Service (https://www.icann.org/privacy/tos [icann.org] <https://urldefense.com/v3/__https:/www.icann.org/privacy/tos__;!!PtGJab4!tn7...>). 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.
council mailing list council@gnso.icann.org <mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council <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 <https://www.icann.org/privacy/policy>) and the website Terms of Service (https://www.icann.org/privacy/tos <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.

Dear Steve, dear colleagues Happy new year!! Steve I added some text to the shared document. Many thanks and best regards Olga El mié, 23 dic 2020 a las 16:08, Steve Chan (<steve.chan@icann.org>) escribió:
Dear Councilors,
The GNSO Council was invited to review the position description that the ICANN Nominating Committee uses in order to fulfill its appointments to the GNSO Council. You can find the position description for the 2020 cycle here: https://www.icann.org/resources/pages/nomcom2020-positions-2020-01-13-en#gns.... The position description is of course an important piece of guidance for the NomCom, to ensure that it appoints GNSO Councilors that will succeed in their role.
Staff, in coordination with Council leadership, has taken that existing description and dropped it into a Google document, where it has undergone some preliminary redlines. A fair amount of those edits are mostly structural, to have the position description look more like a job description (e.g., separating out criteria and skillset and also separating out job responsibilities and time commitment). You can find that redline here, where you are invited to add in your own suggested edits: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCEy....
The target date to receive and integrate feedback as appropriate is early January.
Finally and most importantly, happy holidays to you all!
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@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=DwMG...>
Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNS...>
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...> _______________________________________________ council mailing list council@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.

Steve, all Many thanks for this and apologies for missing your deadline. If still useful, some points that my former NomCom colleagues have raised: · We have to be conscious that in the past there have been complaints by some NomCom appointees about the volume of work required by the GNSO because they underestimated the responsibilities attached to the role – we need to be sure this is clear upfront. It is important that the GNSO clearly spells out the time requirement for the role so that interested candidates determine if they can volunteer for the required hours. · In this round, the NomCom would be filling both seats for voting appointees in each house of the GNSO, so please note that contrary to the edits in the current GNSO criteria, the voting NCAs, under the GNSO operating principles, are not eligible to become Chair of the Council - only the non-voting NCA can do that, in the event that both houses cannot reach a compromise on who would be Chair. · As the Council's business is conducted in English, it should indeed be a requirement that candidates can converse, write and understand English. Hope this helps! Marie From: council <council-bounces@gnso.icann.org> On Behalf Of Olga Cavalli Sent: Thursday, January 7, 2021 4:35 PM To: Steve Chan <steve.chan@icann.org> Cc: council@gnso.icann.org Subject: Re: [council] Nominating Committee Criteria for Appointing GNSO Councilors Dear Steve, dear colleagues Happy new year!! Steve I added some text to the shared document. Many thanks and best regards Olga El mié, 23 dic 2020 a las 16:08, Steve Chan (<steve.chan@icann.org<mailto:steve.chan@icann.org>>) escribió: Dear Councilors, The GNSO Council was invited to review the position description that the ICANN Nominating Committee uses in order to fulfill its appointments to the GNSO Council. You can find the position description for the 2020 cycle here: https://www.icann.org/resources/pages/nomcom2020-positions-2020-01-13-en#gns.... The position description is of course an important piece of guidance for the NomCom, to ensure that it appoints GNSO Councilors that will succeed in their role. Staff, in coordination with Council leadership, has taken that existing description and dropped it into a Google document, where it has undergone some preliminary redlines. A fair amount of those edits are mostly structural, to have the position description look more like a job description (e.g., separating out criteria and skillset and also separating out job responsibilities and time commitment). You can find that redline here, where you are invited to add in your own suggested edits: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCEy.... The target date to receive and integrate feedback as appropriate is early January. Finally and most importantly, happy holidays to you all! 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@icann.org<mailto:steve.chan@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...> _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@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.

Dear Marie, Thanks for the input. Please see the responses inline to your bullets below, in blue. Please let me know of course if you still have questions, comments or concerns. I will send around a proposed final red-line and clean copy in a bit for non-objection. Best, Steve From: council <council-bounces@gnso.icann.org> on behalf of Marie Pattullo <marie.pattullo@aim.be> Date: Wednesday, January 13, 2021 at 6:32 AM To: "council@gnso.icann.org" <council@gnso.icann.org> Subject: [council] FW: Nominating Committee Criteria for Appointing GNSO Councilors Steve, all Many thanks for this and apologies for missing your deadline. If still useful, some points that my former NomCom colleagues have raised: We have to be conscious that in the past there have been complaints by some NomCom appointees about the volume of work required by the GNSO because they underestimated the responsibilities attached to the role – we need to be sure this is clear upfront. It is important that the GNSO clearly spells out the time requirement for the role so that interested candidates determine if they can volunteer for the required hours. SC: There is some language already in the updated draft that talks about time commitments. If you or others believe that additional guidance is needed, please let me know and it can hopefully be integrated. In this round, the NomCom would be filling both seats for voting appointees in each house of the GNSO, so please note that contrary to the edits in the current GNSO criteria, the voting NCAs, under the GNSO operating principles, are not eligible to become Chair of the Council - only the non-voting NCA can do that, in the event that both houses cannot reach a compromise on who would be Chair. SC: Staff’s reading of the Bylaws and GNSO Operating Procedures is actually a bit different. Section 2.2.b of the GNSO Operating Procedures state that: “Each house will be allowed to nominate one candidate for GNSO Council Chair. Each house is responsible for determining how to nominate its candidate. A candidate for GNSO Council Chair does not need to be a member of a house, but must be a current or incoming member of the GNSO Council. Should a Chair be elected from outside of the houses that Chair will be a non-voting Chair.” And section 11.3.a (v) of the ICANN Bylaws state that: “three representatives selected by the ICANN Nominating Committee, one of which shall be non-voting, but otherwise entitled to participate on equal footing with other members of the GNSO Council including, e.g. the making and seconding of motions and of serving as Chair if elected. One Nominating Committee appointee voting representative shall be assigned to each House (as described in Section 11.3(h)) by the Nominating Committee.” Taken collectively, this seems to indicate that the two voting NomCom appointees, that are assigned to the respective Houses, could be the nominated Chair candidate from a House. The non-voting NCA is also eligible to Chair as you point out and if that were the case, would remain non-voting. As the Council's business is conducted in English, it should indeed be a requirement that candidates can converse, write and understand English. This remains part of the requirements – it was merely shifted underneath “skillset”. Hope this helps! Marie From: council <council-bounces@gnso.icann.org> On Behalf Of Olga Cavalli Sent: Thursday, January 7, 2021 4:35 PM To: Steve Chan <steve.chan@icann.org> Cc: council@gnso.icann.org Subject: Re: [council] Nominating Committee Criteria for Appointing GNSO Councilors Dear Steve, dear colleagues Happy new year!! Steve I added some text to the shared document. Many thanks and best regards Olga El mié, 23 dic 2020 a las 16:08, Steve Chan (<steve.chan@icann.org>) escribió: Dear Councilors, The GNSO Council was invited to review the position description that the ICANN Nominating Committee uses in order to fulfill its appointments to the GNSO Council. You can find the position description for the 2020 cycle here: https://www.icann.org/resources/pages/nomcom2020-positions-2020-01-13-en#gns... [icann.org]. The position description is of course an important piece of guidance for the NomCom, to ensure that it appoints GNSO Councilors that will succeed in their role. Staff, in coordination with Council leadership, has taken that existing description and dropped it into a Google document, where it has undergone some preliminary redlines. A fair amount of those edits are mostly structural, to have the position description look more like a job description (e.g., separating out criteria and skillset and also separating out job responsibilities and time commitment). You can find that redline here, where you are invited to add in your own suggested edits: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCEy... [docs.google.com]. The target date to receive and integrate feedback as appropriate is early January. Finally and most importantly, happy holidays to you all! 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@icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar _______________________________________________ council mailing list council@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 [icann.org]) and the website Terms of Service (https://www.icann.org/privacy/tos [icann.org]). 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.

Dear Councilors, It took a bit longer than expected to integrate the feedback from Councilors. Attached, you can find the latest redline that has suggested edits from me and all of you. Also attached, you can find a proposed clean copy that accepts nearly all of those redlines. However, there is one section of text in the clean version that I would like to draw your attention to however. Jeff had suggested some additional text about how NomCom appointed Councilors should engage as a Councilor, emphasizing that they should act independently. You can get the context of his suggestions and my suggested text in a comment in the redline and that same proposed text from me, incorporated into the clean version and highlighted in yellow. I know this might seem a bit overcomplicated, so apologies in advance – please let me know if you have any questions. Please review and provide any comments at your earliest convenience. As I understand it, the NomCom is expected to launch their invitation process quite soon, though I think this text can actually be incorporated into their process even after its launch. Best, Steve From: council <council-bounces@gnso.icann.org> on behalf of Steve Chan <steve.chan@icann.org> Date: Wednesday, January 13, 2021 at 1:50 PM To: Marie Pattullo <marie.pattullo@aim.be>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] FW: Nominating Committee Criteria for Appointing GNSO Councilors Dear Marie, Thanks for the input. Please see the responses inline to your bullets below, in blue. Please let me know of course if you still have questions, comments or concerns. I will send around a proposed final red-line and clean copy in a bit for non-objection. Best, Steve From: council <council-bounces@gnso.icann.org> on behalf of Marie Pattullo <marie.pattullo@aim.be> Date: Wednesday, January 13, 2021 at 6:32 AM To: "council@gnso.icann.org" <council@gnso.icann.org> Subject: [council] FW: Nominating Committee Criteria for Appointing GNSO Councilors Steve, all Many thanks for this and apologies for missing your deadline. If still useful, some points that my former NomCom colleagues have raised: We have to be conscious that in the past there have been complaints by some NomCom appointees about the volume of work required by the GNSO because they underestimated the responsibilities attached to the role – we need to be sure this is clear upfront. It is important that the GNSO clearly spells out the time requirement for the role so that interested candidates determine if they can volunteer for the required hours. SC: There is some language already in the updated draft that talks about time commitments. If you or others believe that additional guidance is needed, please let me know and it can hopefully be integrated. In this round, the NomCom would be filling both seats for voting appointees in each house of the GNSO, so please note that contrary to the edits in the current GNSO criteria, the voting NCAs, under the GNSO operating principles, are not eligible to become Chair of the Council - only the non-voting NCA can do that, in the event that both houses cannot reach a compromise on who would be Chair. SC: Staff’s reading of the Bylaws and GNSO Operating Procedures is actually a bit different. Section 2.2.b of the GNSO Operating Procedures state that: “Each house will be allowed to nominate one candidate for GNSO Council Chair. Each house is responsible for determining how to nominate its candidate. A candidate for GNSO Council Chair does not need to be a member of a house, but must be a current or incoming member of the GNSO Council. Should a Chair be elected from outside of the houses that Chair will be a non-voting Chair.” And section 11.3.a (v) of the ICANN Bylaws state that: “three representatives selected by the ICANN Nominating Committee, one of which shall be non-voting, but otherwise entitled to participate on equal footing with other members of the GNSO Council including, e.g. the making and seconding of motions and of serving as Chair if elected. One Nominating Committee appointee voting representative shall be assigned to each House (as described in Section 11.3(h)) by the Nominating Committee.” Taken collectively, this seems to indicate that the two voting NomCom appointees, that are assigned to the respective Houses, could be the nominated Chair candidate from a House. The non-voting NCA is also eligible to Chair as you point out and if that were the case, would remain non-voting. As the Council's business is conducted in English, it should indeed be a requirement that candidates can converse, write and understand English. This remains part of the requirements – it was merely shifted underneath “skillset”. Hope this helps! Marie From: council <council-bounces@gnso.icann.org> On Behalf Of Olga Cavalli Sent: Thursday, January 7, 2021 4:35 PM To: Steve Chan <steve.chan@icann.org> Cc: council@gnso.icann.org Subject: Re: [council] Nominating Committee Criteria for Appointing GNSO Councilors Dear Steve, dear colleagues Happy new year!! Steve I added some text to the shared document. Many thanks and best regards Olga El mié, 23 dic 2020 a las 16:08, Steve Chan (<steve.chan@icann.org>) escribió: Dear Councilors, The GNSO Council was invited to review the position description that the ICANN Nominating Committee uses in order to fulfill its appointments to the GNSO Council. You can find the position description for the 2020 cycle here: https://www.icann.org/resources/pages/nomcom2020-positions-2020-01-13-en#gns... [icann.org]. The position description is of course an important piece of guidance for the NomCom, to ensure that it appoints GNSO Councilors that will succeed in their role. Staff, in coordination with Council leadership, has taken that existing description and dropped it into a Google document, where it has undergone some preliminary redlines. A fair amount of those edits are mostly structural, to have the position description look more like a job description (e.g., separating out criteria and skillset and also separating out job responsibilities and time commitment). You can find that redline here, where you are invited to add in your own suggested edits: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCEy... [docs.google.com]. The target date to receive and integrate feedback as appropriate is early January. Finally and most importantly, happy holidays to you all! 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@icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar _______________________________________________ council mailing list council@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 [icann.org]) and the website Terms of Service (https://www.icann.org/privacy/tos [icann.org]). 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.

Dear Councilors, To add to my message below, and in an effort to try and close out this topic in a timely manner, I’d like to see if the document can be agreed to via non-objection, by 23:59 UTC on Wednesday, 27 January 2021. Best, Steve From: council <council-bounces@gnso.icann.org> on behalf of Steve Chan <steve.chan@icann.org> Date: Friday, January 22, 2021 at 2:19 PM To: Marie Pattullo <marie.pattullo@aim.be>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] FW: Nominating Committee Criteria for Appointing GNSO Councilors Dear Councilors, It took a bit longer than expected to integrate the feedback from Councilors. Attached, you can find the latest redline that has suggested edits from me and all of you. Also attached, you can find a proposed clean copy that accepts nearly all of those redlines. However, there is one section of text in the clean version that I would like to draw your attention to however. Jeff had suggested some additional text about how NomCom appointed Councilors should engage as a Councilor, emphasizing that they should act independently. You can get the context of his suggestions and my suggested text in a comment in the redline and that same proposed text from me, incorporated into the clean version and highlighted in yellow. I know this might seem a bit overcomplicated, so apologies in advance – please let me know if you have any questions. Please review and provide any comments at your earliest convenience. As I understand it, the NomCom is expected to launch their invitation process quite soon, though I think this text can actually be incorporated into their process even after its launch. Best, Steve From: council <council-bounces@gnso.icann.org> on behalf of Steve Chan <steve.chan@icann.org> Date: Wednesday, January 13, 2021 at 1:50 PM To: Marie Pattullo <marie.pattullo@aim.be>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] FW: Nominating Committee Criteria for Appointing GNSO Councilors Dear Marie, Thanks for the input. Please see the responses inline to your bullets below, in blue. Please let me know of course if you still have questions, comments or concerns. I will send around a proposed final red-line and clean copy in a bit for non-objection. Best, Steve From: council <council-bounces@gnso.icann.org> on behalf of Marie Pattullo <marie.pattullo@aim.be> Date: Wednesday, January 13, 2021 at 6:32 AM To: "council@gnso.icann.org" <council@gnso.icann.org> Subject: [council] FW: Nominating Committee Criteria for Appointing GNSO Councilors Steve, all Many thanks for this and apologies for missing your deadline. If still useful, some points that my former NomCom colleagues have raised: We have to be conscious that in the past there have been complaints by some NomCom appointees about the volume of work required by the GNSO because they underestimated the responsibilities attached to the role – we need to be sure this is clear upfront. It is important that the GNSO clearly spells out the time requirement for the role so that interested candidates determine if they can volunteer for the required hours. SC: There is some language already in the updated draft that talks about time commitments. If you or others believe that additional guidance is needed, please let me know and it can hopefully be integrated. In this round, the NomCom would be filling both seats for voting appointees in each house of the GNSO, so please note that contrary to the edits in the current GNSO criteria, the voting NCAs, under the GNSO operating principles, are not eligible to become Chair of the Council - only the non-voting NCA can do that, in the event that both houses cannot reach a compromise on who would be Chair. SC: Staff’s reading of the Bylaws and GNSO Operating Procedures is actually a bit different. Section 2.2.b of the GNSO Operating Procedures state that: “Each house will be allowed to nominate one candidate for GNSO Council Chair. Each house is responsible for determining how to nominate its candidate. A candidate for GNSO Council Chair does not need to be a member of a house, but must be a current or incoming member of the GNSO Council. Should a Chair be elected from outside of the houses that Chair will be a non-voting Chair.” And section 11.3.a (v) of the ICANN Bylaws state that: “three representatives selected by the ICANN Nominating Committee, one of which shall be non-voting, but otherwise entitled to participate on equal footing with other members of the GNSO Council including, e.g. the making and seconding of motions and of serving as Chair if elected. One Nominating Committee appointee voting representative shall be assigned to each House (as described in Section 11.3(h)) by the Nominating Committee.” Taken collectively, this seems to indicate that the two voting NomCom appointees, that are assigned to the respective Houses, could be the nominated Chair candidate from a House. The non-voting NCA is also eligible to Chair as you point out and if that were the case, would remain non-voting. As the Council's business is conducted in English, it should indeed be a requirement that candidates can converse, write and understand English. This remains part of the requirements – it was merely shifted underneath “skillset”. Hope this helps! Marie From: council <council-bounces@gnso.icann.org> On Behalf Of Olga Cavalli Sent: Thursday, January 7, 2021 4:35 PM To: Steve Chan <steve.chan@icann.org> Cc: council@gnso.icann.org Subject: Re: [council] Nominating Committee Criteria for Appointing GNSO Councilors Dear Steve, dear colleagues Happy new year!! Steve I added some text to the shared document. Many thanks and best regards Olga El mié, 23 dic 2020 a las 16:08, Steve Chan (<steve.chan@icann.org>) escribió: Dear Councilors, The GNSO Council was invited to review the position description that the ICANN Nominating Committee uses in order to fulfill its appointments to the GNSO Council. You can find the position description for the 2020 cycle here: https://www.icann.org/resources/pages/nomcom2020-positions-2020-01-13-en#gns... [icann.org]. The position description is of course an important piece of guidance for the NomCom, to ensure that it appoints GNSO Councilors that will succeed in their role. Staff, in coordination with Council leadership, has taken that existing description and dropped it into a Google document, where it has undergone some preliminary redlines. A fair amount of those edits are mostly structural, to have the position description look more like a job description (e.g., separating out criteria and skillset and also separating out job responsibilities and time commitment). You can find that redline here, where you are invited to add in your own suggested edits: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCEy... [docs.google.com]. The target date to receive and integrate feedback as appropriate is early January. Finally and most importantly, happy holidays to you all! 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@icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar _______________________________________________ council mailing list council@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 [icann.org]) and the website Terms of Service (https://www.icann.org/privacy/tos [icann.org]). 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.

Dear Councilors, Having seen no comments or objections, I will pass on the revised criteria to the NomCom, which has just very recently opened up its application process (see announcement here: https://www.icann.org/news/announcement-2021-01-25-en). The updated criteria are extremely important for potential candidates to consider, as well as for the NomCom to take into account as it seeks to identify qualified applicants, so thanks all for your comments, feedback and attention. Best, Steve From: council <council-bounces@gnso.icann.org> on behalf of Steve Chan <steve.chan@icann.org> Date: Monday, January 25, 2021 at 2:20 PM To: Marie Pattullo <marie.pattullo@aim.be>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] FW: Nominating Committee Criteria for Appointing GNSO Councilors Dear Councilors, To add to my message below, and in an effort to try and close out this topic in a timely manner, I’d like to see if the document can be agreed to via non-objection, by 23:59 UTC on Wednesday, 27 January 2021. Best, Steve From: council <council-bounces@gnso.icann.org> on behalf of Steve Chan <steve.chan@icann.org> Date: Friday, January 22, 2021 at 2:19 PM To: Marie Pattullo <marie.pattullo@aim.be>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] FW: Nominating Committee Criteria for Appointing GNSO Councilors Dear Councilors, It took a bit longer than expected to integrate the feedback from Councilors. Attached, you can find the latest redline that has suggested edits from me and all of you. Also attached, you can find a proposed clean copy that accepts nearly all of those redlines. However, there is one section of text in the clean version that I would like to draw your attention to however. Jeff had suggested some additional text about how NomCom appointed Councilors should engage as a Councilor, emphasizing that they should act independently. You can get the context of his suggestions and my suggested text in a comment in the redline and that same proposed text from me, incorporated into the clean version and highlighted in yellow. I know this might seem a bit overcomplicated, so apologies in advance – please let me know if you have any questions. Please review and provide any comments at your earliest convenience. As I understand it, the NomCom is expected to launch their invitation process quite soon, though I think this text can actually be incorporated into their process even after its launch. Best, Steve From: council <council-bounces@gnso.icann.org> on behalf of Steve Chan <steve.chan@icann.org> Date: Wednesday, January 13, 2021 at 1:50 PM To: Marie Pattullo <marie.pattullo@aim.be>, "council@gnso.icann.org" <council@gnso.icann.org> Subject: Re: [council] FW: Nominating Committee Criteria for Appointing GNSO Councilors Dear Marie, Thanks for the input. Please see the responses inline to your bullets below, in blue. Please let me know of course if you still have questions, comments or concerns. I will send around a proposed final red-line and clean copy in a bit for non-objection. Best, Steve From: council <council-bounces@gnso.icann.org> on behalf of Marie Pattullo <marie.pattullo@aim.be> Date: Wednesday, January 13, 2021 at 6:32 AM To: "council@gnso.icann.org" <council@gnso.icann.org> Subject: [council] FW: Nominating Committee Criteria for Appointing GNSO Councilors Steve, all Many thanks for this and apologies for missing your deadline. If still useful, some points that my former NomCom colleagues have raised: We have to be conscious that in the past there have been complaints by some NomCom appointees about the volume of work required by the GNSO because they underestimated the responsibilities attached to the role – we need to be sure this is clear upfront. It is important that the GNSO clearly spells out the time requirement for the role so that interested candidates determine if they can volunteer for the required hours. SC: There is some language already in the updated draft that talks about time commitments. If you or others believe that additional guidance is needed, please let me know and it can hopefully be integrated. In this round, the NomCom would be filling both seats for voting appointees in each house of the GNSO, so please note that contrary to the edits in the current GNSO criteria, the voting NCAs, under the GNSO operating principles, are not eligible to become Chair of the Council - only the non-voting NCA can do that, in the event that both houses cannot reach a compromise on who would be Chair. SC: Staff’s reading of the Bylaws and GNSO Operating Procedures is actually a bit different. Section 2.2.b of the GNSO Operating Procedures state that: “Each house will be allowed to nominate one candidate for GNSO Council Chair. Each house is responsible for determining how to nominate its candidate. A candidate for GNSO Council Chair does not need to be a member of a house, but must be a current or incoming member of the GNSO Council. Should a Chair be elected from outside of the houses that Chair will be a non-voting Chair.” And section 11.3.a (v) of the ICANN Bylaws state that: “three representatives selected by the ICANN Nominating Committee, one of which shall be non-voting, but otherwise entitled to participate on equal footing with other members of the GNSO Council including, e.g. the making and seconding of motions and of serving as Chair if elected. One Nominating Committee appointee voting representative shall be assigned to each House (as described in Section 11.3(h)) by the Nominating Committee.” Taken collectively, this seems to indicate that the two voting NomCom appointees, that are assigned to the respective Houses, could be the nominated Chair candidate from a House. The non-voting NCA is also eligible to Chair as you point out and if that were the case, would remain non-voting. As the Council's business is conducted in English, it should indeed be a requirement that candidates can converse, write and understand English. This remains part of the requirements – it was merely shifted underneath “skillset”. Hope this helps! Marie From: council <council-bounces@gnso.icann.org> On Behalf Of Olga Cavalli Sent: Thursday, January 7, 2021 4:35 PM To: Steve Chan <steve.chan@icann.org> Cc: council@gnso.icann.org Subject: Re: [council] Nominating Committee Criteria for Appointing GNSO Councilors Dear Steve, dear colleagues Happy new year!! Steve I added some text to the shared document. Many thanks and best regards Olga El mié, 23 dic 2020 a las 16:08, Steve Chan (<steve.chan@icann.org>) escribió: Dear Councilors, The GNSO Council was invited to review the position description that the ICANN Nominating Committee uses in order to fulfill its appointments to the GNSO Council. You can find the position description for the 2020 cycle here: https://www.icann.org/resources/pages/nomcom2020-positions-2020-01-13-en#gns... [icann.org]. The position description is of course an important piece of guidance for the NomCom, to ensure that it appoints GNSO Councilors that will succeed in their role. Staff, in coordination with Council leadership, has taken that existing description and dropped it into a Google document, where it has undergone some preliminary redlines. A fair amount of those edits are mostly structural, to have the position description look more like a job description (e.g., separating out criteria and skillset and also separating out job responsibilities and time commitment). You can find that redline here, where you are invited to add in your own suggested edits: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCEy... [docs.google.com]. The target date to receive and integrate feedback as appropriate is early January. Finally and most importantly, happy holidays to you all! 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@icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar _______________________________________________ council mailing list council@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 [icann.org]) and the website Terms of Service (https://www.icann.org/privacy/tos [icann.org]). 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.
participants (8)
-
Farell FOLLY
-
Marie Pattullo
-
Maxim Alzoba
-
Olga Cavalli
-
Steve Chan
-
Tom Dale
-
Tomslin Samme-Nlar
-
Wisdom Donkor