[council] GNSO Council resolutions 25 August 2022

Thu Aug 25 16:07:30 UTC 2022

Dear all,

Please find below the resolution from the GNSO Council meeting on Thursday, 25 August 2022 which has been posted on the GNSO Council resolutions <https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/2020-current__;!!PtGJab4!sLlCB4cV9KdvFnPD2LwSl2p7z4Gk6tPXTWpUAhoW8SCziUIjp5aHd47AEUpgcVkTCRcwggmgOcyz$> page.

20220825-1

Approval of the 2022 Customer Standing Committee (CSC) Slate of Members and Liaisons

Submitted by Philippe Fouquart

Seconded by Tomslin Samme-Nlar

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 4 August 2022, the GNSO Council received a letter<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/bryce-to-fouquart-et-al-04aug22-en.pdf> 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:

Brett Carr (EU) (reappointed)

Appointing Organization: ccNSO

Term: 2022 - 2024

Rick Wilhelm (NA)

Appointing Organization: RySG

Term: 2022 - 2024

Dmitry Burkov (EU)

Appointing Organization: RySG

Term: 2021 - 2023

Federico Neves (LAC)

Appointing Organization: ccNSO

Term: 2021 – 2023

Liaisons:

Gloria Atwine Katuuku

Appointing Organization: GAC

Term: 2022 – 2024

Ken Renard

Appointing Organization: RSSAC

Term: 2022 - 2024

Holly Raiche

Appointing Organization: ALAC

Term: 2021 - 2023

Milton Mueller

Appointing Organization: GNSO (Non-Registry)

Term: 2021 - 2023

Amy Creamer

Appointing Organization: PTI

Term: No term limit

Resolved,

  1.  The GNSO Council approves the 2022 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 2022 that the GNSO has approved 2022 CSC slate of members and liaisons.

Vote results<https://gnso.icann.org/sites/default/files/policy/2022/vote-result/gnso-council-motion-recorder-25aug22-en.pdf>

20220825-2

Initiation of the GNSO Guidance Process on Applicant Support (DEFERRED to the August 2022 meeting)

Submitted by: Philippe Fouquart

Seconded by: Sebastien Ducos

SubProGGPInitiationRequest_24 August 2022_redline.docx<https://community.icann.org/download/attachments/206144520/SubProGGPInitiationRequest_24%20August%202022_redline.docx?version=1&modificationDate=1661418235000&api=v2>

SubProGGPInitiationRequest_24 August 2022_clean.docx<https://community.icann.org/download/attachments/206144520/SubProGGPInitiationRequest_24%20August%202022_clean.docx?version=1&modificationDate=1661418247000&api=v2>

Whereas,

  1.  In February 2021, the GNSO Council approved the consensus Affirmations, Recommendations, and Implementation Guidance (collectively referred to as "Outputs") of the New gTLD Subsequent Procedures (SubPro) PDP.
  2.  In September 2021, the ICANN Board directed the ICANN og to organize the resources required to begin work on an Operational Design Phase (ODP) and the ODP launched on 3 January 2022.
  3.  The ICANN org ODP Team identified a concern related to the Applicant Support topic, where the SubPro Final Report envisioned that a dedicated Implementation Review Team (IRT) would be responsible for performing substantive work; the ODP Team submitted a set of questions<https://mm.icann.org/pipermail/subpro-odp/2022-February/000033.html> to the GNSO Council, asking whether the work required to implement Applicant Support may be beyond the scope envisioned for IRTs.
  4.  The GNSO Council responded<https://mm.icann.org/pipermail/subpro-odp/attachments/20220526/8ffa36fc/GNSOResponsestoSubProODPQuestionSet2-0001.pdf> to the ODP Team, communicating that it would explore avenues to perform work as envisaged by the SubPro Final Report.
  5.  The GNSO Council discussed and agreed that the GNSO Guidance Process (GGP) would serve as an appropriate mechanism in order to provide additional guidance to support eventual implementation efforts.
  6.  The GNSO Council further agreed that the GGP should be limited to the single topic of Applicant support, with an allowance to add additional scope to the GGP subject to Council vote.
  7.  On 13 July 2022, the GGP Initiation Request<https://mm.icann.org/pipermail/council/2022-July/025817.html> was submitted to the GNSO Council.
  8.  The GNSO Council determined that more time was needed to refine the Initiation Request and the vote was deferred.
  9.  The GGP Initiation Request was refined following input from Councilors and an updated GGP Initiation Request<https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-subpro-ggp-initiation-request-clean-24aug22-en.pdf> was shared with the GNSO Council on 24 August 2022.

Resolved,

  1.  The GNSO Council approves the GNSO Guidance Process Initiation Request and initiates the GGP.
  2.  The GNSO Council directs staff to:

     *   communicate the results of this motion to the GNSO SG/Cs as well as ICANN SO/ACs and invite them to identify Members for the Working Group following the Working Group composition described in the initiation request;
     *   communicate the results of this motion to the ICANN Org GDS Team and invite them to identify at least one (1) staff liaison for the Working Group; and
     *   launch a call for expressions of interest seeking interested candidates to Chair the Working Group.

Vote results<https://gnso.icann.org/sites/default/files/policy/2022/vote-result/gnso-council-motion-recorder-25aug22-en.pdf>

Thank you.

With kind regards,
Terri
            ---
Terri Agnew
Policy Operations Specialist (GNSO)
Internet Corporation for Assigned Names and Numbers (ICANN)
Skype ID:  terri.agnew.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=>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/council/attachments/20220825/5b9d8f08/attachment-0001.html>