Registries SG feedback on Fundamental Bylaws Amendment Approval Action

Tue Nov 19 05:35:30 EET 2019

hi all,

sharing here a communication from Registries SG (RySG)
regarding Fundamental Bylaws Amendment related to IANA Functions Review
that was requested by ccNSO and is going through the Empowered Community
approval process. The RySG are suggesting to *" it may be prudent for the
Empowered Community to consider a review of the Fundamental Bylaws at some
time in the future with a view to removing flaws, contradictions or
conflicts between requirements."*

the proposal seems reasonable (while it means some work in addition to all
what is going on in future) but looking for input and feedback here.

Best,

Rafik

---------- Forwarded message ---------
De : Maxim Alzoba <m.alzoba at gmail.com>
Date: mar. 19 nov. 2019 à 06:03
Subject: [council] Fwd: Re: [Ext] Re: FW: Reminder: Deadline Tuesday 19
November 2019: Beginning of the GNSO community feedback period: Fundamental
Bylaws Amendment Approval Action
To: Drazek, Keith via council <council at gnso.icann.org>, Drazek, Keith <
kdrazek at verisign.com>, Donna Austin <donna.austin at team.neustar>, Ducos,
Sebastien <sebastien.ducos at team.neustar>, <gnso-secs at icann.org>

Dear Councillors,

Please find RySG feedback below:

Maxim Alzoba

The RySG supports the Fundamental Bylaws Amendment re IANA Naming Function
> Review Composition as requested by the ccNSO.
>
>
>
> The RySG appreciates the discussion during the Community Action Approval
> Forum (CAAF) that recognized the importance of the community process that
> ultimately lead to the approval of the Fundamental Bylaws in order to move
> forward with the IANA Transition as well as highlighting some of the
> challenges associated with meeting the prescribed requirements that
> ultimately lead to the amendment request from the ccNSO. During the
> discussion, Katrina Sataki also highlighted that the ccNSO is likely to
> have the same problem in finding a non-ccNSO representative in the event
> that a separation working group (Section 19.4) is ever required.
>
>
>
> The RySG also had challenges meeting the prescribed requirements for
> representatives from the RySG for the IANA Naming Function Review that we
> highlighted during the associated public comment process:
>
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.wixstatic.com_ugd_ec8e4c-5F90b99999e38546a4ae25ea556a165ad4.pdf&d=DwIF-g&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=kCfx3XrmJJU4ZbJq2ad6XblwlnehXeYKn1YKwkFN6bA&s=Q50n-Aejqw1_Y4utaxZIBeCIexKzoHu9OVbZLhaI378&e=
>
>
>
>
> During the CAAF, Jim Galvin recognized that the bylaws were written “ ..
> very, very quickly during the transition…” and further that “… where we as
> the community find loopholes or flaws, or contradictions within the bylaws,
> it's up to us now as the communities here to raise these fundamental bylaw
> changes, to come back to ICANN Legal with proposals on, oh hey, we've seen
> a conflict here between these two requirements. This is really our role now
> in order to solve those conflicts.”
>
>
>
> In this context, it may be prudent for the Empowered Community to consider
> a review of the Fundamental Bylaws at some time in the future with a view
> to removing flaws, contradictions or conflicts between requirements.
>
>  ======
>
>
>
> *From:* Nathalie Peregrine [mailto:nathalie.peregrine at icann.org]
> *Sent:* Thursday, November 14, 2019 1:45 AM
> *To:* gbunton at tucows.com; Austin, Donna <Donna.Austin at team.neustar>;
> Selli, Claudia <cs574w at intl.att.com>; Brian Winterfeldt
> <Brian at Winterfeldt.law>; Wolf-Ulrich Knoben <
> Wolf-Ulrich.Knoben at t-online.de>; Stephanie Perrin <
> stephanie.perrin at mail.utoronto.ca>; Joan Kerr <joankerr at fbsc.org>; Bruna
> Martins dos Santos <bruna.mrtns at gmail.com>
> *Cc:* Ariel Liang <ariel.liang at icann.org>; Sue Schuler <
> secretariat at rysg.info>; gnso-secs at icann.org; Zoe Bonython <
> secretariat at icannregistrars.org>; Maryam Bakoshi <maryam.bakoshi at icann.org>;
> Chantelle Doerksen <chantelle.doerksen at icann.org>; Julie Hedlund <
> julie.hedlund at icann.org>
> *Subject:* Reminder: Deadline Tuesday 19 November 2019: Beginning of the
> GNSO community feedback period: Fundamental Bylaws Amendment Approval Action
>
>
>
> Dear Stakeholder Groups and Constituency Chairs,
>
>
>
> Following the Approval Action Community Forum [66.schedule.icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__66.schedule.icann.org_meetings_1116779&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=2cPq9HldwzJ0SRBxvUOjPdv0w97yO16GBwmoa3UocWY&s=e8c4rZoNtT744A89kky6k9wiSoRfbZ_VZuXKCSIRjrc&e=>
> on the “Fundamental Bylaws Amendment Approval Action in regard to the IANA
> Naming Function Review Composition”, which took place on Sunday, 3 November
> 2019 during ICANN66, GNSO Stakeholder Groups’ and Constituencies’ input
> is now being sought by the GNSO Council. This marks the start of the GNSO
> community feedback period following the Approval Action Community Forum.
>
>
>
> Please provide opinions or comments, if any, from your Stakeholder Groups
> or Constituencies’ on the Approval Action under consideration that would inform
> the GNSO Council’s support for, objection to, or abstention from the
> Approval Action. Any feedback from your Stakeholder Groups and
> Constituencies must be submitted to the GNSO Council *through your
> Council representatives* by *Tuesday 19 November 2019 at 23:59 UTC.*
>
>
>
> Following the closing of the GNSO community feedback period, the GNSO
> Council – the representative body of the GNSO as a Decisional Participant
> in the Empowered Community – will conduct an electronic vote to decide
> whether to support, object to, or abstain from the Approval Action.
>
>
>
> *Please use the following materials for context of the Approval Action
> that the GNSO Council is going to vote on:*
>
>
>    - Board Notice of the Board Approval of Fundamental Bylaws Amendment
>    re IANA Naming Function Review Composition: https://www.icann.org/en/system/files/bm/secretarys-notice-3-13sep19-en.pdf
>    [icann.org]
>    <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_bm_secretarys-2Dnotice-2D3-2D13sep19-2Den.pdf&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=2cPq9HldwzJ0SRBxvUOjPdv0w97yO16GBwmoa3UocWY&s=auaf60E43ClSoQfnZzSyT4rPTcp9BtOgdrefiS23o4g&e=>
>
>    - Board Approval of Fundamental Bylaws Amendment to composition of the
>    IANA Naming Functions Review: https://www.icann.org/resources/board-material/prelim-report-2019-09-08-en#1.e
>    [icann.org]
>    <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_board-2Dmaterial_prelim-2Dreport-2D2019-2D09-2D08-2Den-231.e&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=2cPq9HldwzJ0SRBxvUOjPdv0w97yO16GBwmoa3UocWY&s=CDH6VVweTgOqtcK5LdPgOAo-OIPlDjFEVTytixl4hR4&e=>
>
>    - Staff report of the public comment on the “Fundamental Bylaws
>    Amendment Proposal – IANA Naming Function Review”: https://www.icann.org/en/system/files/files/report-comments-bylaws-amend-iana-naming-function-12aug19-en.pdf
>    [icann.org]
>    <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_files_report-2Dcomments-2Dbylaws-2Damend-2Diana-2Dnaming-2Dfunction-2D12aug19-2Den.pdf&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=2cPq9HldwzJ0SRBxvUOjPdv0w97yO16GBwmoa3UocWY&s=LXy4raPHVK9rFzev4Zwea4uWQgfabv6jt1SmCCbFSZo&e=>
>
>
>
>
> Thank you,
>
>
>
> Kind regards,
>
>
>
> Nathalie Peregrine
>
> Manager, Operations Support (GNSO)
>
> Internet Corporation for Assigned Names and Numbers (ICANN)
>
> Email: nathalie.peregrine at icann.org
> <http://nathalie.peregrine@icann.org%20>
>
> Skype: nathalie.peregrine.icann
>
>
>
> 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=>
>
> See All SO and AC events on the ICANN Global calendar [features.icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__features.icann.org_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=2cPq9HldwzJ0SRBxvUOjPdv0w97yO16GBwmoa3UocWY&s=fyrsAzJOqnaod6aw0dD1ma-zFsXMUahf0dUYL4edjXo&e=>
>
>
>
>
>
> _______________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20191119/76504757/attachment.htm>