All, On Tue, Sep 23, 2025 at 01:37:26PM +0200, Alejandra Reynoso Barral via Ccnso-council wrote:

The Google doc access has been updated.

that made me add a number of comments to the doc and the proposed changes. There's one in particular that I think needs a bit more attention: "The ccNSO Council does not regard a potential appointee's employment by an ICANN contracted party to be any barrier. Already a number of ccTLD managers are also contracted parties and this is no barrier to ccNSO participation, including at the Council level. " Not sure what inspired this, but I do not think I agree - for a number of reasons, the easiest being that what is presented as a conclusion, or at least a precedent, doesn't hold. The fact that some ccTLD managers are "contracted" cannot limit their membership rights, which is something the additional Councillors don't bring. And, by the way, we explicitly ask for "no ccTLD affiliation" (for good reasons) which would be wrong if we followed the logic above. The fact that there might already be a bit of 'g' mixed in doesn't necessarily suggest to encourage more of that. Whatever the intention was, we should probably widen the scope of this advice. Noting that we do not state anything about non-contracted parties (still GNSO), ALAC, GAC, or others, I can only guess there was a specific observation from a more recent NomCom and the response turned into what I perceive as an explicit invitation. Best regards Peter

Hi Jordan This document includes the informal advice given at the start of year, at the "Eligibility" section. Here is the reference, if helpful: https://ccnso.icann.org/sites/default/files/field-attached/reynoso-to-nomcom... Best, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Wed, Sep 24, 2025 at 2:19 AM Jordan Carter via Ccnso-council < ccnso-council@icann.org> wrote:

Hi all

Just separate to Peter's point, does this updated version work in the informal advice that we had offered the NomCom last year? Should we be preparing that document separately as well, or integrating the two?

Cheers Jordan

-----Original Message----- From: Peter Koch via Ccnso-council <ccnso-council@icann.org> Sent: Tuesday, 23 September 2025 10:29 PM To: Alejandra Reynoso Barral <alejandra.reynoso@gmail.com> Cc: ccNSO Council <ccnso-council@icann.org> Subject: [EXTERNAL] - [ccnso-council] Re: Job-description NomCom appointed ccNSO Councillor

All,

On Tue, Sep 23, 2025 at 01:37:26PM +0200, Alejandra Reynoso Barral via Ccnso-council wrote:

...

The Google doc access has been updated.

that made me add a number of comments to the doc and the proposed changes.

There's one in particular that I think needs a bit more attention:

"The ccNSO Council does not regard a potential appointee's employment by an ICANN contracted party to be any barrier. Already a number of ccTLD managers are also contracted parties and this is no barrier to ccNSO participation, including at the Council level. "

Not sure what inspired this, but I do not think I agree - for a number of reasons, the easiest being that what is presented as a conclusion, or at least a precedent, doesn't hold. The fact that some ccTLD managers are "contracted" cannot limit their membership rights, which is something the additional Councillors don't bring. And, by the way, we explicitly ask for "no ccTLD affiliation" (for good reasons) which would be wrong if we followed the logic above. The fact that there might already be a bit of 'g' mixed in doesn't necessarily suggest to encourage more of that.

Whatever the intention was, we should probably widen the scope of this advice. Noting that we do not state anything about non-contracted parties (still GNSO), ALAC, GAC, or others, I can only guess there was a specific observation from a more recent NomCom and the response turned into what I perceive as an explicit invitation.

Best regards Peter _______________________________________________ Ccnso-council mailing list -- ccnso-council@icann.org To unsubscribe send an email to ccnso-council-leave@icann.org _______________________________________________ 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. _______________________________________________ Ccnso-council mailing list -- ccnso-council@icann.org To unsubscribe send an email to ccnso-council-leave@icann.org _______________________________________________ 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.