[council] NomCom Rebalancing response

Tue Jul 4 13:59:48 UTC 2023

Hi Paul,

Thanks alot. That suggestion works. For completeness, I also made a minor
edit to Question #1. So here below is what I see as the proposed response
which includes your suggestion:

   1.

   What does it mean to have a balanced NomCom at a point in time? For
   example, what criteria would you apply to measure or assess whether the
   NomCom is balanced? And further, how can one test whether or not the NomCom
   is balanced?

GNSO Council response: The current NomCom structure is based on
appointments made by bodies defined in the ICANN Bylaws ACs, SOs, SGs and
Constituencies (https://www.icann.org/nomcom2023). Going by this structure,
a balanced NomCom is one with all Stakeholder Groups and Constituencies
equally represented and this also forms the measure of balanced.

   1.

   Do you support the view that the current composition of the NomCom needs
   to be rebalanced? Please explain why or why not.

GNSO Council response: Composition of the NomCom is based on appointments
made by bodies defined in the ICANN Bylaws. Article 8.2 of the ICANN Bylaws
regarding NomCom composition refers to GNSO organizations as per Article
11. However, the only NCSG constituency listed is NCUC. Accordingly,
Article 8.2 of the Bylaws should be amended to add a seat on the NomCom for
NPOC. The GNSO Council supports rebalancing the current composition to
allow for all GNSO Constituencies to appoint at least one delegate to the
NomCom.

   1.

   How do you suggest that the NomCom’s composition be rebalanced?

GNSO Council response: Addition of one seat in order to better represent
the disparities amongst Constituencies representation and in order for NPOC
to also be represented at the NomCom.

Happy to discuss further.

Warmly,
Tomslin

On Mon, 3 Jul 2023 at 22:45, Paul McGrady via council <
council at gnso.icann.org> wrote:

> Thanks Bruna, Mark, Farell, Tomslin, and Susan,
>
>
>
> All, I think the reason for Susan’s proposed edit is coming from the
> current text which uses the singular article “a”, i.e. that at the end of
> the rebalancing each GNSO constituency would get “a” (singular) delegate to
> the Nom Com.
>
>
>
>    1. *Do you support the view that the current composition of the NomCom
>    needs to be rebalanced? Please explain why or why not.*
>
> GNSO Council response: Composition of the NomCom is based on appointments
> made by bodies defined in the ICANN Bylaws. Article 8.2 of the ICANN Bylaws
> regarding NomCom composition refers to GNSO organizations as per Article
> 11. However, the only NCSG constituency listed is NCUC. Accordingly,
> Article 8.2 of the Bylaws should be amended to add a seat on the NomCom for
> NPOC. The GNSO Council supports rebalancing the current composition to
> allow for all GNSO Constituencies to appoint a delegate to the NomCom.
>
>
>
> Combined with our request to add NPOC, this use of the singular article
> “a” could be read as the Council’s desire to remove one NomCom seat from
> the BC (which has 2) and give that to NPOC.  If that is not our will, we
> need to correct the singular article “a”, perhaps along the lines of “at
> least one.”  I think this makes more sense anyway, since why should we
> limit ourselves this early in the discussions when others in the community
> are certainly going to advocate for more seats for them while the Council,
> in the current draft, is advocating for simply reshuffling what we already
> have.
>
>
>
> If it is our will, however, to eliminate one seat for the BC and transfer
> that seat to the NPOC, I don’t think we should hide a ball that big – let’s
> just say it directly.  I expect the BC reps may want to reply to this email.
>
>
>
> For clarity, I think we should not include Susan’s addition, but modify
> our response on 2. to read:
>
>
>
>    1. *Do you support the view that the current composition of the NomCom
>    needs to be rebalanced? Please explain why or why not.*
>
> GNSO Council response: Composition of the NomCom is based on appointments
> made by bodies defined in the ICANN Bylaws. Article 8.2 of the ICANN Bylaws
> regarding NomCom composition refers to GNSO organizations as per Article
> 11. However, the only NCSG constituency listed is NCUC. Accordingly,
> Article 8.2 of the Bylaws should be amended to add a seat on the NomCom for
> NPOC. The GNSO Council supports rebalancing the current composition to
> allow for all GNSO Constituencies to appoint at least one delegate to the
> NomCom.
>
>
>
> Hope this helps.
>
>
>
> Best,
>
> Paul
>
>
>
>
>
>
>
>
>
> *From:* council <council-bounces at gnso.icann.org> *On Behalf Of *Bruna
> Martins dos Santos via council
> *Sent:* Monday, July 3, 2023 4:08 AM
> *To:* Mark W. Datysgeld <mark at governanceprimer.com>
> *Cc:* GNSO-Chairs <gnso-chairs at icann.org>; Julie Bisland via Gnso-secs <
> gnso-secs at icann.org>; COUNCIL at GNSO.ICANN.ORG
> *Subject:* Re: [council] NomCom Rebalancing response
>
>
>
> Id like to also support Tomslin point on this matter. And I trust that the
> language that is on the document translates well NCSG's concerns regarding
> the *addition* of a seat in order to better represent the current
> configuration of GNSO at NomCom. And, in all honesty, I think this
> discussion is about remedying the lack of proper Non-Commercial
> representation at the committee, above all.
>
>
>
> Best,
>
> Bruna
>
>
>
> On Mon, Jul 3, 2023 at 3:19 AM Mark W. Datysgeld via council <
> council at gnso.icann.org> wrote:
>
> We could probably do with CPH or NomCom appointees input here.
>
> ---
>
> Mark W. Datysgeld
> Director at Governance Primer
> ICANN GNSO Councilor
> ------------------------------
>
> *From:* Farell FOLLY via council <council at gnso.icann.org>
> *Sent:* Sunday, July 2, 2023 19:41
> *To:* Tomslin Samme-Nlar
> *Cc:* GNSO-Chairs; Julie Bisland via Gnso-secs; COUNCIL at GNSO.ICANN.ORG
> *Subject:* Re: [council] NomCom Rebalancing response
>
>
>
> I would second Tomslin on this.
>
>
>
>
>
> Best regards
>
> @__f_f__
>
> ____________________________________
>
>
>
> Lt-Colonel Farell FOLLY, Ir.
>
>
>
> GNSO Councillor - ICANN (Los Angeles, USA).
>
> https://www.linkedin.com/in/farellf/?locale=en_US
>
>
>
>
>
>
>
>
>
>
>
> On 2 Jul 2023, at 12:57, Tomslin Samme-Nlar via council <
> council at gnso.icann.org> wrote:
>
>
>
> Dear Susan, all
>
>
>
> I would like to politely disagree with the proposed change. I think
> section 4 as originally written answers the question of 'how' enough from a
> council perspective.
>
>
>
> Warmly,
> Tomslin
>
>
>
> On Sat, 1 July 2023, 02:30 Susan Payne via council, <
> council at gnso.icann.org> wrote:
>
> Hi Sebastien
>
> Thanks for this, and thanks to those who worked on the draft.  I have
> proposed one addition to section 4 : “For avoidance of doubt, we do not
> believe that this should be effected by removing any seats from other GNSO
> groups.”  I would trust that my Council colleagues would not disagree with
> this.
>
>
>
> thanks
>
>
>
> Susan Payne
> Head of Legal Policy
> Com Laude
> *T* +44 (0) 20 7421 8250
> *Ext* 255
>
>
>
> *We are pleased to launch our new YouTube channel*[image: .]
> <https://comlaude.com/>
>
> *From:* council <*council-bounces at gnso.icann.org*> *On Behalf Of *Sebastien---
> via council
> *Sent:* Monday, June 26, 2023 9:28 PM
> *To:* *COUNCIL at GNSO.ICANN.ORG*; GNSO-Chairs <*gnso-chairs at icann.org*>;
> *gnso-secs at icann.org*
> *Subject:* [council] NomCom Rebalancing response <https://comlaude.com/>
>
>   <https://comlaude.com/>
>
>
> *https://docs.google.com/document/d/1QF_o1d5o3cqdJi1c_2YyWcsCepWpKGx-/edit?pli=1*
> <https://comlaude.com/>
>
>   <https://comlaude.com/>
>
> Dear Council Colleagues, <https://comlaude.com/>
>
>   <https://comlaude.com/>
>
> We have prepared a response to the Board’s questions about the NomCom
> rebalancing.
> While we discussed this in DC (albeit briefly), we didn’t sense the need
> for any specific response from the Council other than to maybe say that we
> would welcome the opportunity of a seat at the table for an NPOC
> representative (the only SG/C not currently represented).
> <https://comlaude.com/>
>
> As it the tradition, the GNSO Council will limit its comments to what is
> directly a Council concern, and will let its different SG&Cs comment in
> their own right. <https://comlaude.com/>
>
>   <https://comlaude.com/>
>
> With this in mind, can I ask you to review the Google doc referenced
> above, and indicate by Friday 30 June any concerns you may have with this
> letter going out? The response deadline to the Board in Friday. Please also
> ensure your SG/Cs formulate their own response by then if not already done.
> <https://comlaude.com/>
>
>   <https://comlaude.com/>
>
> Kindly, <https://comlaude.com/>
>
>   <https://comlaude.com/>
>
>
>
> *Sebastien Ducos* <https://comlaude.com/>
>
> GoDaddy Registry | Senior Client Services Manager <https://comlaude.com/>
>
> +33612284445 <https://comlaude.com/>
>
> France & Australia <https://comlaude.com/>
>
> sebastien at registry.godaddy <https://comlaude.com/>
>
>   <https://comlaude.com/>
>
> <https://comlaude.com/>
> ------------------------------
> <https://comlaude.com/>
>
>
>
> The contents of this email and any attachments are confidential to the
> intended recipient. They may not be disclosed, used by or copied in any way
> by anyone other than the intended recipient. If you have received this
> message in error, please return it to the sender (deleting the body of the
> email and attachments in your reply) and immediately and permanently delete
> it. Please note that Com Laude Group Limited (the “Com Laude Group”) does
> not accept any responsibility for viruses and it is your responsibility to
> scan or otherwise check this email and any attachments. The Com Laude Group
> does not accept liability for statements which are clearly the sender's own
> and not made on behalf of the group or one of its member entities. The Com
> Laude Group is a limited company registered in England and Wales with
> company number 10689074 and registered office at 28-30 Little Russell
> Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ
> Limited t/a Com Laude, a company registered in England and Wales with
> company number 5047655 and registered office at 28-30 Little Russell
> Street, London, WC1A 2HN England; Valideus Limited, a company registered in
> England and Wales with company number 6181291 and registered office at
> 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a
> company registered in Scotland with company number SC197176 and registered
> office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland;
> Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation
> incorporated in the State of Washington and principal office address at
> Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com
> Laude (Japan) Corporation, a company registered in Japan with company
> number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku,
> Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered
> in Spain and registered office address at Calle Barcas 2, 2, Valencia,
> 46002, Spain. For further information see *www.comlaude.com*
> <https://comlaude.com/>
>
> _______________________________________________
> 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.
> <https://comlaude.com/>
>
> <image003.png>_______________________________________________
> 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.
> <https://comlaude.com/>
>
> _______________________________________________
> 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.
> <https://comlaude.com/>
>
>
> <https://comlaude.com/>
>
> -- <https://comlaude.com/>
>
> *Bruna Martins dos Santos * <https://comlaude.com/>
>
> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | *Alexander
> von Humboldt Foundation* <https://comlaude.com/>
>
> Member | *Coalizão Direitos na Rede*
> Co-Coordinator | *Internet Governance Caucus * <https://comlaude.com/>
>
> Twitter: *@**boomartins* // Skype: bruna.martinsantos
> <https://comlaude.com/>
>
> Email: *bruna.mrtns at gmail.com* <https://comlaude.com/>
>
> This email originated from outside the firm. Please use caution.
> <https://comlaude.com/>
> _______________________________________________
> 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/council/attachments/20230704/392ea677/attachment-0001.html>