August 2023 - council - lists.icann.org

GNSO Council resolutions 24 August 2023
by Terri Agnew 24 Aug '23

24 Aug '23

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/20…> 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-cou…> 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-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 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 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-p…> 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

1 0

Recordings | GNSO Council Meeting | Thursday, 24 August 2023
by Terri Agnew 24 Aug '23

24 Aug '23

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, 24 August 2023 at 13:00 UTC. Audio only: https://icann.zoom.us/rec/play/RxtmVmbXvudaaITfU2bmo7d77LR_cZlSX2Eb_fUmX1MP… Zoom Recording (includes chat, visual and rough transcript). See both tabs on recording page: https://icann.zoom.us/rec/share/DKkfH8duJAFd0R8fn1hqf5d98mxqnUAUCeTwBRLJxd7… The recordings and transcriptions of the calls are posted on the GNSO Calendar page.<https://gnso.icann.org/en/group-activities/calendar> Thank you. With kind regards, Terri

1 0

FYI | FW: [Ext] Starting Soon: Next Term of ICANN Policy Development Accelerator
by Terri Agnew 24 Aug '23

24 Aug '23

FYI [https://r20.rs6.net/on.jsp?ca=ed02ac10-12c6-4477-848d-f2f75bd18053&a=112202…] Thursday, 24 August 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=001P6bMGFqvmTF8xA-E…> 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 · ICANN78 Community Childcare Grants Program Application Now Open · Sign up for the session slot for ICANN78 Fellowship Program participants · Translation Deadlines · Community Regional Outreach Program (CROP) Trip Proposal Submission Deadline for ICANN78 Action Items · 🔥 ACTION ITEM: Policy Transition Program on gTLD Registration Data Launches Expression of Interest Information Sharing · Starting Soon: Next Term of ICANN Policy Development Accelerator · NEW: Applications Now Open: Coalition for Digital Africa DNSSEC Roadshow Project Public Comment · GNSO Guidance Process Applicant Support Guidance Recommendation Initial Report · ccNSO PDP4 Initial Report on the (de-)selection of IDNccTLDs · ccNSO Proposed Policy for a Specific ccTLD Related Review Mechanism ICANN78 Sign up for the session slot for ICANN78 Fellowship Program participants Want to introduce your group’s work to ICANN78 Fellowship Program participants? Sign up for a 15 or 30 minute session on 21-22 October. This outreach session is an opportunity to share information with the fellows and highlight the important work that your group does within ICANN. The deadline to sign up for a slot is 30 August 2023 Link to sign up for available slots [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P6bMGFqvmTF8xA-E…> For any additional questions, please contact ICANN Fellowship Program Manager, Siranush Vardanyan at siranush.vardanyan(a)icann.org<mailto:siranush.vardanyan@icann.org>. Community Regional Outreach Program (CROP) Trip Proposal Submission Deadline for ICANN78 Please see the CROP Procedures and Guidelines [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P6bMGFqvmTF8xA-E…> to determine eligibility. Trips must originate and conclude within the same region and must be taken by someone located in the region where the meeting is taking place SUBMISSION DEADLINE: 01 SEPTEMBER 2023 FY24 CROP Landing Page [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P6bMGFqvmTF8xA-E…> 13 SEPTEMBER 2023 TRANSLATION DEADLINE: If your publication requires translation, please provide the final material(s) to Andrea Glandon<mailto:andrea.glandon@icann.org> by 13 SEPTEMBER. This ensures that there is enough time to translate the publication by the start of the meeting, with the possibility of potential changes. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline to be translated ICANN78 Community Childcare Grants Program Application Now Open The program facilitates in-person participation of community members with children who are 12 years old or younger at ICANN public meetings and eligible ICANN events. APPLICATION DEADLINE: 15 SEPTEMBER 2023 | Application form [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P6bMGFqvmTF8xA-E…> Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P6bMGFqvmTF8xA-E…> Action Items 🔥 ACTION ITEM: Policy Development Accelerator on gTLD Registration Data Launches Expression of Interest The ICANN Policy Development Accelerator creates opportunities for newer ICANN community members to cultivate substantive knowledge on a specific policy topic, while fostering relationships and value in service through connections with experienced ICANN community members. The Policy Development Accelerator will meet monthly via Zoom, from September 2023 to March 2024, and will explore gTLD Registration Data: The Temporary Specification and Beyond. Expression of Interest You can find the Expression of Interest and further information on the Policy Development Accelerator workspace [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P6bMGFqvmTF8xA-E…>. The submission deadline is 23:59 UTC on 31 August 2023. Information Sharing Starting Soon: Next Term of ICANN Policy Development Accelerator The ICANN Policy Development Accelerator provides opportunities for newer ICANN community members to build substantive knowledge on a specific policy topic, while fostering value in service and relationships through connections with experienced ICANN community members. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P6bMGFqvmTF8xA-E…> NEW: Applications Now Open: Coalition for Digital Africa DNSSEC Roadshow Project The goal of this project is to promote the adoption and implementation of DNSSEC protocols to improve the security of African country code top-level domains (ccTLDs). The roadshows are intended to provide ccTLD operators with the tools and expertise they need to protect their infrastructure, maintain user trust, and improve overall Internet security. ccTLD operators that wish to participate in the DNSSEC Roadshows project are requested to submit their application by 23:59 UTC on 30 September 2023. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P6bMGFqvmTF8xA-E…> Public Comment GNSO Guidance Process Applicant Support Guidance Recommendation Initial Report [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P6bMGFqvmTF8xA-E…> Open for Submissions: 31 July 2023 Closed for Submissions: 11 September 2023 ccNSO PDP4 Initial Report on the (de-)selection of IDNccTLDs [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P6bMGFqvmTF8xA-E…> Open for Submissions: 16 August 2023 Closed for Submissions: 27 September 2023 ccNSO Proposed Policy for a Specific ccTLD Related Review Mechanism [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P6bMGFqvmTF8xA-E…> Open for Submissions: 01 August 2023 Closed for Submissions: 28 September 2023 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P6bMGFqvmTF8xA-E…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P6bMGFqvmTF8xA-E…>. Volume 5, Issue 62 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P6bMGFqvmTF8xA-E…> | Next Issue: Monday, 28 August 2023 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P6bMGFqvmTF8xA-E…>

1 0

FW: [gnso-chairs] FW: [Ext] Update on Board review of clarifying statements.
by Sebastien＠registry.godaddy 24 Aug '23

24 Aug '23

Dear Council Colleagues, Please find below the communication Paul and I received from Becky and Avril yesterday and attached the redline prepared by Steve. As indicated by Becky, there are a number of points of then Clarifying Statements which the Board is asking us to hold on while they work on offering wording alternatives for us to review. As you know that Board was in recess until Monday, Becky sent apologies for the very late input. Steve’s edits reflect the request by setting Topics 30 and 31 and most of the Topic 9 Recommendations aside. For us to discuss later today. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_2093298213] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: Gnso-chairs <gnso-chairs-bounces(a)icann.org> on behalf of Steve Chan via Gnso-chairs <gnso-chairs(a)icann.org> Date: Thursday, 24 August 2023 at 12:16 am To: gnso-chairs(a)icann.org <gnso-chairs(a)icann.org> Subject: Re: [gnso-chairs] FW: [Ext] Update on Board review of clarifying statements. Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Dear Sebastian, John, and Greg, Assuming you agree with the approach (Greg, thanks for your comments so far), here is some proposed text to send to the Council, to try and prepare them for action during tomorrow’s meeting. Thanks, Steve Dear Councilors Colleagues, In respect of item 4 and the Council’s SubPro Clarifying Statement, I have some news to share and a proposed path forward. Council leadership and Paul received a note from Avri and Becky (co-leads of the Board SubPro caucus), informing us that the Board wishes to have a little more time to refine the language regarding the enforceability of PICs and RVCs (i.e., the majority of Topic 9 and by implication, Topics 30 and 31). From a leadership perspective, we believe that removing the text in the Clarifying Statement that relates to PICs and RVCs, and having the Council approve what remains, is a pragmatic path forward to allow progress on at least some of the recommendations. Once the Board reverts with suggested refinements to the PICs and RVCs language in the Clarifying Statement, separate Council action can be taken when appropriate. We believe the alternative approach is to delay any action on the Clarifying Statement until all of the language is ready for approval. While it is not ideal to break the Clarifying Statement into two parts, we believe incremental progress is preferred. To be clear, we are proposing that a revised Clarifying Statement (attached as a redlined document), that removes the topics related to PICs and RVCs, be approved by the Council’s meeting on 24 August. While time is allocated for discussion on this item, we do encourage you to voice any concerns you may have on the mailing list. Kindly, Sebastien From: Gnso-chairs <gnso-chairs-bounces(a)icann.org> on behalf of Steve Chan via Gnso-chairs <gnso-chairs(a)icann.org> Reply-To: Steve Chan <steve.chan(a)icann.org> Date: Wednesday, August 23, 2023 at 2:49 PM To: "gnso-chairs(a)icann.org" <gnso-chairs(a)icann.org> Subject: [gnso-chairs] FW: [Ext] Update on Board review of clarifying statements. FYI… From: Becky Burr <becky.burr(a)board.icann.org> Date: Wednesday, August 23, 2023 at 2:48 PM To: "Sebastien(a)registry.godaddy" <Sebastien(a)registry.godaddy> Cc: Paul McGrady <paul(a)elstermcgrady.com>, Steve Chan <steve.chan(a)icann.org>, Lars HOFFMANN <lars.hoffmann(a)icann.org>, Avri Doria <avri.doria(a)board.icann.org> Subject: [Ext] Update on Board review of clarifying statements. Sebastian Ducos, Chair GNSO Council Dear Seb, We wanted to let you know in advance of the Council meeting that the Board’s SubPro Caucus has reviewed the clarifying statements provided by the Council and we are comfortable that all but one of the clarifications address the Board’s concerns. We are still working on and need a little more time on the language regarding the enforceability of PICs and RVCs. The Board would like to propose a small tweak to the language to ensure that it is crystal clear. We will revert with this as soon as possible and apologize for the delay. Best, avri and Becky

5 5

**Starting in 15 minutes | Meeting Invitation | GNSO Council Meeting | Thursday, 24 August 2023 at 13:00 UTC
by Terri Agnew 24 Aug '23

24 Aug '23

**Starting in 15 minutes Dear all, The GNSO Council meeting is scheduled on Thursday, 24 August 2023 at 13: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/0IBXDg Check your time zone: https://tinyurl.com/2h2mdzcd [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2h2mdzcd__;!!PtGJab4!5uF-ruA…> 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/yIBXDg> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind Regards, Terri

1 0

Update on Closed Generics
by John McElwaine 23 Aug '23

23 Aug '23

Dear Councilors, As GNSO Council liaison to the ALAC-GAC-GNSO Facilitated Dialogue on Closed Generic gTLDs, I wanted to update you on the latest developments on this project. On 7 July 2023, after discussions amongst themselves that I also participated in, Sebastien (in his capacity as GNSO Chair), Jonathan Zuck (ALAC Chair) and Nico Caballero (GAC Chair) sent the attached letter to the participants in the dialogue. For reasons set out in the letter, and in response to questions that the dialogue participants had referred to them (also noted in the letter), the three Chairs have collectively decided that it will be neither necessary to continue with the dialogue to develop a final framework nor initiate further policy development work on this topic. The dialogue participants have discussed the Chairs' joint letter and agreed to conclude their work as requested, including producing an outcomes report to ensure that the work to date is thoroughly documented. Participants also agreed to forward the Chairs' letter to all the commenters that submitted input on the draft framework (viz., Tucows, RySG, BC, ISPCPC, ALAC and GAC), and have invited those commenters that wish to engage with the group to join their next call to clarify any significant concerns they raised in the feedback they provided. The staff team that is supporting the dialogue is currently preparing a draft outcomes report for the group to review. The group intends for the outcomes report to serve as an introduction and summary of their work, including expressly clarifying that the draft framework the group published in June 2023 does not reflect agreed outcomes but, rather, was a product of compromise that was reached in the interests of soliciting community feedback on the various elements and points included in the draft framework. The outcomes report will also include all the community feedback that were submitted in full, links to the group's community wiki space and other relevant documentation, and the participants' feedback on the consensus building techniques and approaches that were used for the dialogue. The group hopes to wrap up its work by September, in line with its previous plan to conclude the dialogue and final framework by end-Q3 2023. I understand that Sebastien, Nico and Jonathan will also be sending a separate communication to the ICANN Board that reflects the decision they took and, as stated in the letter, expressing the collective view that: (1) closed generic gTLDs should not be viewed as a dependency for the next round; (2) until there is community-developed policy, the Board should maintain the position from the 2012 round (i.e., any applications seeking to impose exclusive registry access for "generic strings" to a single person or entity and/or that person's or entity's Affiliates (as defined in Section 2.9(c) of the Registry Agreement) should not proceed; and (3) should the community decide in the future to resume the policy discussions, this should be based on the good work that has been done to date in the facilitated dialogue. Sebastien and I will be happy to answer any questions you may have on the letter, the Chairs' decision and the proposed next steps. You may also wish to check in with the representatives that each of your Stakeholder Groups appointed to the dialogue for further information. Finally, I am sure I speak for all of us when I say that we are very grateful to the dialogue participants and the staff support team for all the hard work and consensus building that resulted in a detailed and substantive, if preliminary, draft framework. I also hope that the participants' feedback on the methods and techniques used in the dialogue, as well as other lessons learned from the experience, will provide the GNSO Council and community with useful information that we can put into practice in future policy discussions. Best regards, John Confidentiality Notice This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged, confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately either by phone (800-237-2000) or reply to this e-mail and delete all copies of this message.

9 19

Please read | Upcoming GNSO Council meeting prep 24 August 2023 at 13:00 UTC
by Terri Agnew 23 Aug '23

23 Aug '23

Dear all, A few reminders of prep for the Council meeting 24 August at 13:00 UTC: 1. Please review the GNSO Council meeting Cheat Sheet <https://urldefense.com/v3/__https:/docs.google.com/document/d/1lQ9fqEjD-inZ…> in order to help you prepare for the session and also provide your input in suggestion mode 1. All documents mentioned on the Council agenda<https://community.icann.org/x/0IBXDg> will be listed on the Document wiki page<https://community.icann.org/x/yIBXDg> for easy referral. If there are any topics you would like to see appear on future Council agendas, please do not hesitate to add them to the Council Topics Google doc. <https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> 1. Please consult the Project Management Portfolio<https://community.icann.org/pages/viewpage.action?pageId=150178769>, in particular the Action Decision Radar<https://community.icann.org/x/14vzC> and the Project List<https://community.icann.org/x/1YvzC> . 1. If you fear you may run into connectivity issues or may not make it on the call, please have an officer of your SG/C fill in the Council Absence Notification form<https://www.icann.org/forms/gnso_notification>. Thank you! Kind regards, Terri

1 0

Re: [council] [Ext] RE: Motions for August Meeting
by Terri Agnew 23 Aug '23

23 Aug '23

Hi Susan, No protocol, first come, gets their name down. Do you mind sending an email to council(a)gnso.icann.org<mailto:council@gnso.icann.org> and once I see it, will get you added. Thanks for checking! Terri From: Susan Payne <susan.payne(a)comlaude.com> Date: Thursday, August 17, 2023 at 9:30 AM To: Terri Agnew <terri.agnew(a)icann.org> Subject: [Ext] RE: [council] Motions for August Meeting Hi Terri, is there a protocol to the seconding? I’d be happy to do so for the clarifying statement if needed, but would it be expected that Paul does since he leads the small team? Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image001.png@01D9D0EE.1E3D7BC0][comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!7F10Z9rsMCP2C4…> Follow us on Linkedin [t-uk.xink.io]<https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/pRkAAGVfAADw…> and YouTube [t-uk.xink.io]<https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/bhkAAGVfAADw…> From: council <council-bounces(a)gnso.icann.org> On Behalf Of Terri Agnew via council Sent: Monday, August 14, 2023 10:58 PM To: John McElwaine <john.mcelwaine(a)nelsonmullins.com>; DiBiase, Gregory <dibiase(a)amazon.com>; COUNCIL(a)GNSO.ICANN.ORG Subject: Re: [council] Motions for August Meeting Thank you, John, this is noted for the CSC motion. We still need a seconded by for the Approval of the GNSO Council’s Clarifying Statement Regarding Select Pending SubPro Recommendations motion. Thanks! Terri From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of John McElwaine via council <COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG>> Reply-To: John McElwaine <john.mcelwaine(a)nelsonmullins.com<mailto:john.mcelwaine@nelsonmullins.com>> Date: Monday, August 14, 2023 at 4:41 PM To: "DiBiase, Gregory" <dibiase(a)amazon.com<mailto:dibiase@amazon.com>>, "COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG>" <COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG>> Subject: Re: [council] Motions for August Meeting Dear Councilors, I will second the motion to approve the slate of CSC members. Kind regards, John From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of DiBiase, Gregory via council Sent: Monday, August 14, 2023 5:21 PM To: COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG> Subject: [council] Motions for August Meeting Hi All, Please see the attached agenda which includes a consent agenda (which contains a motion to approve CSC members) as well a regular agenda (which contains a motion to adopt clarifying statements on subpro recommendations). Please let Hi All, Please see the attached agenda which includes a consent agenda (which contains a motion to approve CSC members) as well a regular agenda (which contains a motion to adopt clarifying statements on subpro recommendations). Please let me know if you have any questions. Thanks, Greg Confidentiality Notice This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged, confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately either by phone (800-237-2000) or reply to this e-mail and delete all copies of this message. ________________________________ 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 [comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com__;!!PtGJab4!7F10Z9rsMCP2C4N…>

6 14

REMINDER | Meeting Invitation | GNSO Council Meeting | Thursday, 24 August 2023 at 13:00 UTC
by Terri Agnew 23 Aug '23

23 Aug '23

Dear all, The GNSO Council meeting is scheduled on Thursday, 24 August 2023 at 13: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/0IBXDg Check your time zone: https://tinyurl.com/2h2mdzcd [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2h2mdzcd__;!!PtGJab4!5uF-ruA…> 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/yIBXDg> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind Regards, Terri

1 0

Fwd: [FormerMembersCCWG-AP] Correspondence ICANN - Anne Aikman-Scalese
by Anne ICANN 22 Aug '23

22 Aug '23

Dear Council Leadership and Members, In relation to the AOB item re the ICANN Grant Program that evolved from the Board's approval of the CCWG Auction Proceeds Final Report, ICANN Org has re-established a list of consenting former CCWG members for the purpose of community consultation. As a former CSG voting delegate to the CCWG Auction Proceeds, I posed certain questions after consultation with some CSG members. The questions and ICANN Org's responses to the questions appear below. Notably, no one knows of a procedure in place for the Board to modify a Final Recommendation of a CCWG that the Board has already adopted. So to borrow a term from cricket, that is a bit of a "sticky wicket". I think other Councilors will have further comments on the substance of the proposed solution of private contracting to eliminate resort to Request for Reconsideration and Independent Review as to grant decisions (in lieu of a ByLaws amendment to accomplish this as recommended by the CCWG.) Thank you, Anne Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso(a)gmail.com ---------- Forwarded message --------- From: Negar Conrad <negar.conrad(a)icann.org> Date: Thu, Aug 17, 2023 at 8:33 AM Subject: Re: [FormerMembersCCWG-AP] Correspondence ICANN - Anne Aikman-Scalese To: Anne ICANN <anneicanngnso(a)gmail.com> Cc: FormerMembersCCWG-AP(a)icann.org <FormerMembersCCWG-AP(a)icann.org>, Susan Payne <susan.payne(a)comlaude.com>, Paul McGrady <paul(a)elstermcgrady.com>, lschulman(a)inta.org <lschulman(a)inta.org> Dear Anne, Thank you very much for your note and clarifying questions. Xavier is currently out of office so I’m responding to your email instead. Please see our responses, inline, below. 1. The Board adopted the Final Recommendations of the CCWG Auction Proceeds in June of 2022 and proceeded to instruct ICANN Org to implement. The Board adopted <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> the Final Recommendations of the CCWG on Auction Proceeds on 12 June 2022 and directed ICANN org to take the actions as specified in the accompanying Scorecard <https://www.icann.org/en/system/files/files/scorecard-ccwg-ap-final-recomme…>, and “to ultimately implement an ICANN Grant Giving Program that is aligned with ICANN's mission and based in sound governance practices.” 2. It appears that it was determined that no IRT was necessary in order to proceed. The CCWG did not specify the need for an IRT. 3. The CCWG Guidelines appear to allow for ICANN to proceed to implement in the absence of an IRT being requested by the CCWG. See what I think are the CCWG guidelines at the link below but I am not certain this version is current. (Could you please confirm by reply all?) https://ccnso.icann.org/sites/default/files/file/field-file-attach/2016-12/… [ccnso.icann.org] The CCWG Guidelines are a community document providing a general framework for the establishment, operations and closure of CCWGs. They are not Board approved. Upon consultation with ICANN org colleagues, I understand that the version that you cited is the most recent version, which the GNSO and ccNSO, as chartering organizations to establish this framework, have both adopted. 4. The Board considers the adoption of the Final Recommendation to amend the ByLaws to exempt grant decisions by the independent panel from the Request for Reconsideration and Independent Review Process as being unwieldy and too complicated, causing too much delay. The Board has recommended transactional remedies in the nature of covenant not to sue ICANN for grant applicants. The Board has signaled its intent to maintain the CCWG’s recommendation that grant decisions by the independent panel should be exempted from the Reconsideration and IRP Processes, but that the manner of implementation of that community-based recommendation should be moved into a contract with applicants as opposed to changes to ICANN’s core accountability mechanisms as defined in the Bylaws. 5. Some members of CSG have questioned the procedure and the efficacy of the recommended solution. [Note, this appears to be a statement that does not require confirmation from ICANN.] 6. The CCWG list has been reestablished for the purpose of facilitating dialogue among consenting former members of the CCWG Auction Proceeds, though this is not an attempt to convene an IRT. A mailing list of prior CCWG members that consent to join the list has been established, as one of the communication avenues that ICANN org has planned to keep the community up to date, for the purpose of facilitating updates to the former members in a transparent and publicly archived list. Any dialogue among those former members would be publicly archived as well. Xavier, could we please see the proposed text of the Resolution to override the adopted Final Recommendation of the CCWG Auction Proceeds and could we please know the date at which this Resolution will next be considered by the Board? While the Board has not taken its decision yet, as Tripti noted in her recent email, the Board intends to direct an implementation path that both upholds the CCWG-AP’s recommendation that individual application decisions should not be challenged through ICANN’s accountability mechanisms, while also keeping ICANN’s accountability mechanisms unchanged within the Bylaws. This will also support the CCWG-AP’s intention to to lower complexity and protect the total amount of proceeds available for applicants. The Board is scheduled to further consider this matter in September. The Board’s intended resolution and rationale will detail all of the Board’s motivation for changing the implementation path, including a discussion that the use of contractual terms and conditions as contemplated is a limited and narrow solution that could only be used when there is a community-developed and supported recommendation to limit the usage of ICANN’s accountability mechanisms. Separately, is there a specific procedure applicable to overriding an adopted Final Recommendation of a Cross Community Working Group? We are not aware of a defined process (such as those defined in the Bylaws to govern consideration of recommendations from the GNSO Council’s PDP or a ccPDP) for the consideration of CCWG recommendations. Thank you for your continued interest in this important program and your efforts to help make it a success. Kind regards, Negar Conrad ICANN Director, Implementation Operations *From: *FormerMembersCCWG-AP <formermembersccwg-ap-bounces(a)icann.org> on behalf of Anne ICANN <anneicanngnso(a)gmail.com> *Date: *Monday, August 14, 2023 at 11:29 AM *To: *"erika(a)erikamann.com" <erika(a)erikamann.com> *Cc: *"FormerMembersCCWG-AP(a)icann.org" <FormerMembersCCWG-AP(a)icann.org>, Susan Payne <susan.payne(a)comlaude.com>, Paul McGrady <paul(a)elstermcgrady.com>, "lschulman(a)inta.org" <lschulman(a)inta.org> *Subject: *Re: [FormerMembersCCWG-AP] Correspondence ICANN - Anne Aikman-Scalese Many thanks Xavier and Erika, for continuing this dialogue. In order to be able to brief the CSG on this proposed action, I need to get clarification on the following: 1. The Board adopted the Final Recommendations of the CCWG Auction Proceeds in June of 2022 and proceeded to instruct ICANN Org to implement. 2. It appears that it was determined that no IRT was necessary in order to proceed. 3. The CCWG Guidelines appear to allow for ICANN to proceed to implement in the absence of an IRT being requested by the CCWG. See what I think are the CCWG guidelines at the link below but I am not certain this version is current. (Could you please confirm by reply all?) https://ccnso.icann.org/sites/default/files/file/field-file-attach/2016-12/… [ccnso.icann.org] <https://urldefense.com/v3/__https:/ccnso.icann.org/sites/default/files/file…> 4. The Board considers the adoption of the Final Recommendation to amend the ByLaws to exempt grant decisions by the independent panel from the Request for Reconsideration and Independent Review Process as being unwieldy and too complicated, causing too much delay. The Board has recommended transactional remedies in the nature of covenant not to sue ICANN for grant applicants. 5. Some members of CSG have questioned the procedure and the efficacy of the recommended solution. 6. The CCWG list has been reestablished for the purpose of facilitating dialogue among consenting former members of the CCWG Auction Proceeds, though this is not an attempt to convene an IRT. *Xavier, could we please see the proposed text of the Resolution to override the adopted Final Recommendation of the CCWG Auction Proceeds and could we please know the date at which this Resolution will next be considered by the Board? * *Separately, is there a specific procedure applicable to overriding an adopted Final Recommendation of a Cross Community Working Group? * *I need to be able to confirm the above assumptions and to obtain answers to the above questions in order to advise CSG members and receive instructions on this matter.* Thank you! Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso(a)gmail.com On Thu, Aug 10, 2023 at 7:33 AM Erika Mann <erika(a)erikamann.com> wrote: Thank you Xavier - This is well understood. I will reach out to Ching and either we will forward you something together or I will respond individually. All is fine, Xavier. Hopefully you’re enjoying the summer period. Warm regards, Erika Erika Mann Senior Advisor Covington & Burling erika(a)erikamann.com +32 498 121354 Sent from my iPhone On Aug 10, 2023, at 4:12 PM, Xavier Calvez <xavier.calvez(a)icann.org> wrote: Dear Erika, Thank you for reaching out. I hope all is well. We have shared on this list information about a Board decision being considered but do not have any specific questions to be addressed. However, we welcome any feedback you, Ching, or any former member of the CCWG AP on this list would like to share. We can not speak on behalf of the GNSO but I believe there are members of the GNSO on this list who may be able to help. Thank you. Best, Xavier Xavier Calvez ICANN *SVP Planning and CFO* *12025 Waterfront Drive, Suite 300* *Los Angeles, California 90094* *USA * *Office phone:* +1 310 301 5800 *Cell phone:* +1 805 312 0052 *Skype:* Xavier.calvez.icann *From: *FormerMembersCCWG-AP <formermembersccwg-ap-bounces(a)icann.org> on behalf of Erika Mann <erika(a)erikamann.com> *Date: *Thursday, August 10, 2023 at 4:46 AM *To: *Giovanni Seppia <giovanni.seppia(a)icann.org> *Cc: *"formermembersccwg-ap(a)icann.org" <formermembersccwg-ap(a)icann.org> *Subject: *Re: [FormerMembersCCWG-AP] Correspondence ICANN - Anne Aikman-Scalese Dear Giovanni, dear Xavier - Would you, the board, the GNSO, be interested in receiving from the co-chairs of the former CCWG an informal opinion on the remaining questions? Kind regards, Erika Erika Mann Senior Advisor Covington & Burling erika(a)erikamann.com +32 498 121354 Sent from my iPhone On Aug 10, 2023, at 12:02 PM, Giovanni Seppia <giovanni.seppia(a)icann.org> wrote: Dear former members of the CCWG-AP, As anticipated, please see below the correspondence between ICANN and Anne Aikman-Scalese that occurred during the past weeks. Now that this list has been created, we encourage conversation to continue here. Best, Giovanni *From: *Xavier Calvez <xavier.calvez(a)icann.org> *Date: *Saturday, 5 August 2023 at 02:49 *To: *Anne ICANN *Cc: *XXX *Subject: *Re: [Ext] Re: Message from Tripti Sinha to Former CCWG-AP Members Dear Anne, Thank you for your response below and for further clarifying your view. As you are likely aware, the Board did not yet formally revisit its decision on the CCWG-AP’s recommendation 7. While many of the concerns you raised (or reported on behalf of others) were already part of the Board’s deliberations, the Board wanted to make sure that its intended outreach was complete before acting. As indicated earlier, we intend to share the content of the emails that Tripti, you, and I have exchanged with the newly created list of former CCWG members who have consented to be included to provide visibility to the concerns you have shared and the responses provided. We also intend to further address your points below as a response to the above list, once we will have posted the previous email communication in it (including your email below). These points are addressed within the Board’s rationale for the recommended decision relative to recommendation #7. Thank you again for your interest on this topic and for taking the time to share your thoughts. The communication that is resulting from it helps to ensure that the Board and org remain accountable to the community. Best regards, Xavier Xavier Calvez ICANN *SVP Planning and CFO* *From: *Anne ICANN *Date: *Thursday, July 27, 2023 at 8:24 AM *To: *Xavier Calvez <xavier.calvez(a)icann.org> *Cc: *XXX *Subject: *Re: [Ext] Re: Message from Tripti Sinha to Former CCWG-AP Members Thanks Xavier. As I am a CSG appointed delegate in this matter, I cannot provide a substantive response to your explanation. Based on the feedback received thus far on the CSG mailing list and the GNSO Council list, it appears the timing of this proposed Board Resolution (TODAY?) is quite concerning given that it modifies a Recommendation contained in the CCWG Final Report without adequate prior consultation with the ICANN community. Significant concerns have been raised by some, not only about procedure, but also about the substantive effectiveness of the chosen path. No one is more interested than I in seeing the ICANN Grant Program move forward. I'm sure CSG members feel similarly. Nonetheless, legitimate concerns have been raised about the timing and the methods chosen for modifying a CCWG Recommendation. The actual Resolution language and the timing of the action were not sent in the previous notification. Accordingly, it would seem appropriate to defer any final action on the proposed Resolution to allow for further discussion. Please include this comment on the list you are now establishing and I do give consent for the posting of this and prior comments communicated. ( I have already authorized Giovanni to add me to that list.) Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 On Thu, Jul 27, 2023 at 8:04 AM Xavier Calvez <xavier.calvez(a)icann.org> wrote: Dear Anne, Thank you for your response to Tripti regarding the Board’s anticipated action on the use of ICANN Accountability Mechanisms in the ICANN Grant Program. This message is in response to the email you sent last week (below). I know that Tripti and Maarten are in receipt of your email from yesterday and will share its content with the Board. You raised several points, and I wanted to confirm that the org’s Grant Program Core Team and Steering Committee, as well as the Board, have been carefully considering these items. While the Board has not taken its decision yet, I want to confirm to you that the org and the Board carefully considered and discussed the impact of the original recommendation on both applicants and third parties. As the org team considered the impact of seeking a fundamental Bylaws change that altered the scope of ICANN’s Independent Review Process and the Reconsideration Request Process while making sure that those changes were as narrowly tailored to the CCWG-AP’s recommendations as possible, significant concerns were uncovered. While the amendments would equally impact applicant and third-party access to accountability mechanisms, the contemplated amendments would actually be quite narrow in impact and could create significant loopholes for the use accountability mechanisms by either applicants or third parties to still challenge actions within the Grant Program. The Board’s revised action was reached after evaluating other ways to achieve as much of the CCWG-AP’s intended goal as possible, while also upholding ICANN’s core commitments to accountability and to having its accountability mechanisms remain available. The Board’s resolution and supporting rationale (if adopted) will provide additional detail. As to your notes regarding the limited review opportunities that org is considering within the Grant Program, to the extent such opportunities will be built into the Program, they are currently contemplated to be only for use by the impacted grant applicant, and not for third parties, and will be limited to procedural items that could arise along the path of evaluation of the applicant and application. They are contemplated to be lightweight mechanisms in line with global grant program best practices, and not appeals of issues such as grant amount, as you also caution against. On a procedural note, I want to confirm that the email you received was sent to all former CCWG-AP members. For transparency, we will be moving these communications back onto a publicly archived mailing list, and we think that the issues raised in your email (and our response) are important parts of continuing the dialogue for the benefit of the community. Please indicate if you are willing to be subscribed to the new publicly archived mailing list, and if you agree to us posting your comment and our response within that list. Thank you for your interest on this important program, and your time and efforts offered to the ICANN community to make this program successful. Thank you. Best, Xavier Xavier Calvez ICANN *SVP Planning and CFO* *From: *Anne ICANN *Date: *Thursday, July 20, 2023 at 12:34 PM *To: *Wendy Profit *Cc: *XXX *Subject: *[Ext] Re: Message from Tripti Sinha to Former CCWG-AP Members Many thanks, Tripti. As the former CSG Voting Member to the CCWG Auction Proceeds, I plan to forward this information to CSG members. My personal comment in advance of CSG input would be to note that any new procedural review mechanism adopted by the Board should be "lightweight" and fast. Further, it probably should not be available to challenge the specific amount of any grant, but only for the purpose of a procedural review of a denial of a grant. Nor would it be advisable for anyone to be able to challenge any grant made to another party. The Independent panel mechanism should be sufficient to ensure fairness. (In this regard, it may be advisable to put the proposed limited procedural review mechanism out for public comment. ) Is the Board comfortable that third parties who have not applied for a grant (and thus have not entered into the contractual restriction) would not have grounds to challenge a grant made to someone else by availing themselves of the existing Accountability Mechanisms? ( I think this may be the reason that the CCWG settled on recommending a ByLaws amendment.) As to whether the CCWG should be reconvened for the purpose of designing this procedural review, I'll seek input from the CSG on that question but am not expecting any strong opinions there. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 On Thu, Jul 20, 2023 at 6:24 AM Wendy Profit <wendy.profit(a)icann.org> wrote: *Sending on behalf of ICANN Board Chair, Tripti Sinha…* Dear Former CCWG-AP Members, (in bcc) In follow up to the update email from Xavier Calvez, I am writing to you as Chair of the ICANN Board to update you on the Board’s discussions at its workshop during ICANN77. During this workshop, the ICANN Board discussed with ICANN org how to best implement Recommendation #7 of the Final Report. As a reminder, part of Recommendation #7 stated that ICANN’s existing accountability mechanisms – the Independent Review Process (IRP) or the Reconsideration Process – could not be used to challenge decisions made by the Independent Applications Assessment Panel on individual applications within the Grant Program. To allow this would add unnecessary complexity to the program. Additionally, the total available funding for the program could also be depleted by the cost of such challenges. The CCWG-AP (and the Board as well, as indicated in our June 2022 action on the CCWG-AP’s Final Report) assumed that the best way to restrict the use of ICANN’s accountability mechanisms in this way would be to amend the ICANN Bylaws to create a “carve-out.” This would therefore require a Fundamental Bylaws Amendment. After exploring this issue more in-depth, I am happy to share with you that the Board and ICANN org identified a path that both upholds the CCWG-AP’s recommendation that individual application decisions should not be challenged through ICANN’s accountability mechanisms, while also keeping ICANN’s accountability mechanisms unchanged within the Bylaws. The Board is planning to take action on this later this month; however, I wanted to provide you with a preview. The Board will direct ICANN org to use the contractual terms and conditions required to apply for the Grant Program to obtain applicant agreement that they cannot use ICANN’s accountability mechanisms to challenge any individual decision taken on their application within the ICANN Grant Program. This remains in line with the CCWG-AP’s recommendation regarding the accountability mechanisms as well as the intention to lower complexity and protect the total amount of proceeds available for applicants. When the CCWG-AP made Recommendation #7, it also provided guidance that providing limited opportunity for review of decisions within the Grant Program might also introduce complexity, and encouraged ICANN to not make such opportunities available. However, when considering the inability for applicants to use ICANN’s accountability mechanisms for individual decisions, the ICANN Board will also ask ICANN org to explore whether there are appropriate interim opportunities within the evaluation process for applicants to ask for a limited procedural review. The Board hopes this will enhance ICANN’s accountability to applicants, while following best practices within grant making programs. We are happy to have identified a path forward that preserves the CCWG-AP’s recommendation and enhances accountability to applicants and the wider Internet community. The Bylaws are important to us, and we are confident that we can keep up ICANN’s accountability, as set up, while at the same time limiting the ability to challenge for individual selection decisions. The Board is following ICANN org’s implementation closely and looks forward to seeing this program launch next year. Thank you again for your time and efforts that went into envisioning this exciting program. The establishment of the ICANN Grant Program is a testament to your commitment to the work of the CCWG-AP and is an excellent representation of the multistakeholder model in action. Kind Regards, Tripti Sinha Chair, ICANN Board of Directors _______________________________________________ FormerMembersCCWG-AP mailing list FormerMembersCCWG-AP(a)icann.org https://mm.icann.org/mailman/listinfo/formermembersccwg-ap _______________________________________________ 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. _______________________________________________ FormerMembersCCWG-AP mailing list FormerMembersCCWG-AP(a)icann.org https://mm.icann.org/mailman/listinfo/formermembersccwg-ap _______________________________________________ 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.

1 0