September 2023 - council - lists.icann.org

Reminder: Input welcome on GNSO Council agenda for 2023 meetings
by Terri Agnew 29 Sep '23

29 Sep '23

Dear councilors, A reminder to all that a Google doc<https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> is open for all to add their suggestions and comments to the upcoming GNSO Council meeting agendas. This does not have to be in the form of a full agenda item proposal, simple comments and questions are equally welcome! You are welcome to add to the document<https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> via the comments feature. Thank you! Kind regards, Terri Policy Team Supporting the GNSO

1 0

Document and Motion deadline | Sunday, 15 October 2023 at 23:59 UTC for GNSO Council Meeting 25 October at 11:00 UTC
by Terri Agnew 29 Sep '23

29 Sep '23

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Sunday, 15 Otober 2023 at 23:59 UTC) of the GNSO Council Meeting on Wednedsay, 25 October at 11:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/uIXxDg Thank you. Terri

1 0

Revised ALAC-GAC-GNSO Chair's Joint Letter
by John McElwaine 29 Sep '23

29 Sep '23

Dear Councilors, Sebastien, Nico Caballero and Jonathan Zuck had a call last week to discuss the joint ALAC-GAC-GNSO Chairs' letter to the Board regarding the Facilitated Dialogue. Both the ALAC and GAC wanted to state that the status quo should be requested in the second bullet point. That said, the ALAC and GAC understood that the GNSO chair needs to remain neutral on this topic. We have attached a version of the letter reflecting this in the footnote. Keep in mind that this is a joint letter and primarily meant to communicate that work on the Facilitate Dialogue has reached an end but should not in any way delay the next round of new gTLDs. As this letter has been with Council for some time, we would ask that we have your comments, if any, by Thursday (9/28) at 20:00 UTC. Thanks, John [http://www.nelsonmullins.com/img/ecard-logo.png] JOHN C. MCELWAINE PARTNER john.mcelwaine(a)nelsonmullins.com<mailto:john.mcelwaine@nelsonmullins.com> LIBERTY CENTER | SUITE 600 151 MEETING STREET | CHARLESTON, SC 29401 T 843.534.4302 F 843.722.8700 101 CONSTITUTION AVENUE, NW | SUITE 900 WASHINGTON, D.C., 20001 T 202.689.2939 F 202.689.2860 NELSONMULLINS.COM<http://www.nelsonmullins.com> VCARD<http://www.nelsonmullins.com/people/john-mcelwaine/vcard> VIEW BIO<http://www.nelsonmullins.com/people/john-mcelwaine> 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.

5 5

CCWG-AP Letter to Org
by John McElwaine 29 Sep '23

29 Sep '23

Dear Councilors, As you will recall from my agenda item at September's Council Meeting, on 17 July 2023, Xavier Calvez sent a written update<https://mm.icann.org/pipermail/council/2023-August/027220.html> on the progress of ICANN org's implementation of the Cross Community Working Group's - Auction Proceeds (CCWG-AP) Final Report. Specifically, the letter let us know of the Board's intention to direct ICANN org to change the implementation path of the CCWG-AP's Recommendation 7, which was focused on limiting the use of ICANN's accountability mechanisms to challenge individual application decisions made by the independent assessment panel. The CCWG-AP recommended that this limitation should be achieved through changing the ICANN Bylaws on the Reconsideration Request and Independent Review Processes to specify a carve out. Instead of touching ICANN's core accountability mechanisms in the Bylaws, the ICANN Board intends to now direct ICANN org to achieve this recommendation through the applicant terms and conditions that grant applicants will agree to when submitting their grant application. Because the Board is looking to direct ICANN org to implement the CCWG-AP's recommendation to limit access to ICANN's accountability mechanisms in a different manner than the CCWG-AP contemplated, the Board agreed it was important to give advance notice to those CCWG representatives who formed Recommendation 7 and at the same time wanted to provide transparency to the chartering organizations approved the CCWG-AP Final Report and its recommendations. The specific ask was to let ICANN Org know if the GNSO Council was comfortable in having ICANN Org engage with the former CCWG-AP members in this conversation or whether it should be held differently. There was a good discussion on this topic and on the Board's decision to change implementation of Recommendation 7, which we have summarized in the attached letter. If you have any comments or revisions, please provide them in a reply to this email. Kind regards, John [http://www.nelsonmullins.com/img/ecard-logo.png] JOHN C. MCELWAINE PARTNER john.mcelwaine(a)nelsonmullins.com<mailto:john.mcelwaine@nelsonmullins.com> LIBERTY CENTER | SUITE 600 151 MEETING STREET | CHARLESTON, SC 29401 T 843.534.4302 F 843.722.8700 101 CONSTITUTION AVENUE, NW | SUITE 900 WASHINGTON, D.C., 20001 T 202.689.2939 F 202.689.2860 NELSONMULLINS.COM<http://www.nelsonmullins.com> VCARD<http://www.nelsonmullins.com/people/john-mcelwaine/vcard> VIEW BIO<http://www.nelsonmullins.com/people/john-mcelwaine> 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.

4 3

Draft minutes of the Minutes of the GNSO Council Meeting 21 September 2023
by Devan Reed 28 Sep '23

28 Sep '23

Dear Councilors, Attached, please find the draft minutes of the GNSO Council Meeting held on 21 September 2023. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 08 October 2023 Thank you. Kind Regards, Devan

1 0

FYI | FW: [Ext] NEW: ICANN Interim President and CEO Shares Goals for Fiscal Year 2024
by Terri Agnew 28 Sep '23

28 Sep '23

FYI [https://r20.rs6.net/on.jsp?ca=a942ca9e-654e-41ca-a5e1-f5cfeb7db000&a=112202…] Thursday, 28 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=001OChG5v_62nSkkEDl…> 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 · Prep Week Schedule Now Available! · Registration for ICANN78 is Now Open Information Sharing · NEW: ICANN Interim President and CEO Shares Goals for Fiscal Year 2024 · NEW: Join Us in Shaping ICANN's FY26-30 Strategic Plan · NEW: Chair’s Blog: September Board Workshop Recap · NEW: ICANN Seeks Input on Pilot Holistic Review Revised Draft Terms of Reference · NEW: FY23 Report Captures Current State of UA-Readiness in Technology · NEW: ICANN’s “Day of DNS Abuse Discussions” Draws More Than 125 Participants Webinars · TODAY: 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 · TODAY: ccNSO Proposed Policy for a Specific ccTLD Related Review Mechanism · NEW: Pilot Holistic Review Revised Draft Terms of Reference · NEXT WEEK: Proposed Updates to Existing Rights Protection Mechanisms Documentation ICANN78 Prep Week Schedule Now Available! ICANN78 Prep Week will be held from Monday, 9 October, to Wednesday, 11 October. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001OChG5v_62nSkkEDl…> 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=001OChG5v_62nSkkEDl…> to learn more about how to register. Information Sharing NEW: ICANN Interim President and CEO Shares Goals for Fiscal Year 2024 This year, the goals are grouped thematically to focus on specific aspects of fulfilling ICANN's mission. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001OChG5v_62nSkkEDl…> NEW: Join Us in Shaping ICANN's FY26-30 Strategic Plan During this session, ICANN will conduct an environmental scan and identify strengths, weaknesses, opportunities, and threats that will inform its strategic planning efforts. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001OChG5v_62nSkkEDl…> NEW: Chair’s Blog: September Board Workshop Recap Please find the highlights from the September 2023 Board Workshop here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001OChG5v_62nSkkEDl…>. NEW: ICANN Seeks Input on Pilot Holistic Review Revised Draft Terms of Reference The Third Accountability and Transparency Review Team recommended the development of a new Specific Review, the Holistic Review. The ICANN Board approved the review as a pilot, "pursuant to a community-agreed Terms of Reference." Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001OChG5v_62nSkkEDl…> NEW: FY23 Report Captures Current State of UA-Readiness in Technology The information provided in the report can help determine whether your systems are UA-ready and provide the current resources and training materials to address and fix UA-related issues. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001OChG5v_62nSkkEDl…> NEW: ICANN’s “Day of DNS Abuse Discussions” Draws More Than 125 Participants The event's goal was for participants to gain a solid understanding of the proposed obligations and new tools to give them the confidence to support the pending contractual amendments and better combat DNS abuse. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001OChG5v_62nSkkEDl…> Webinars TODAY: 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 #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=001OChG5v_62nSkkEDl…> 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=001OChG5v_62nSkkEDl…> 🔥 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=001OChG5v_62nSkkEDl…>. 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=001OChG5v_62nSkkEDl…>. Public Comment TODAY: ccNSO Proposed Policy for a Specific ccTLD Related Review Mechanism [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001OChG5v_62nSkkEDl…> Open for Submissions: 01 August 2023 Closed for Submissions: 28 September 2023 NEW: Pilot Holistic Review Revised Draft Terms of Reference [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001OChG5v_62nSkkEDl…> Open for Submissions: 28 September 2023 Closed for Submissions: 27 November 2023 NEXT WEEK: Proposed Updates to Existing Rights Protection Mechanisms Documentation [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001OChG5v_62nSkkEDl…> 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=001OChG5v_62nSkkEDl…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001OChG5v_62nSkkEDl…>. Volume 5, Issue 71 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001OChG5v_62nSkkEDl…> | Next Issue: Monday, 02 October 2023 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001OChG5v_62nSkkEDl…>

1 0

FYI | FW: [gnso-chairs] PLEASE READ - ICANN78 Stakeholders/Board sessions | Due by Wednesday 11 October, 2023.
by Terri Agnew 27 Sep '23

27 Sep '23

Hello all, FYI, see below and due by Wednesday 11 October, 2023. Please respond to the council list for staff to send in the questions. Thank you. Kind regards, Terri From: Gnso-chairs <gnso-chairs-bounces(a)icann.org> on behalf of Vinciane Koenigsfeld via Gnso-chairs <gnso-chairs(a)icann.org> Reply-To: Vinciane Koenigsfeld <vinciane.koenigsfeld(a)icann.org> Date: Thursday, September 21, 2023 at 1:25 AM To: "gnso-chairs(a)icann.org" <gnso-chairs(a)icann.org>, "sebastien(a)registry.godaddy" <sebastien(a)registry.godaddy>, "dibiase(a)amazon.com" <dibiase(a)amazon.com>, "john.mcelwaine(a)nelsonmullins.com" <john.mcelwaine(a)nelsonmullins.com> Cc: Matthew Shears <matthew.shears(a)board.icann.org>, Michelle Bright <michelle.bright(a)icann.org>, "becky.burr(a)icann.org" <becky.burr(a)icann.org> Subject: [gnso-chairs] PLEASE READ - ICANN78 Stakeholders/Board sessions Sent on behalf of Tripti Sinha, Chair, ICANN Board of Directors Dear Generic Names Supporting Organization Council Leaders, *Please reply no later than Wednesday 11 October 2023* ICANN78 is right at our doorstep, and the Board and I couldn’t be happier about the opportunity to meet with all of you in Hamburg from October 21st to 26th. This upcoming meeting is not only a chance for us to come together and discuss our common interests, but it’s also a momentous occasion as we celebrate ICANN’s remarkable 25th Anniversary. We’re diligently preparing for the upcoming Annual General Meeting, and we are equally excited about the celebration that awaits. Rest assured, we will share more details with you soon. In the meantime, I want to remind you of the positive changes we initiated during our time in Cancún, which were favorably received: 1. Tailored questions designed to cater to the unique needs of each stakeholder group. 2. A blog that highlighted key takeaways from the ICANN Meeting. 3. Summaries of bilateral sessions included in the Policy Outcomes Report published after the ICANN meeting. In the next few months, we will be suggesting additional improvements that we hope will enhance our partnership’s performance and transparency, all with your satisfaction in mind. Meanwhile though, it is important that we continue listening to your specific needs and therefore here is the question we would like to ask your Group ahead of our joint session in Hamburg: * Looking forward over the next 3 - 5 years, what are the key strategic issues ICANN and the ICANN ecosystem should be addressing in the FY26-30 Strategic plan, and why? We look forward to hearing your thoughts on this soon. We would be grateful if you could send to Board Operations (board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>) the questions you would like the Board to address during our face-to-face meetings. Given the finite time available for these meetings, please list your questions in order of priority. We would also appreciate getting your questions no later than Wednesday 11 October, 2023. Looking forward to engaging discussions and shared celebrations in Hamburg! Best regards, Tripti Sinha Chair, ICANN Board of Directors

1 0

For your information: CPH Nominates Greg DiBiase for GNSO Chair
by Terri Agnew 26 Sep '23

26 Sep '23

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: "Demetriou, Samantha" <sdemetriou(a)verisign.com<mailto:sdemetriou@verisign.com>> Date: Monday, September 25, 2023 at 1:53 PM To: Terri Agnew <terri.agnew(a)icann.org<mailto:terri.agnew@icann.org>>, "aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>" <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>>, "chair(a)rysg.info<mailto:chair@rysg.info>" <chair(a)rysg.info<mailto:chair@rysg.info>> Cc: "secretariat(a)rysg.info<mailto:secretariat@rysg.info>" <secretariat(a)rysg.info<mailto:secretariat@rysg.info>>, "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>, "secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>" <secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>> Subject: Re: Re: [Ext] RE: Please submit names - 25 September deadline | GNSO Chair 2023 Election Timeline Just confirming that the RySG supports Greg’s nomination. Thanks Terri! -- Samantha Demetriou Senior Director - Policy sdemetriou(a)verisign.com<mailto:sdemetriou@verisign.com> 571-455-0668 From: Terri Agnew <terri.agnew(a)icann.org> Date: Monday, September 25, 2023 at 1:45 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: FW: [Ext] RE: Please submit names - 25 September deadline | GNSO Chair 2023 Election Timeline 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.

3 2

ICANN78 prep week schedule is now published / How to Create your Prep Week Schedule
by Julie Bisland 26 Sep '23

26 Sep '23

Dear all, The ICANN78 prep week schedule is now published! Please take a moment to read the information below to help create your prep week schedule and add sessions to your calendar. For the prep week schedule, go here: https://icann78.sched.com/ [icann78.sched.com]<https://urldefense.com/v3/__https:/icann78.sched.com/__;!!PtGJab4!5PS-FK-94…> * Click Sign up or Log in and enter your information (email address and create password) * Once you “Join Event”, the schedule shows up with blank circular buttons to the left of each session. Hover over each button and click “ADD TO MY SCHEDULE” (see screenshot below) or just click in each circle to add the checkmark. [cid:image001.png@01D9F088.207FDF90] * Once you’ve selected all sessions, click the My Schedule link in the lower left corner or hover over your profile and select My Schedule. [cid:image002.png@01D9F088.207FDF90] Or [cid:image003.png@01D9F088.207FDF90] * You will see this message, “A copy of your schedule has been sent to your(a)email.com<mailto:your@email.com>.” To export the schedule, click the Phone icon: [cid:image004.png@01D9F088.207FDF90] * On the page that appears, notice the sections “Mobile” and “Calendar Sync for Google Calendar, Outlook & Apple Calendar”. In the “Calendar Sync …” section, select Export Calendar, and click the link next to “My Schedule”. When the .ics is exported, add it to the appropriate calendar (see screenshots below). Or, after exporting, drag and drop the .ics file directly into your calendar.. [cid:image005.png@01D9F088.207FDF90] [cid:image006.png@01D9F088.207FDF90] The ICANN78 Schedule<https://meetings.icann.org/en/icann78> will be posted 02 October 2023. Please email questions to us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, Policy Team Supporting the GNSO -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 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=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> 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_grou…>

1 0

Jeff's Take on GAC-related issues for ICANN 78 (Long)
by jeff＠jjnsolutions.com 26 Sep '23

26 Sep '23

All, Full credit here to Paul McGrady who asked me a question on what I personally thought the issues for the GAC would be at the upcoming ICANN meeting and what if anything I believed may be subject to GAC advice. I thought I would share this with the full Council list so that you all could have discussions on these issues and be prepared. Please note that my thoughts are based on discussions with the GAC Point of Contact and working on the agenda for ICANN 78. I am not speaking on behalf of the GAC PoC or the GAC as I cannot do that, nor do I have the ability to do so. This is being sent to you all with the huge caveat that everything is subject to change AND I have separated my personal take on the topics in blue. I am going to send out a more comprehensive version of this to the Council shortly before ICANN 78 which has the final agenda for the GAC/GNSO bilateral as well as some potential talking points. Some of these items below will likely be on the GAC/GNSO agenda, but likely not all of them due to time constraints. 1. SubPro Topics: a. Closed Generics - Status on the Facilitated Dialog and the future of Closed Generic discussions / implementation. Jeff's note: If you recall the original draft letter proposed by the GNSO/GAC/ALAC chairs recommended that the Board be instructed to maintain the moratorium on Closed Generics from the last round, but the GNSO discussed removing that from the letter. The GAC has a very strong interest in the issue of Closed Generics and does not believe they should be allowed absent consensus policy on the topic (which of course is developed with GAC input). b. IRT Progress on Next Round - Jeff's take: No known concerns here from GAC, just an update. c. Pending items still not addressed by the Board / Open Issues - PICs / RVCs: Jeff's Take: As most GAC Advice on new gTLDs is implemented as a PIC, or may be implemented as an RVC if Registries respond to Early Warnings or comments, it is important to the GAC that these be incorporated as contractual commitments into the agreements (See ICANN 77 Communique Advice 2(a). GAC agrees that such commitments must be enforceable by ICANN through clear contractual obligations, and that consequences for the failure to meet those obligations should be specified in the relevant agreements with the contracted parties. However, they are looking to understand (as we are) the changes being proposed by the ICANN Board to the language. - Private Auctions: Jeff's take: The GAC has previously expressed on several occasions, including as Advice in its ICANN 77 Communique that, ICANN "ban or strongly disincentivize private monetary means of resolution of contention sets, including private auctions." (ICANN 77 Communique 4(a)(ii). They also do not want to see ICANN auctions of last resort in contention sets involving non-commercial applicants. - Opening up small team to GAC participation (especially for items not accepted by the Board) Jeff's Take: GAC members want to make sure that they are participating in the process to determine both the processes used, as well as the substance, of revisions to recommendations, new recommendations, not pursuing existing recommendations, etc. This is especially true for all of the issues that the GAC has already issued advice on as well as items that they previously deemed were of importance to the GAC. - Applicant Support (more than financial) - Jeff's Take: Not surprisingly and also quite aligned with the GNSO, the GAC issued advice on Applicant Support (ICANN Communique 77, Advice #3). The Applicant Support program to be incredibly important to them and they want to make sure that applicants not only have access to financial assistance with the application, but also assistance in application preparation and ongoing registry management (including potentially a reduction in ICANN ongoing registry fees). They also want to make sure that the program is highly publicized to those that are the intended beneficiaries of the program. - GGP Initial Report - Jeff's Take: I would propose this gets combined with the topic above and may just be an update. - .quebec: Is this an issue for the GAC? Jeff's Take: This issue of course is of interest to the GAC Canadian Reps, but as of today this issue has not gotten on the GAC agenda as a whole. That is not an indication of whether this issue is important or not, there just have not been any GAC-wide discussions on the topic. Because it was discussed within the GNSO Council this week, I raised it at the meeting today and the GAC Point of Contact is going to see if this is an issue for the GAC at this ICANN meeting. 2. IGOs a. Implementation of Curative Rights (what is the status of the IRT) - Jeff's Take: I believe The GAC is supposed to get a briefing at ICANN78 from ICANN on the status of implementation of Curative Rights as well as the Watch Service (see below). They believe that these are must haves before ICANN should consider lifting the reservation of IGO Acronyms. This was in their GAC Communique as advice a couple of meetings ago. They want to discuss this with the GNSO. I do not expect further advice on this unless they affirm their previous advice or if it appears that ICANN is moving in a direction that is inconsistent with the previous GAC Advice. b. Question of Moratorium on IGO acronyms / watch service (which ICANN is supposed to develop) - See Above. 3. Future Policy Work on DNS Abuse? Jeff's Take: The GAC positions on this are well-known. They are supportive of the proposed contract amendments for the Contracted Parties but of course want to see more done on the policy front before the opening up of the next round. But I do not expect any advice here, just more of wanting an update on what is going on and making sure it is progressing. 4. WHOIS / Data Protection a. Access to non-public information / "urgent requests" - Jeff's Take LONG): This relates to the pilot being lunched soon by ICANN with the Registrars. On August 23, 2023, the GAC Chair sent a letter to the ICANN Board (https://www.icann.org/en/system/files/correspondence/caballero-to-sinha-23a…), to express its concerns over the time line to respond to requests in select emergency situations ("Urgent Requests"). They do not like the proposed three (3) business days currently in the EPDP Phase 1 implementation report and want the ICANN Board to reconsider this. On September 8, 2023, the Registrars sent a letter to the ICANN Board (https://www.icann.org/en/system/files/correspondence/heineman-to-sinha-08se…) providing some context to the 3 business days stating that this language has been in the text since September 2021, but in August 2022 the language changed to requiring a response, "no longer than two (2) business days from receipt" which was put out for comment. This was a change from the Implementation Pilot Team without consultation of the full IRT. Once that was published, there were several meetings of the full IRT to come up with a compromise solution. The Compromise language published following the July 24, 2023 meeting, which the Registrars agree with, was: "10.6. For Urgent Requests for Lawful Disclosure, Registrar and Registry Operator MUST respond, as defined in Section 10.7, without undue delay, generally within 24 hours of receipt. 10.6.1. If Registrar or Registry Operator cannot respond to an Urgent Request for Lawful Disclosure within 24 hours, it MUST notify the requestor within 24 hours of receipt of an Urgent Request for Lawful Disclosure of the need for an extension to respond. Registrar or Registry Operator’s extension notification to the requestor MUST include (a) confirmation that it has reviewed and considered the Urgent Request for Lawful Disclosure on its merits and determined additional time to respond is needed, (b) rationale for why additional time is needed, and (c) the time frame it will respond, as required by Section 10.7, which cannot exceed two (2) business days from the time of the initial receipt of the request. 10.6.2. In addition to the extension provided for in Section 10.6.1, if responding to an Urgent Request for Lawful Disclosure is complex, or a large number of requests are received by Registrar or Registry Operator, it MAY extend the time for response up to an additional one (1) business day provided it notifies the requestor within (2) business days from the time of the initial receipt of the request of the updated time frame to respond explaining the need for an additional extension of time. " So according to the registrars, they are only requesting 3 business days if they have notified the requestor within 24 hours that it needs more time and if it needs 3 business days it needs to notify the requestor again within 2 business days from receipt of the original request. Registrars do not agree with the GAC's interpretation that this will always be 3 business days and believes that the GAC should have given the Board the full context. It is my impression that the GAC may believe that because it allows 3 business days that this will become the default. This will be discussed by the GAC at ICANN 78. b. Accuracy Issue and status of DPAs between the Contracted Parties and ICANN (Since this has been the reason for delaying policy work on accuracy). Jeff's Take: Accuracy of Registration data is of utmost importance to the GAC and "remains committed to working within the Accuracy Scoping Team to assess the current state of accuracy under ICANN's contracts." The GAC welcomes the completion of a Data Protection Impact Assessment on a contractual compliance audit that could shed light on the current state of accuracy. Although I believe they were ok with the initial 6-month delay of the Scoping Team work waiting for the DPAs, they are looking for more meaningful updates on where ICANN is with the DPAs . They would like to see policy work ASAP. I am not sure if there will be Advice on this, but it certainly is an issue of importance. 5. SOI: Status of discussions on the representation of undisclosed clients. Jeff's Take: The GAC Is following this one closely and I believe they are aligned more with requiring disclosure of clients that are directly being represented in policy processes. Governments individually generally require full disclosure of clients when they engage in discussions with representatives of industry, the community, etc. Whether there will be advice on this at ICANN 78 or not, I don't think so. But it is an item of importance to them. Other GAC Activities / Issues (Jeff's Take) 1. I discussed the proposed Charter for the Standing Committee on RDRS to help inform the next steps on the SSAD policy recommendations with the GAC PoC today. Specifically I discussed the composition which currently is made up of Councilors and members of the ePDP Phase 2 small team members. from the GAC, I believe Chris Lewis-Evans and Laureen Kapin had a "shared membership." Chris is no longer working with the Public safety working group and is in the private sector. So I am sure being able to appoint a replacement (not an alternate) will be important to them. 2. GAC is having two days of outreach sessions at ICANN 78 during the first weekend. The second day will focus on "emerging technologies" and getting briefings from ICANN Org on Blockchain in general and "alternative naming spaces" with an eye on trying to figure out what, if anything, is the GAC role. 3. GAC is also focused on the IANA Review, especially with respect to Articles 18 and 19 of the Bylaws. (https://www.icann.org/en/announcements/details/icann-board-convenes-second-…). This review is taking a broader look athat includes identifying whether the requirements identified in the IANA contract SOW are still relevant or whether they need changing. This is defined in Section 18.3 of the Bylaws. 4. GAC will be looking at the Proposed Updates to Existing Rights Protection Mechanisms documentation (https://www.icann.org/en/announcements/details/icanns-proposed-updates-to-e…) posted on August 24, 2023. 5. There are a couple of ccTLD items the GAC will discuss including input on ccNSO PDP4 (initial Report on (de-) selection of IDN ccTLDs (https://www.icann.org/en/announcements/details/icann-seeks-input-on-ccnso-p…) and the proposed ccLD related Review mechanism Policy Proposal (https://www.icann.org/en/announcements/details/icann-seeks-input-on-a-speci…).

6 6