[council] GNSO Council resolutions 24 August 2023

[Terri Agnew]

Dear all,

Please find below the resolutions from the GNSO Council meeting on Wednesday, 14 June 2023, which will be posted shortly on the GNSO Council resolutions <https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/2020-current__;!!PtGJab4!sLlCB4cV9KdvFnPD2LwSl2p7z4Gk6tPXTWpUAhoW8SCziUIjp5aHd47AEUpgcVkTCRcwggmgOcyz$> page.


20230824-1
CONSENT AGENDA

Approval of the 2023 Customer Standing Committee (CSC) Slate of Members and Liaisons
Submitted by Greg DiBiase
Seconded by Paul McGrady

Whereas,


  1.  The Customer Standing Committee (CSC) was established as one of the post IANA Transition entities and conducted its first meeting on 6 October 2016.
  2.  In accordance with Section 17.2 (d) of the ICANN Bylaw and per the CSC Charter, the full membership of the CSC must be approved by the GNSO Council.
  3.  On 9 August 2023, the GNSO Council received a letter from ICANN org staff supporting the CSC requesting that the GNSO Council approve the CSC slate of members and liaisons, noting that the SSAC has declined to appoint a liaison:

Members:

Dmitry Burkov (EU)
Appointing Organization: RySG
Term: 2023 - 2025

Federico Neves (LAC)
Appointing Organization: ccNSO
Term: 2023 – 2025

Brett Carr (EU)
Appointing Organization: ccNSO
Term: 2022 - 2024

Rick Wilhelm (NA)
Appointing Organization: RySG
Term: 2022 - 2024

Liaisons:

Holly Raiche
Appointing Organization: ALAC
Term: 2023 - 2025

Milton Mueller
Appointing Organization: GNSO (Non-Registry)
Term: 2023 - 2025

Gloria Atwine Katuuku
Appointing Organization: GAC
Term: 2022 – 2024

Ken Renard
Appointing Organization: RSSAC
Term: 2022 - 2024
Amy Creamer
Appointing Organization: PTI
Term: No term limit

Alternates:

John Gbadamosi
Appointing Organization: GNSO (Non-Registry)
Term: 2023 - 2025

Ejikeme Egbuogu
Appointing Organization: ALAC
Term: 2023 - 2025


Resolved,


  1.  The GNSO Council approves the 2023 CSC slate of members and liaisons.
  2.  The GNSO Council requests that the GNSO Secretariat notify ICANN Org staff supporting the CSC no later than 1 September 2023 that the GNSO has approved the 2023 CSC slate of members and liaisons.
Vote results<https://gnso.icann.org/sites/default/files/policy/2023/vote-result/gnso-council-motion-recorder-24aug24-en.pdf>
20230824-2

Approval of the GNSO Council’s Clarifying Statement Regarding Select Pending SubPro Recommendations
Submitted by Greg DiBiase
Seconded by Susan Payne

Whereas,

  1.  The GNSO Council adopted<https://gnso.icann.org/en/council/resolutions/2020-current#202102> the Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf> of the New gTLD Subsequent Procedures (SubPro) PDP on 18 February 2021.
  2.  On 16 March 2023, the ICANN Board adopted the majority of the SubPro Outputs, as identified in Section A of the Scorecard<https://www.icann.org/en/system/files/files/scorecard-subpro-pdp-board-action-16mar23-en.pdf>, while designating a select set of recommendations as pending, identified in Section B<https://www.icann.org/en/system/files/files/scorecard-subpro-pdp-board-action-16mar23-en.pdf> of the Scorecard.
  3.  The GNSO Council established a small team to carefully review the pending SubPro recommendations and identify the best path forward to seek to resolve the issues that were preventing Board adoption of the pending recommendations.
  4.  The GNSO Council’s small team benefited greatly from the open and frank dialogue with the co-leads of the Board’s Caucus on SubPro.
  5.  On 22 May 2023, the GNSO Council and ICANN Board discussed the expectation that for certain pending recommendations, a Clarifying Statement from the Council may be sufficient to mitigate the concerns preventing adoption of some of the pending recommendations.
  6.  At ICANN77, the GNSO Council and ICANN Board reached agreement on the specific set of pending recommendations that may be resolved via a Clarifying Statement from the Council.
  7.  The GNSO Council’s small team developed a draft Clarifying Statement<https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-sub-pro-pending-recommendations-10jul23-en.pdf> that was discussed with the Council during its July meeting and was subsequently shared with the ICANN Board for their consideration of whether the Clarifying Statement does indeed address the Board’s concerns.
  8.  The GNSO Council took into account the feedback from the ICANN Board and finalized the Council’s Clarifying Statement<https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-subpro-pending-recommendations-redline-23aug23-en.pdf> by removing the text in the Clarifying Statement relating to the enforceability of PICs and RVCs and holding this over to a future Clarifying Statement, pending further feedback from the ICANN Board.
  9.  The Clarifying Statement should be read as complementary to the relevant pending recommendation(s) and should be considered jointly with the recommendations for the purposes of implementation.



Resolved,

  1.  The GNSO Council approves the Clarifying Statement<https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-subpro-pending-recommendations-clean-23aug23-en.pdf> regarding select pending SubPro recommendations and stresses that the statement should be read as complementary to the relevant pending recommendation(s) and should be considered jointly with the recommendations for the purposes of implementation.
  2.  The GNSO Council requests that the GNSO Secretariat communicate resolved #1 to the ICANN Board and provide the Board with the Clarifying Statement.
  3.  The GNSO Council extends its thanks to the ICANN Board for its collegial, constructive, and pragmatic approach to addressing select pending recommendations and in particular, extends thanks to the co-leads of the Board’s Caucus on SubPro, Avri Doria and Becky Burr.

Vote results<https://gnso.icann.org/sites/default/files/policy/2023/vote-result/gnso-council-motion-recorder-24aug24-en.pdf>

Thank you.

Kind regards,

Terri
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/council/attachments/20230824/38f2cfe5/attachment-0001.html>