- council - lists.icann.org

Consent Agenda for July Meeting
by DiBiase, Gregory 09 Jul '24

09 Jul '24

Dear Councilors, Please see the proposed consent agenda for our July meeting (attached). Thanks, Greg

3 2

LAST REMINDER | Document and Motion deadline | Monday, 08 July 2024 at 23:59 UTC for GNSO Council Meeting 18 July 2024 at 13:00 UTC
by Terri Agnew 08 Jul '24

08 Jul '24

Dear all, Reports, motions, and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 08 July 2024 at 23:59 UTC) for the GNSO Council Meeting on Thursday, 18 July 2024 at 13:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Motions Wiki at: https://community.icann.org/x/IIDKF Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

FW: [Ext] NEW: Nomination Period Open for the Dr. Tarek Kamel Award
by Julie Bisland 08 Jul '24

08 Jul '24

FYI-- From: ICANN Community Digest <digest(a)icann.ccsend.com> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, July 8, 2024 at 10:01 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] NEW: Nomination Period Open for the Dr. Tarek Kamel Award [https://danh45uab.cc.rs6.net/on.jsp?ca=26366c8a-51ed-4320-8e2d-27655aa876cf…] Monday, 08 July 2024 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. Click Here to Learn More about the RDRS Pilot Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001dEHO3XW…> 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 Information Sharing · NEW: 2024 WASIG (West Africa School of Internet Governance) and WAIGF (West Africa Internet Governance Forum) Action Items · ICANN Opens Nomination Period for Dr. Tarek Kamel Award for Capacity Building Public Comment · Han Script Single Character IDN Generic Top-Level Domains · IRP-IOT – Proposed updates to the IRP Supplementary Procedure Information Sharing NEW: 2024 WASIG (West Africa School of Internet Governance) and WAIGF (West Africa Internet Governance Forum) Date: Sunday 7 July 2024 (07:00 UTC) - Saturday 13 July 2024 (07:00 UTC) Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001dEHO3XW…> Action Items ICANN Opens Nomination Period for Dr. Tarek Kamel Award for Capacity Building The ICANN Board will evaluate a shortlist of candidates and determine the recipient of this year's award. Please submit nominations via this nomination form [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001dEHO3XW…>by 29 July 2024 23:59 UTC. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001dEHO3XW…> Public Comment Han Script Single Character IDN Generic Top-Level Domains [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001dEHO3XW…> Open for Submissions: 27 June 2024 Closed for Submissions: 16 August 2024 IRP-IOT – Proposed updates to the IRP Supplementary Procedures [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001dEHO3XW…> Open for Submissions: 03 July 2024 Closed for Submissions:16 September 2024 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001dEHO3XW…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001dEHO3XW…>. Volume 6, Issue 50 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001dEHO3XW…> | Next Issue: Thursday, 11 July 2024 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001dEHO3XW…>

1 0

FW: RySG elections - GNSO Council
by Julie Bisland 08 Jul '24

08 Jul '24

Dear all, See the updated information below from the RySG. Best regards, Julie -- Julie Bisland Policy Team Supporting the GNSO From: Sue Schuler <secretariat(a)rysg.info> Date: Monday, July 8, 2024 at 9:27 AM To: GNSO-Secs <gnso-secs(a)icann.org> Subject: RySG elections - GNSO Council The RySG has held their elections, and we are pleased to announce our selections for GNSO Council: Nacho Amadoz - EU Samantha Demetriou - NA Have a great day! -- Sincerely, Sue Schuler RySG Secretariat

1 0

Proposed Agenda | GNSO Council Meeting | Thursday, 18 July 2024
by Terri Agnew 08 Jul '24

08 Jul '24

Dear all, Please find below the final proposed agenda for the GNSO Council Meeting taking place on Thursday, 18 July 2024 at 13:00 UTC for 2 hours This has been posted on the agenda wiki page<https://community.icann.org/x/CYDyEg>. Thank you. Kind regards, Terri Policy Team Supporting the GNSO GNSO Council Agenda 18 July 2024 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/IoDKF. This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 15 March 2023. For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting on Thursday, 18 July 2024 at 13:00 UTC: https://tinyurl.com/mud7kn9k 06:00 Los Angeles; 09:00 Washington DC; 14:00 London; 15:00 Paris; 16:00 Moscow; 23:00 Melbourne GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09 Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1: Administrative Matters (5 minutes) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes<https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso…> of the GNSO Council Meeting on 16 May 2024 were posted on 01 June 2024. Minutes<https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso…> of the GNSO Council Meeting on 12 June 2024 were posted on 01 July 2024. Item 2: Opening Remarks / Review of Projects & Action List (0 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List<https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (5 minutes) * GNSO PR Officer - Roles & Responsibilities * Confirmation of GNSO nominees to the Pilot Holistic Review Item 4: COUNCIL DISCUSSION - EPDP on Temporary Specification Phase 1 Urgent Requests (20 minutes) On 18 May 2019, the ICANN Board adopted the Temporary Specification for gTLD Registration Data<https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#temp…> to enable contracted parties to continue to comply with existing ICANN contractual requirements and community-developed policies as they relate to registration directory services. The GNSO Council initiated a one-year policy development process to confirm whether or not the Temporary Specification should become a consensus policy, and whether it provided an enduring framework for complying with the European Union’s General Data Protection Regulation (GDPR). The EPDP Team sent its Phase 1 Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld…> to the GNSO Council on 20 February 2019, and the GNSO Council voted to approve the Final Report on 4 March 2019. The Board subsequently adopted the Phase 1 Final Report on 15 May 2019, with the exception of Recommendation 1, Purpose 2, and Recommendation 12, which the Board did not adopt in full. The Board directed the ICANN President and CEO or their designee(s) to implement the policy recommendations. ICANN org convened an Implementation Review Team, which began meeting in May 2019. ICANN org published the draft Registration Data Policy for public comment<https://www.icann.org/en/public-comment/proceeding/registration-data-consen…> on 24 August 2022. Several commenters expressed dissatisfaction with the implementation of Recommendation 18, specifically around the issue of the response timeline for urgent requests. The relevant portion of Recommendation 18 reads, “A separate timeline of [less than X business days] will considered [sic] for the response to ‘Urgent’ Reasonable Disclosure Requests, those Requests for which evidence is supplied to show an immediate need for disclosure [time frame to be finalized and criteria set for Urgent requests during implementation].” Following the public comment period and subsequent discussion by the Implementation Review Team, the Governmental Advisory Committee (GAC) wrote to the Board about the topic of urgent requests on 23 August 2023<https://www.icann.org/en/system/files/correspondence/caballero-to-sinha-23a…>. The Registrar Stakeholder Group wrote to the Board on 8 September 2023<https://www.icann.org/en/system/files/correspondence/heineman-to-sinha-08se…> in response to the GAC’s letter. Following the receipt of these letters and further communication amongst Board members, the Board sent a letter to the GNSO Council on 3 June 2024<https://gnso.icann.org/sites/default/files/policy/2024/correspondence/sinha…>, expressing its concerns with the text of Recommendation 18 related to urgent requests. Here, the GNSO Council will discuss the concerns raised in the Board’s letter and discuss next steps in light of the concerns. 4.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 4.2 - Council Discussion 4.3 - Next Steps Item 5: COUNCIL DISCUSSION - Accuracy Check-in (20 minutes) The Registration Data Accuracy (RDA) Scoping Team was initiated by the GNSO Council in July 2021 per the formation instructions<https://gnso.icann.org/sites/default/files/file/field-file-attach/registrat…>. The Scoping Team completed Assignment #1 (enforcement and reporting) and Assignment #2 (measurement of accuracy) and submitted its write up<https://mm.icann.org/pipermail/council/2022-September/025950.html> to the Council on 5 September 2022. In its write up, the Scoping Team suggested moving forward with two proposals that would not require access to registration data, namely a registrar survey (recommendation #1) and a possible registrar audit (recommendation #2) that may help further inform the team’s work on assignment #3 (effectiveness) and #4 (impact & improvements), while it awaits the outcome of the outreach to the European Data Protection Board (EDPB) by ICANN org in relation to proposals that would require access to registration data (recommendation #3). On 19 October 2023, ICANN org provided an update<https://mm.icann.org/pipermail/council/2023-October/027397.html> on Registration Data Accuracy efforts, in which it noted limitations and concerns with proceeding with the Scoping Team’s recommendation #1 (voluntary registrar survey) and registrar audit (recommendation #2). The Council voted to extend the deferral<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…> of the Accuracy Scoping Team’s recommendations by another six months during its meeting on 15 February 2024. During this meeting, the Council agreed to check in on the progress of these items during its June 2024 meeting. Following the ICANN80 GNSO Council Wrap-Up<https://icann80.sched.com/event/1dr4t/gnso-council-wrap-up>, the GNSO Council Chair asked Councilors to consider the following questions: 1. Evaluation of Proposed Alternatives: In its [gnso.icann.org]write-up [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>, ICANN noted limitations in processing data for the purpose of assessing accuracy and proposed two alternatives (analyzing historical audit data and engagement with Contracted Parties on ccTLD practices – see detail below). Is pursuing these alternatives worthwhile? If not, are there other alternatives for obtaining data Council should consider? 2. Consideration of Scoping Team Restart: Given the limitations with respect to access to data, would there be value in restarting the Scoping Team at this time? 3. Advancing the Topic: If restarting the Scoping Team at this time is not deemed advisable, what other ideas do you have to advance this topic given its importance to the ICANN community? Here, the Council will discuss the above questions and determine next steps. 5.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 5.2 - Council Discussion 5.3 - Next Steps Item 6: COUNCIL DISCUSSION - GNSO Review of GAC Communiqué (10 minutes) Following the GAC’s publication of its Communiqué, a small group of GNSO Councilors closely reviews the contents of the Communiqué and provides additional draft guidance to the ICANN Board, where appropriate. Following this review, the small team provides its draft guidance to the GNSO Council for further feedback and approval before sending it to the ICANN Board. Here, the Council will receive an update on the expected contents of the GNSO Council’s Review of the ICANN80 GAC Communiqué<https://gac.icann.org/contentMigrated/icann80-kigali-communique#:~:text=ICA….>. 6.1 - Introduction of Topic (Jeff Neuman, GNSO Council Liaison to the GAC) 6.2 - Council Discussion 6.3 - Next Steps Item 7: COUNCIL DISCUSSION - Update from Small Team Plus on Singulars/Plurals (10 minutes) In March 2023, the ICANN Board approved the majority of the recommendations contained in the Final Report on the new gTLD Subsequent PDP, but also placed some recommendations into a pending status. The Council convened a small team that worked collaboratively with the ICANN Board to resolve all pending recommendations. While the majority of the pending recommendations were able to be adopted by the ICANN Board, recommendations across six Topics were non adopted by the ICANN Board. The Council tasked the Small Team Plus with developing Supplemental Recommendations on five of the six Topics, i.e., Registry Voluntary Commitments / Public Interest Commitments, Applicant Support, Terms and Conditions, String Similarity Evaluations, and Limited Challenge/Appeal Mechanisms. Based on the expected implementation as it relates to the Continued Operations Instrument (COI), the Small Team Plus determined it was unnecessary to develop a Supplemental Recommendation for Topic 22: Registrant Protections. The Small Team Plus developed Supplemental Recommendations for all five topics and shared them with the Council. Because of information received just prior to Council consideration in April 2024, the Council elected to defer consideration of the Supplemental Recommendation related to String Similarity Evaluations, or more specifically, singular/plurals. The new information received was a strawperson developed by ICANN org, which provided a potential path forward for singular/plurals. The Council asked to consider whether it felt that the strawperson was promising enough to task the Small Team Plus considering whether strawperson, or and amended version, could be agreed upon. Here, the Council will receive an update from the Small Team Plus on Singulars/Plurals. 7.1 - Introduction of Topic (Paul McGrady, Chair of Small Team Plus) 7.2 - Council Discussion 7.3 - Next Steps Item 8: COUNCIL DISCUSSION - SubPro Small Team Supplemental Recommendations - Non-Adopted Recommendations (20 minutes) In March 2023, the ICANN Board approved the majority of the recommendations contained in the Final Report on the new gTLD Subsequent PDP, but also placed some recommendations into a pending status. The Council convened a small team that worked collaboratively with the ICANN Board to resolve all pending recommendations. While the majority of the pending recommendations were able to be adopted by the ICANN Board, recommendations across six Topics were non adopted by the ICANN Board. With the primary task of addressing the pending recommendations completed, the Council tasked the Small Team Plus with an updated assignment form<https://docs.google.com/document/d/1yDgWIwKZqKk0WY0q7CS2pf7aD4VupCWV/edit>. The Small Team Plus developed Supplemental Recommendation language for five of the six Topics. On 01 April 2024, the Small Team Plus shared the final Supplemental Recommendations<https://gnso.icann.org/sites/default/files/policy/2024/agenda/new-gtld-subp…> and explanations for the Supplemental Recommendations with the GNSO Council. On 18 April 2024, the GNSO Council voted to approve<https://community.icann.org/display/gnsocouncilmeetings/Motions+2024-04-18> the Supplemental Recommendations<https://gnso.icann.org/sites/default/files/policy/2024/agenda/new-gtld-subp…> for the non-adopted SubPro recommendations (regarding the following topics: Topic 9: Registry Voluntary Commitments / Public Interest Commitments, Topic 17: Applicant Support, Topic 18: Terms & Conditions, and Topic 32: Limited Challenge/Appeal Mechanism). The Council elected to remand back to the Small Team Plus the Supplemental Recommendations related to string similarity, after an ICANN org strawperson was shared shortly before the Council meeting. On 8 June 2024, the ICANN Board adopted<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> the following scorecard<https://www.icann.org/en/system/files/files/scorecard-subsequent-procedures…>, wherein it approved the Supplemental Recommendations related to Topic 17: Applicant Support and Topic 32: Limited Challenge/Appeal Mechanism. The Board did not adopt the Supplemental Recommendations related to Topic 9: Registry Voluntary Commitments / Public Interest Commitments and Topic 18: Terms & Conditions. Here, the Council will discuss whether any further actions should be pursued for any of the non-adopted Supplemental Recommendations. 8.1 - Introduction of Topic (Paul McGrady, Chair of Small Team Plus) 8.2 - Council Discussion 8.3 - Next Steps Item 9: COUNCIL UPDATE - Intellectual Property Constituency Request for Reconsideration (10 minutes) On 22 November 2023, the Intellectual Property Constituency (IPC) filed a Request for Reconsideration<https://www.icann.org/en/system/files/files/reconsideration-23-2-ipc-reques…> of the ICANN Board Resolutions 2023.10.26.11 and 2023.10.26.122<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…>, regarding (i) the actions and inactions that led to (a) the ICANN Board’s public comment of 6 December 2018 on the Initial Report<https://www.icann.org/en/system/files/files/new-gtld-auction-proceeds-initi…> of the Cross-Community Working Group on New gTLD Auction Proceeds (CCWG-AP), (b) the organization of the public comment phase<https://www.icann.org/en/public-comment/proceeding/proposed-final-report-of…> on the Proposed Final Report<https://www.icann.org/en/system/files/files/proposed-new-gtld-auction-proce…> of the New gTLD Auction Proceeds Cross Community Working Group, (c) the ICANN Board Resolutions 2022.06.12.13 to 2022.06.12.16 , and (ii) the actions and inactions involving the implementation of the ICANN Grant Giving Program. During its meeting at ICANN80<https://icann80.sched.com/event/1dr33/gnso-council-meeting>, a few GNSO Councilors volunteered to draft a letter to the Board regarding the Request for Reconsideration<https://www.icann.org/en/system/files/files/reconsideration-23-2-ipc-reques…>. Here, the Council will hear an update on the draft letter and discuss potential next steps for the Council, if any. 9.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) 9.2 - Council Discussion 9.3 - Next Steps Item 10: Any Other Business (20 minutes) 10.1 - Aspirational Statement 10.2 - SPS Actions Follow-up * Recommendations Report * Public Comment Review * Board Readiness _______________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… References for Coordinated Universal Time of 13:00 UTC Local time between March and November in the NORTHERN hemisphere See https://www.timeanddate.com/time/change/ for Dates for Daylight Saving Time and Clock Changes ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 06:00 San José, Costa Rica (CST) UTC-6 07:00 New York/Washington DC, USA (EDT) UTC-4 09:00 Buenos Aires, Argentina (ART) UTC-3 22:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 14:00 Paris, France (CEST) UTC+2 15:00 Moscow, Russia (MSK) UTC+3 16:00 Singapore (SGT) UTC+8 21:00 Melbourne, Australia (AEST) UTC+10 23:00 ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/mud7kn9k

1 0

FYI | FW: [Ext] NEW: Approved Resolutions | Special Meeting of the ICANN Board | 28 June 2024
by Terri Agnew 04 Jul '24

04 Jul '24

FYI [https://danh45uab.cc.rs6.net/on.jsp?ca=4111a935-6dc2-4810-9448-b30acced0b2d…] Thursday, 04 July 2024 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 [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…> 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 Information Sharing · NEW: Approved Resolutions | Special Meeting of the ICANN Board | 28 June 2024 · NEW: ICANN to Place .Nowruz Into Emergency Back-End Registry Operator Program · NEW: Implementation Oversight Team seeks input on IRP Supplementary Procedures · NEW: Asia Pacific Internet Governance Academy (APIGA) 2024 · NEW: Trusted Internet Summer School on Internet Governance and International Law · NEW: ICANN Outreach Program, Dhaka Bangladesh Action Items · ICANN Opens Nomination Period for Dr. Tarek Kamel Award for Capacity Building Public Comment · NEW Summary Report: Proposed Bylaws Updates to Limit Access to Accountability Mechanisms · NEW Public Comment: IRP-IOT – Proposed updates to the IRP Supplementary Procedure · Han Script Single Character IDN Generic Top-Level Domains Information Sharing NEW: Approved Resolutions | Special Meeting of the ICANN Board | 28 June 2024 Please find the Approved Resolutions from the 28 June 2024 Special meeting of the ICANN Board here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…>. NEW: ICANN to Place .Nowruz Into Emergency Back-End Registry Operator Program An EBERO provider may be temporarily activated if a gTLD registry operator is at risk of failing to sustain any of the five critical registry functions. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…> NEW: Implementation Oversight Team seeks input on IRP Supplementary Procedures The Independent Review Process (IRP) Implementation Oversight Team (IOT) seeks input on the IRP rules regarding Initiation, Panel selection, Time for Filing, Translation, Consolidation, Intervention, and Amicus. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…> NEW: Asia Pacific Internet Governance Academy (APIGA) 2024 The Asia Pacific Internet Governance Academy (APIGA) aims to develop youth leaders’ understanding of the Internet and its ecosystem. Date: Monday 8 July 2024 (01:00 UTC) - Friday 12 July 2024 (01:00 UTC) Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…> NEW: Trusted Internet Summer School on Internet Governance and International Law The summer school will be held fully residentailly residentially in Lodz, Poland, from 8 to 12 July 2024, focusing on the theme "Low Earth Orbit Satellites and Data Transfers: Ensuring a Trusted Internet." Date: Monday 8 July 2024 (07:00 UTC) - Friday 12 July 2024 (07:00 UTC) Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…> NEW: ICANN Outreach Program, Dhaka Bangladesh ICANN Outreach Program in Dhaka, Bangladesh being organised by EyHost and BTRC. Date: Wednesday 10 July 2024 (05:00 UTC) - Friday 12 July 2024 (05:00 UTC) Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…> Action Items ICANN Opens Nomination Period for Dr. Tarek Kamel Award for Capacity Building The ICANN Board will evaluate a shortlist of candidates and determine the recipient of this year's award. Please submit nominations via this nomination form [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…>by 29 July 2024 23:59 UTC. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…> Public Comment NEW Summary Report: Proposed Bylaws Updateds to Limit Access to Accountability Mechanisms [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…> NEW Public Comment: IRP-IOT – Proposed updates to the IRP Supplementary Procedures [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…> Open for Submissions: 03 July 2024 Closed for Submissions:16 September 2024 Han Script Single Character IDN Generic Top-Level Domains [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…> Open for Submissions: 27 June 2024 Closed for Submissions: 16 August 2024 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…>. Volume 6, Issue 49 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…> | Next Issue: Monday, 08 July 2024 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001k5bYpH9…>

1 0

Call for volunteers: Council small group on board readiness
by Caitlin Tubergen 03 Jul '24

03 Jul '24

Dear Councilors, During the ICANN80 Council Wrap-up Session<https://icann80.sched.com/event/1dr4t/gnso-council-wrap-up>, Kurt raised the topic of board readiness and volunteered to work with a small group of interested councilors to look into what steps the Council can take to ensure the policy recommendations it approves are board-ready. During this discussion, Jennifer and Justine volunteered to be a part of this effort. If you are interested in joining Kurt, Jennifer, and Justine, please reply to this message by Friday, 28 June. Kind regards, Caitlin

7 6

Preliminary Issue Report on Latin Script Diacritics
by Steve Chan 03 Jul '24

03 Jul '24

Dear Councilors, Per the PDP Manual, the creation of the Preliminary Issue Report is afforded 45 days, but staff can request additional time if it is needed. While great progress has been needed, staff needs just a little bit more time (e.g., two weeks) to finalize the document and publish it for public comment. Please let us know if you have any questions or concerns. Best, Steve Steven Chan  VP, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org<mailto:steve.chan@icann.org> Skype: steve.chan55 Mobile: +1.310.339.4410 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…>

2 1

FYI | FW: [gnso-secs] Re: RrSG Council Change
by Terri Agnew 03 Jul '24

03 Jul '24

Hello all, See the updated information below from the RrSG group. All the best, Terri **** Hello again GNSO Secs! RrSG concluded its elections yesterday. Please note that for council, Hong-Fu will replace Antonia and Prudence will continue her role. Both are copied above. Thanks and let me know if you need any additional information. Regards, Ashley Heineman Chair, RrSG From: Devan Reed <devan.reed(a)icann.org> Sent: Tuesday, June 25, 2024 12:24 PM To: Ashley Heineman <aheineman(a)godaddy.com>; gnso-secs(a)icann.org Cc: Zoe Bonython <secretariat(a)icannregistrars.org> Subject: Re: [gnso-secs] RrSG Council Change 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 Ashley, Thank you for letting us know. This has been shared with the GNSO Council. Kind regards, Devan From: aheineman--- via Gnso-secs <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Reply-To: "aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>" <aheineman(a)godaddy.com<mailto:aheineman@godaddy.com>> Date: Tuesday, June 25, 2024 at 11:16 AM To: "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Cc: Zoe Bonython <secretariat(a)icannregistrars.org<mailto:secretariat@icannregistrars.org>> Subject: [gnso-secs] RrSG Council Change Dear GNSO Secs, I wanted to let you know that Antonia Chu has stepped down as one of the RrSG Council members. We have initiated an election period today to fill this position (and others). I’ll let you know as soon as possible once we have a replacement and any other possible changes. Thanks so much and please feel free follow up with any questions. Ashley Heineman Chair, RrSG

1 0

Follow Up on Registration Data Accuracy
by DiBiase, Gregory 02 Jul '24

02 Jul '24

Dear Councilors, At ICANN 80 we considered next steps for advancing work on the Registration Data Accuracy topic. We are sending this follow up as reminder to consider the following questions with your respective SGs to inform discussion at our July meeting: 1. Evaluation of Proposed Alternatives: In its <https://gnso.icann.org/sites/default/files/policy/2023/correspondence/yokoy…> write-up<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/yokoy…>, ICANN noted limitations in processing data for the purpose of assessing accuracy and proposed two alternatives (analyzing historical audit data and engagement with Contracted Parties on ccTLD practices - see detail below). Is pursuing these alternatives worthwhile? If not, are there other alternatives for obtaining data Council should consider? 2. Consideration of Scoping Team Restart: Given the limitations with respect to access to data, would there be value in restarting the Scoping Team at this time? 3. Advancing the Topic: If restarting the Scoping Team at this time is not deemed advisable, what other ideas do you have to advance this topic given its importance to the ICANN community? Additional background and context is below for your reference. We look forward to the July meeting. Thanks, Greg Additional Background and Context: * EPDP on Temporary Specification (Reg Data) Phase 2 Team: Tasked with reviewing accuracy and the Whois Accuracy Reporting System (ARS), this team did not agree on policy recommendations for registration data accuracy. Consequently, the GNSO Council formed a scoping team to further define and scope potential issues related to accuracy and the ARS. The Scoping Team was charged with scoping issues related to accuracy and making recommendations on next steps, such as requesting an Issue Report, conducting a study, or determining no further work was needed. * Need for Data and GDPR Considerations: The Accuracy Scoping Team highlighted the need for data to inform its work. The ICANN Board suggested consulting European authorities on GDPR's impact, tasking ICANN with creating scenarios for assessing registration data accuracy and ensuring compliance with privacy rights. * ICANN Org's Four Proposed Scenarios:<https://gnso.icann.org/sites/default/files/policy/2023/correspondence/yokoy…> ICANN org proposed four scenarios for assessing registration data accuracy, considering current contractual requirements and applicable laws. These scenarios faced several challenges: * Scenario 1: Analyzing publicly available registration data was deemed infeasible due to redaction of personal data post-GDPR. * Scenario 2: Conducting a compliance audit on registrar validation and verification requirements could provide compliance insights but not confirm data accuracy and would require significant resources. * Scenario 3: Analyzing full registration data from registrars raised legal and GDPR compliance concerns. * Scenario 4: A voluntary registrar survey on data accuracy raises concerns regarding disparate participation (due to the voluntary nature) as well as potentially disproportionate or skewed data. * ICANN's Proposed Alternatives in light of the limitations with the proposed scenarios: * Historical Data from Compliance Audits: ICANN Compliance's existing audit program data from 2016 to 2023 could be summarized in a detailed report, providing insights into registrar compliance with validation and verification requirements in the <https://www.icann.org/en/system/files/files/registrar-accreditation-agreeme…> RDDS Accuracy Specification<https://www.icann.org/en/system/files/files/registrar-accreditation-agreeme…>. (While assessing the viability and value that a targeted contractual compliance audit would provide as envisioned in Scenario 2, ICANN determined that ICANN Compliance's existing audit program may provide a more suitable and less costly avenue for assessing current validation and verification requirements under the RAA.) * Engagement with Contracted Parties on European ccTLD Practices: Reviewing European ccTLD identity verification practices could offer insights into potential requirements for accuracy policies, considering evolving European legislation. These steps are intended to address the accuracy challenges while navigating legal frameworks and resource limitations. This engagement, led by ICANN staff, will focus on the likelihood that policymakers may put forward requirements for accuracy of registration data, including verification practices, through legislation.

1 0