September 2023 - council - lists.icann.org

FW: [Ext] RE: DUE TODAY-Please submit names - 25 September deadline | GNSO Chair 2023 Election Timeline
by Terri Agnew Sept. 26, 2023

Sept. 26, 2023

Dear councilors, Please see below the communication from the Non-Contracted Party House regarding the GNSO Chair candidate nomination. Thank you. Kind regards, Terri Policy Team Supporting the GNSO From: "Cole, Mason (Perkins Coie)" <MCole(a)perkinscoie.com> Date: Tuesday, September 26, 2023 at 10:35 AM To: Andrea Glandon <andrea.glandon(a)icann.org>, Lori Schulman <lschulman(a)inta.org>, "philippe.fouquart(a)orange.com" <philippe.fouquart(a)orange.com>, Johan Helsingius <julf(a)julf.com>, Raoul Plommer <plommer(a)gmail.com>, Benjamin Akinmoyeje <benakin(a)gmail.com>, Brian King <brian.king(a)clarivate.com> Cc: Brenda Brewer <brenda.brewer(a)icann.org>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, Terri Agnew <terri.agnew(a)icann.org> Subject: [Ext] RE: DUE TODAY-Please submit names - 25 September deadline | GNSO Chair 2023 Election Timeline Andrea – On behalf of the NCPH, I report that we will not be advancing a candidate for GNSO Council chair. Please let Julf and me know if you require more in terms of documentation. We are now turning our attention to a vice chair candidate. Thanks – Mason Mason Cole | Perkins Coie LLP INTERNET GOVERNANCE ADVISOR 1120 N.W. Couch Street Tenth Floor D. +1.503.727.2074 E. MCole(a)perkinscoie.com<mailto:%20MCole@perkinscoie.com>

1 0

Action Items - GNSO Council meeting 21 September 2023
by Terri Agnew Sept. 25, 2023

Sept. 25, 2023

Dear Councilors, Please find the action items, as stated during the meeting, below arising from the GNSO Council meeting held on Thursday, 21 September 2023. Please refer to the Action Item page<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> for updates on item completion progress. Please take note of the action items coming out of the Council meeting and the proposed timing for delivering on these actions. Please refer to this page for the recent status updates on the Action items. Please note that actions for all councilors are highlighted below. Item 5: COUNCIL VOTE - Charter for Registration Data Request Service (RDRS) Standing Committee to help inform the next steps on the SSAD policy recommendations (10 minutes) Action Items: 1. The GNSO Secretariat will confirm with the existing EPDP Phase 2 small team members if they are willing to continue as members of the RDRS Standing Committee and/or identify any alternates that may take their place in case of absence. For greater clarity, alternates mean in some cases replacements as required. 2. Prior to the launch of the RDRS Standing Committee, the GNSO Council will identify a Chair. 3. The GNSO Secretariat will reach out to the EPDP Phase 2 ICANN Board liaison and ICANN org liaison to confirm their willingness to continue in their role on the Standing Committee. If not, a new liaison(s) will be requested to be identified. 4. On behalf of the GNSO Council the GNSO Secretariat thanks the EPDP Phase 2 small team for its work to date and appreciates the willingness of its members to continue contributing to this important topic. Item 7: COUNCIL DISCUSSION - SubPro Small Team Updated Assignment Form (20 minutes) Action Items: As there were no questions, comments, or objections the GNSO Council is deemed to have accepted the updated Assignment Form. Item 8: ICANN78 Planning (15 minutes) Action Items: Staff to develop and distribute a list of agreed upon topics for the bilateral GNSO meetings at ICANN78 with At-Large, ccNSO, GAC, and ICANN Board. GNSO Councilors are encouraged to review and suggest additions or revisions. Item 9: Cross Community Working Group - Auction Proceeds Response (20 minutes) Action Items: GNSO Council Leadership to draft a response for Council review to the written update from Xavier Calvez on the progress of ICANN org’s implementation of the Cross Community Working Group’s - Auction Proceeds (CCWG-AP) Final Report, including the concerns expressed during the Council meeting. Item 10: ANY OTHER BUSINESS (20 minutes) 10.1 GNSO Prep Week Webinar - Tuesday - 10 October at 13:00 UTC Action Items: GNSO Councilors should note that attendance at the GNSO Prep Week Webinar is mandatory. 10.4 Review of CCOICI pilot Action Items: The staff support team will work with the Chair of the CCOICI to identify the proposed approach for the review that will be shared with the GNSO Council for its input. 10.6 WS2 Community Coordination Group (CCG) (Manju Chen) Action Items: The Chair of the CCOICI will communicate to the CCOICI that it is expected to continue to assist with any remaining WS2 items from the CCG that may need a Council response or input. NEW 10.7 .québec Issue (Sebastien Ducos) Action Items: Council Leadership to consult with staff to determine the appropriate steps to initiate work on this issue. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

FW: [Ext] RE: Please submit names - 25 September deadline | GNSO Chair 2023 Election Timeline
by Terri Agnew Sept. 25, 2023

Sept. 25, 2023

Dear all, Please find below the Contracted Party House nomination of Greg DiBiase as candidate to the GNSO Chair election. Thank you. Kind regards, Terri Policy Team Supporting the GNSO From: "aheineman(a)godaddy.com" <aheineman(a)godaddy.com> Date: Monday, September 25, 2023 at 1:27 PM To: Terri Agnew <terri.agnew(a)icann.org>, "Demetriou, Samantha" <sdemetriou(a)verisign.com>, "chair(a)rysg.info" <chair(a)rysg.info> Cc: Sue Schuler <secretariat(a)rysg.info>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, Zoe Bonython <secretariat(a)icannregistrars.org> Subject: [Ext] RE: Please submit names - 25 September deadline | GNSO Chair 2023 Election Timeline Hi Terri. Assuming I understand the “assignment” correctly, the RrSG nominates Greg DiBiase for Council Chair.

1 0

FW: [Ext] TOMORROW and THURSDAY: ICANN to Provide RDRS Early Access for Registrars and Supporting Webinars
by Julie Bisland Sept. 25, 2023

Sept. 25, 2023

FYI: From: ICANN Community Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, September 25, 2023 at 10:03 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] TOMORROW and THURSDAY: ICANN to Provide RDRS Early Access for Registrars and Supporting Webinars [https://r20.rs6.net/on.jsp?ca=a9b25cd6-37f8-493b-a1fd-68c3ff05828d&a=112202…] Monday, 25 September 2023 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN organization Policy Development Support function publishes this twice-weekly digest to help ICANN community groups track requests and follow updates. How Domain Name System Policy is Developed, and How You Can Get Involved [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001RmqH_Hz3sUKn6Yzw…> Do you have any ideas for improving the ICANN Community Digest? Write to us at policyinfo(a)icann.org!<mailto:policyinfo@icann.org> Table of Contents ICANN78 · Registration for ICANN78 is Now Open Information Sharing · ICANN Update on AFRINIC Webinars · TOMORROW and THURSDAY: ICANN to Provide RDRS Early Access for Registrars and Supporting Webinars Action Items · 🔥 ACTION ITEM: Calling for NextGen@ICANN Applications for ICANN79 · 🔥 ACTION ITEM: NextGen@ICANN Mentor Program Nominations Public Comment · WEDNESDAY: ccNSO PDP4 Initial Report on the (de-)selection of IDN ccTLDs · THURSDAY: ccNSO Proposed Policy for a Specific ccTLD Related Review Mechanism · Proposed Updates to Existing Rights Protection Mechanisms Documentation ICANN78 Registration for ICANN78 is Now Open Registration is now open for the ICANN78 Annual General Meeting, which will be held both virtually and in-person from 21-26 October 2023 in Hamburg, Germany. ICANN78 will mark the organization's 25th Annual General Meeting. Click here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001RmqH_Hz3sUKn6Yzw…> to learn more about how to register. Information Sharing NEW: ICANN Update on AFRINIC ICANN has been closely following the legal proceedings in Mauritius involving the African Network Information Centre (AFRINIC), one of five RIRs, and AFRINIC's governance struggles. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001RmqH_Hz3sUKn6Yzw…> Webinars TOMORROW and THURSDAY: ICANN to Provide RDRS Early Access for Registrars and Supporting Webinars ICANN will host two webinars to go over early access and answer any questions registrars might have. Webinar #1: Tuesday, 26 September 2023 at 01:00 UTC for 60 minutes Webinar #2: Thursday, 28 September 2023 at 15:00 UTC for 60 minutes Read more and find the links to register here. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001RmqH_Hz3sUKn6Yzw…> Action Items 🔥 ACTION ITEM: Calling for NextGen@ICANN Applications for ICANN79 ICANN wants to hear from university students living and studying in the North American region who are interested in the future of the Internet and in participating in the ICANN79 Community Forum Meeting. ICANN79 is scheduled to be held in San Juan, Puerto Rico from 2–7 March 2024. Application Deadline: 13 October 2023 Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001RmqH_Hz3sUKn6Yzw…> 🔥 ACTION ITEM: NextGen@ICANN Mentor Program Nominations The NextGen@ICANN Program seeks nominations for the 2024 Mentor Program. This appointment will serve for the ICANN79, ICANN80, and ICANN81 meetings. Nominations must be submitted no later than Friday, 1 November 2023. The community-nominated mentor will be responsible for overseeing the mentor process. Communities may choose to appoint program alumni and are encouraged to appoint active community members who have an interest in mentoring students. Guidelines for the program can be found here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001RmqH_Hz3sUKn6Yzw…>. Interested community groups should select their respective volunteers and notify Deborah Escalera, deborah.escalera(a)icann.org [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001RmqH_Hz3sUKn6Yzw…>. Public Comment WEDNESDAY: ccNSO PDP4 Initial Report on the (de-)selection of IDN ccTLDs [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001RmqH_Hz3sUKn6Yzw…> Open for Submissions: 16 August 2023 Closed for Submissions: 27 September 2023 THURSDAY: ccNSO Proposed Policy for a Specific ccTLD Related Review Mechanism [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001RmqH_Hz3sUKn6Yzw…> Open for Submissions: 01 August 2023 Closed for Submissions: 28 September 2023 Proposed Updates to Existing Rights Protection Mechanisms Documentation [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001RmqH_Hz3sUKn6Yzw…> Open for Submissions: 24 August 2023 Closed for Submissions: 03 October 2023 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001RmqH_Hz3sUKn6Yzw…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001RmqH_Hz3sUKn6Yzw…>. Volume 5, Issue 70 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001RmqH_Hz3sUKn6Yzw…> | Next Issue: Thursday, 28 September 2023 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001RmqH_Hz3sUKn6Yzw…>

1 0

FW: [gnso-chairs] [ECAdmin] Secretary's Notice to the Empowered Community
by DiBiase, Gregory Sept. 22, 2023

Sept. 22, 2023

Dear Councilors, Please see the ICANN Secretary's notice to the Empowered Community that the Board has 1) approved amendments to both standard and fundamental bylaws and 2) NomCom bylaws have been proposed for adoption. As a reminder, the following guideline was developed in 2019 by the GNSO to map out the expected steps in relation to Annex D, Article 1, Procedure for exercise of the EC’s rights to approve approval actions: https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-a…. Specifically pages 6-9 map out the expected next steps and timeline. There will be further communications prior to the next Council meeting, including information regarding an Approval Action Community Forum. Thanks, Greg From: Gnso-chairs <gnso-chairs-bounces(a)icann.org> On Behalf Of John Jeffrey via Gnso-chairs Sent: Friday, September 15, 2023 6:07 PM To: ecadmin(a)icann.org; aso-chairs(a)aso.icann.org; Jonathan Zuck <JZuck(a)innovatorsnetwork.org>; Alejandra Reynoso <alejandra.reynoso(a)cctld.gt>; sebastien(a)registry.godaddy; gnso-chairs(a)icann.org; Nicolas Caballero <nicustkd(a)gmail.com> Cc: Tripti Sinha <tripti.sinha(a)board.icann.org>; Sally Costerton <sally.costerton(a)icann.org> Subject: [EXTERNAL] [gnso-chairs] [ECAdmin] Secretary's Notice to the Empowered Community CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Greetings, Attached please find the following Secretary’s Notice(s) to the Empowered Community: * Notice of Board Approval of Fundamental Bylaws Amendments * Notice of Board Approval of ICANN Standard Bylaws Amendments * NomCom Bylaws Proposed for Adoption – August 2023 Sent on behalf of John Jeffrey. Best, Peg -- Peg Rettino (she/her) Project Specialist & Executive Assistant to John Jeffrey ICANN 12025 Waterfront Dr, Ste 300 Los Angeles, CA 90094

1 0

GNSO Council resolutions 21 September 2023
by Terri Agnew Sept. 22, 2023

Sept. 22, 2023

Dear all, Please find below the resolutions from the GNSO Council meeting on Thursday, 21 September 2023, which will be posted shortly on the GNSO Council resolutions <https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/20…> page. 20230921-1 Motion to adopt the recommendations of the Council Committee for Overseeing and Implementing Continuous Improvement in relation to the review of the GNSO Statement of Interest (SOI) requirements - (WITHDRAWN) Submitted by Manju Chen Seconded by Desiree Miloshevic Whereas, 1. The CCOICI tasked<https://community.icann.org/display/CCFOICI/b.+Assignment> the GNSO Statement of Interest (SOI) Task Force (TF) to address the following questions: * Is the original objective of the SOI, as stated in the BGC WG Report, still valid? If not, why not and what should the current objective be? * Based on the response to question 1), is the requested information to be provided as part of the SOI still fit for purpose? If not, why not, and what would need to be changed to make it fit for purpose? * Are there any further measures that should be considered from an enforcement / escalation perspective, in addition or instead of those already included in the requirements? 2. The TF commenced its deliberations in February 2022, submitting the TF Recommendations Report<https://mm.icann.org/pipermail/gnso-ccoici/attachments/20230427/565584b7/GN…> to the CCOICI on 27 April 2023. As the TF was not able to achieve full consensus on one essential element of its recommendations, namely whether there should be an exemption for those prevented by professional ethical obligations to disclose who they are representing in a specific effort, it recommended the CCOICI take on responsibility for resolving this specific issue as all other recommendations had achieved full consensus. 3. The CCOICI took up this issue in May of 2023 and considered it in detail as outlined in Annex A of the CCOICI Recommendations Report<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/chen-…>. As the CCOICI was not able to resolve the different positions on the exemption language, the CCOICI agreed to revert to the current, existing exemption language in the SOI to allow the Council to consider all the other recommendations as outlined in section 2 and 3 of the CCOICI Recommendations Report. These recommendations achieved full consensus of the TF as well as the CCOICI. 4. The CCOICI submitted its Recommendations Report<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/chen-…> to the GNSO Council on 14 August 2023. 5. The GNSO Council considered<https://gnso.icann.org/sites/default/files/policy/2023/presentation/present…> the CCOICI Recommendations Report during its August 2023 meeting. Resolved, 1. The GNSO Council adopts the recommendations as outlined in section #2 (SOI Recommendations) and #3 (Proposed Updates to the GNSO Operating Procedures), with the caveat that the proposed updates to the GNSO Operating Procedures will not be implemented until resolved #2 and #3 have been completed. 2. The GNSO Council requests that the GNSO Policy Development Support Staff develop a proposed implementation plan for these recommendations, recognising that exploring the technical options as well as the transition needs careful consideration. 3. The GNSO Council will consider the proposed implementation plan and as part of that consideration confirm when the proposed updates to the GNSO Operating Procedures are expected to take effect. 4. The GNSO Council thanks the members of the GNSO SOI TF as well as the CCOICI for its work. Vote results<https://gnso.icann.org/sites/default/files/policy/2023/vote-result/gnso-cou…> 20230921-2 Motion to adopt the Charter for a Registration Data Request Service (RDRS) Standing Committee to help inform the next steps on the SSAD policy recommendations Submitted by Sebastien Ducos Seconded by Osvaldo Novoa (updated with the friendly amendment proposed by Stephanie Perrin and accepted by Sebastien Ducos and Osvaldo Novoa) Whereas, 1. On 24 September 2020, the Generic Names Supporting Organization Council (GNSO Council or Council) voted to approve<https://gnso.icann.org/en/council/resolutions/2020#20200924-2> all of the recommendations in its Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phas…> on the Expedited Policy Development Process on the Temporary Specification for gTLD Registration Data (EPDP) Phase 2. 2. On 25 March 2021, the ICANN Board directed the President and CEO<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> in office at the time, or their designee(s), to proceed with the Operational Design Phase (ODP) for GNSO Council-approved recommendations 1-18 from the EPDP Phase 2 Final Report on the System for Standardized Access/Disclosure (SSAD). 3. On 25 January 2022, ICANN organization (ICANN org) published its Operational Design Assessment<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> (ODA) of the SSAD. 4. On 4 April 2022, the Phase 2 Expedited Policy Development Process on the Temporary Specification for gTLD Registration Data Small Team (Small Team), which the GNSO Council tasked to assess the ODA, delivered its Preliminary Report<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/ducos…> to the GNSO Council, recommending a "proof of concept" approach. 5. The GNSO Council and the ICANN Board consulted regarding the next steps for the SSAD and the GNSO Council requested on 27 April 2022<https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-…> that the ICANN Board pause its consideration of the recommendations concerning the SSAD while work continues on a "proof of concept". 6. On 13 September 2022, ICANN org published a WHOIS Disclosure System (System) Design Paper<https://www.icann.org/en/system/files/files/whois-disclosure-system-design-…> based on the "proof of concept" approach outlined by the Small Team. 7. The GNSO Council informed the ICANN Board on 17 November 2022<https://www.icann.org/en/system/files/correspondence/ducos-to-sinha-17nov22…> that the Council unanimously accepted the Addendum to the Preliminary Report<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/ducos…> (Addendum) prepared by the Small Team and supported the implementation of the System. 8. On 27 February 2023, the ICANN Board directed<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> ICANN org to “proceed to develop and launch the System as soon as possible”. The ICANN Board also “directed ICANN org to continue to engage with the Phase 2 Small Team throughout the development and operation of the System, and ensure periodic publication of the collected usage data, once operational". 9. On 15 March 2023, GNSO Council instructed<https://gnso.icann.org/sites/default/files/policy/2023/minutes/minutes-gnso…> the small team to continue working with ICANN org on the implementation of the System as well as “provide the Council with a recommendation on the approach and format through which, following implementation of the system, data should be reviewed and analyzed to help inform subsequent decisions on how to proceed with the SSAD recommendations”. 10. On 7 September 2023, the small team shared<https://mm.icann.org/pipermail/council/2023-September/027247.html> with the GNSO Council the proposed charter for a Registration Data Request Service (RDRS) Standing Committee to help inform the next steps on the SSAD policy recommendations. 11. The GNSO Council considered the proposed charte<https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-rdrs-sta…>r during its meeting on 21 September 2023. Resolved, 1. The GNSO Council adopts the Charter for the Registration Data Request Service (RDRS) Standing Committee to help inform the next steps on the SSAD policy recommendations (see https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-rdrs-sta…) 2. Prior to the launch of the RDRS Standing Committee, the GNSO Council will identify a Chair. 3. The GNSO Council requests the GNSO Secretariat to confirm with the existing EPDP Phase 2 small team members if they are willing to continue as members of the RDRS Standing Committee and/or identify any alternates that may take their place in case of absence. For greater clarity, alternates mean in some cases replacements as required. Similarly, the GNSO Secretariat will reach out to the existing ICANN Board liaison and ICANN org liaison to confirm their willingness to continue in their role on the Standing Committee. If not, a new liaison(s) will be requested to be identified. 4. The GNSO Council expects that the RDRS Standing Committee will become operational upon the moment of the public RDRS launch. Until that time, the EPDP Phase 2 small team is expected to continue its engagement with the ICANN org team, as necessary, in fulfillment of its assignment. Upon the public launch of RDRS, the EPDP Phase 2 small team will cease to exist. Any remaining activities at that point will transition to the RDRS Standing Committee. 5. The GNSO Council thanks the EPDP Phase 2 small team for its work to date and appreciates the willingness of its members to continue contributing to this important topic. Vote results<https://gnso.icann.org/sites/default/files/policy/2023/vote-result/gnso-cou…> 20230921-3 Approval of the GNSO Council’s Clarifying Statement Regarding Select Pending SubPro Recommendations (DEFERRED to the October 2023 meeting) Submitted by Greg DiBiase Seconded by 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-rep…> 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-acti…>, 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-acti…> 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-…> 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 first Clarifying Statement<https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-subpro-p…> 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 GNSO Council approved the first Clarifying Statement<https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-subpro-p…> durings its August 2023 meeting. 10. The ICANN Board’s SubPro caucus shared feedback on the recommendations relating to the enforceability of PICs and RVCs with the Council’s SubPro Pending Recommendations small team; the small team subsequently finalized the Council’s second Clarifying Statement (add link when available). 11. As with the first Clarifying Statement, this second Clarifying Statement should also 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 second Clarifying Statement (add link when available) 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-cou…> Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

Recordings | GNSO Council Meeting | Thursday, 21 September 2023
by Terri Agnew Sept. 21, 2023

Sept. 21, 2023

Dear all, Please find below the audio recording and zoom recording (audio, visual, rough transcript, and chat) of the GNSO Council Meeting that took place on Thursday, 21 September 2023 at 21:00 UTC. Audio only: https://icann.zoom.us/rec/play/Rfsx1AhVad3fr_nkuHDMgElryQBocYuo-4hrKD0e5IZX… Zoom Recording (includes chat, visual and rough transcript). See both tabs on recording page: https://icann.zoom.us/rec/share/NsXTXKFQ9BuckOpWO4FCl7PIYqb4oV06nilRZB9XR9J… The recordings and transcriptions of the calls are posted on the GNSO Calendar page. [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> Thank you. With kind regards, Terri

1 0

GNSO Council Absence Notification Form: Farell Folly
by GNSO Council via ICANN Sept. 21, 2023

Sept. 21, 2023

Full Name of Officer: Julf Helsingius Officer Email Address: julf(a)julf.com Date Prepared: 21 September 2023 GNSO Organization: Non-Commercial Stakeholder Group Officer Position or Title: Chair Name of Absent Councilor: Farell Folly Voting Remedy: Proxy Proxy Information Reason(s) for or condition(s) leading to the remedy: If Farell can't join, proxy is assigned to Manju Chen Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: Council meeting Date upon which the remedy will expire or terminate: 22 September 2023 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). Yes Full Name of GNSO Councilor Serving as Voting Proxy: Manju Chen By submitting my personal data, I agree that my personal data will be processed in accordance with the ICANN Privacy Policy [1], and agree to abide by the website Terms of Service [2]. I Agree [1] https://www.icann.org/privacy/policy [2] https://www.icann.org/privacy/tos

1 0

**Starting in 15 minutes | Meeting Invitation | GNSO Council Meeting | Thursday, 21 September 2023 at 21:00 UTC
by Terri Agnew Sept. 21, 2023

Sept. 21, 2023

**Starting in 15 minutes Dear all, The GNSO Council meeting is scheduled on Thursday, 21 September 2023 at 21:00 UTC for 2 hours. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki Agenda page: https://community.icann.org/x/r4XxDg Check your time zone: https://tinyurl.com/3h2a9edd <https://urldefense.com/v3/__https:/tinyurl.com/3h2a9edd__;!!PtGJab4!4zO3261…> . Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please click the link below to join the webinar: https://icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/97891627902?pwd=RURCTiti…> Passcode: 5d$X0$^0L2 If joining Zoom via Zoom App the following will be required: Webinar ID: 978 9162 7902 Passcode: 9844091488 One tap mobile : US: +13126266799,,97891627902#,,,,*9844091488# or +13017158592,,97891627902#,,,,*9844091488# If you are joining via audio only: Dial(for higher quality, dial a number based on your current location): US: +1 312 626 6799 or +1 301 715 8592 or +1 929 436 2866 or +1 253 215 8782 or +1 346 248 7799 or +1 669 900 6833 or 877 853 5247 (Toll Free) or 888 788 0099 (Toll Free) or 833 548 0276 (Toll Free) or 833 548 0282 (Toll Free) International numbers available: https://icann.zoom.us/u/abaexQvkCI <https://urldefense.com/v3/__https:/icann.zoom.us/u/abaexQvkCI__;!!PtGJab4!4…> Observers are welcome to join, they will be in a read-only and listen-only mode. Please note that all documents<https://community.icann.org/x/rIXxDg> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind Regards, Terri

1 0

GNSO Council Absence Notification Form: Bruna Martins dos Santos
by GNSO Council via ICANN Sept. 21, 2023

Sept. 21, 2023

Full Name of Officer: Julf Helsingius Officer Email Address: julf(a)julf.com Date Prepared: 21 September 2023 GNSO Organization: Non-Commercial Stakeholder Group Officer Position or Title: Chair Name of Absent Councilor: Bruna Martins dos Santos Voting Remedy: Proxy Proxy Information Reason(s) for or condition(s) leading to the remedy: Bruna Martins dos Santos is unable to attend. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: Council meeting September 21 Date upon which the remedy will expire or terminate: 22 September 2023 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). Yes Full Name of GNSO Councilor Serving as Voting Proxy: Stephanie Perrin By submitting my personal data, I agree that my personal data will be processed in accordance with the ICANN Privacy Policy [1], and agree to abide by the website Terms of Service [2]. I Agree [1] https://www.icann.org/privacy/policy [2] https://www.icann.org/privacy/tos

1 0