- ALAC - lists.icann.org

Summary Report for GNSO Council 10 July 2025 meeting
by Justine Chew July 18, 2025

July 18, 2025

Dear all, Please find below, the re-updated Agenda for the GNSO Council 10 July 2025 meeting, followed by my Summary Report on Matters of Interest. You can also find these at this link <https://icann-community.atlassian.net/wiki/x/WIDYDw> under the relevant tabs. I'd be happy to answer and questions on this thread or during the next ALAC Monthly Call on 22 July. *GNSO Council Meeting #7 of 2025 held on 10 July 2025 (agenda updated again) <https://icann-community.atlassian.net/wiki/x/WIDYDw>* *Full Agenda* <https://icann-community.atlassian.net/wiki/x/KKafBg>* | * *Documents* <https://icann-community.atlassian.net/wiki/x/4KefBg>* | * *Motions* <https://icann-community.atlassian.net/wiki/x/PKifBg> - *Item 1: Administrative Matters* - Item 2: Opening Remarks / Review of Projects Action List - 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 - Confirmation of the GNSO-appointed Member for the Universal Acceptance (UA) Expert Working Group (EWG) - GNSO Council Review of GAC Communiqué - *Item 4: COUNCIL VOTE - Council Next Steps Regarding ICANN Reviews* - *Item 5: COUNCIL BRIEFING - Second IANA Naming Function Review Team (IFR2) Draft Report* - *Item 6: COUNCIL UPDATE - Privacy Proxy Services Accreditation Issues Implementation Work* - *Item 7: COUNCIL UPDATE - GNSO Council Small Team on Accuracy Draft Report* - *Item 8: COUNCIL UPDATE - GNSO Council Small Team on DNS Abuse* - Item 9: Any Other Business - 9.1 - ccNSO Council Update - 9.2 - Customer Standing Committee (CSC) Effectiveness Review Deferral - 9.3 - Celebration of Greg DiBiase, Outgoing GNSO Chair *Summary to the ALAC on GNSO Council Meeting #7 of 2025 held on 10 July 2025* For brevity, I will just highlight a few things here. For some of the issues, you can glean a wider perspective from GNSO Council July 2025 Matters of Interest and/or from GNSO Council July 2025 Meeting Records. 1. *Future of Reviews* - Council declined to support the ALAC’s Petition for an Empowered Community Reconsideration Request <https://www.icann.org/en/system/files/correspondence/alac-to-eca-19jun25-en…> and instead prefers the potential path being discussed by SOAC leadership (i.e. a Bylaws amendment to the Board that would amend the Bylaws to allow for a one-time review of all Reviews currently required by the Bylaws and to suspend the conduct of all Reviews until this exercise is completed, with the explicit safeguard of a time frame for completion, absent which the current Reviews obligations come back fully into force). - Council also decided that a motion confirming GNSO’s position be deferred pending more information on the potential path. 2. *Registration Data Accuracy (RDA)* - Council’s Accuracy Small Team has worked on: - Examining the current timeline for validation and verification of registration data under the 2024 Registrar Accreditation Agreement - Assembling a diverse and representative group of interested stakeholders who could work together on producing clear and user-friendly registrant educational materials related to the importance of accurate registration data - Further work on a previously-approved Whois2 Review Team recommendation (CC.1) related to the inclusion of a notation in the RDDS record that the domain name is suspended due to incorrect data - Council received an update on 4 recommendations <https://icann-community.atlassian.net/wiki/download/attachments/351535105/2…> being developed, which are expected to be voted on in its August meeting. 3. *DNS Abuse* - Council’s DNS Abuse Small Team has been working on: - Its Assignment Form <https://gnso.icann.org/sites/default/files/policy/2025/draft/assignment-for…> which includes the review and analysis of DNS Abuse mitigation efforts across the broader ICANN ecosystem, the impact of the RA and RAA amendments, the INFERMAL study, as well as other data sources. - On concluding that there are indeed gaps remaining, then cataloguing the issues. In developing that catalogue of issues, the small team also solicited input from SG/C/SO/ACs. (see At-Large Input to GNSO Council DNS Abuse Small Team (prioritization) <https://icann-community.atlassian.net/wiki/download/attachments/370246404/2…> (16 July 2025)) - A Request for an Issues Report. - Council received an update on the progress of the small team’s work and are expected to vote on the Request for an Issues Report in its August meeting. 4. *Privacy Proxy Services Accreditation Issues (PPSAI) Implementation* - The PPSAI Implementation Review Team (PPSAI IRT) re-convened by ICANN org in June 2024, has been refining a set of overarching threshold questions that require input to move forward on implementation of the 21 policy recommendations from the Final Report <https://gnso.icann.org/sites/default/files/filefield_48305/ppsai-final-07de…> that was approved by the ICANN Board back in August 2016. Work had been paused due to overlapping issues around the General Data Protection Regulation (GDPR), data processing, and the Temporary Specification <https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#temp…> . - The threshold questions currently under discussion are: - 1. Are there any policy questions or items the IRT already wants to bring to the GNSO Council for guidance? - 2. Implementation Model: Accreditation Program or Alternative Implementation: - (a) Can an implementation model without a new standalone accreditation program remain consistent with the policy recommendations? - 3. Disclosure Frameworks (Intellectual Property and Law Enforcement). - (a) Are there specific areas to revisit under new law/policy? - (b) Can these frameworks be aligned with existing work on the Registration Data Request Service (RDRS), Registration Data Policy, and other existing procedures and remain consistent with the policy recommendations? - Council expects discussions on these threshold questions to be formally presented in August 2025 whereupon Council will determine what approach to take to review these or to provide the guidance to the PPSAI threshold questions. - There after in September, draft responses to these questions is expected to be socialized with different groups, and in October, Council will discuss input received and finalize the responses to the IRT so that they can keep working considerations. 5. *Second IANA Naming Function Review Team (IFR2)* - Council received an update (slides <https://gnso.icann.org/sites/default/files/policy/2025/presentation/iana-na…>) from Ashley Heineman and Peter Koch, IFR2 Co-Chairs, on the IFR2 draft report <https://itp.cdn.icann.org/en/files/internet-assigned-numbers-authority-iana…> which contained findings and recommendations in three key areas: - Presence of specific Domain Name System Security Extensions (DNSSEC) policy details in the IANA Naming Function Contract - Transparency and availability of Contract amendments - Frequency of reviews - After considering public comment received and making adjustments as appropriate, the IFR2 team is working to reach consensus on its Final Report. - Council is expected to vote on the Final Report during the August Council meeting. Thanks for reading / considering Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://icann-community.atlassian.net/wiki/x/fG7xBQ?atlOrigin=eyJpIjoiNDI1Y…>

1 0

The SSAC Has Published SAC129
by Matthias M. Hudobnik July 9, 2025

July 9, 2025

Dear all, The SSAC appreciates the opportunity to provide input on the GNSO's efforts regarding domain name registration data accuracy. Although our response comes later than intended, we are grateful for your consideration. Key Points: Impact of Inaccurate Data: Usability: Hinders effective communication and identification. Security: Impairs law enforcement, anti-abuse efforts, and timely cybersecurity notifications. Operations: Disrupts domain transfers, dispute resolution, and security analysis due to incorrect metadata (e.g., create/update dates, registrar info). The SSAC consistently stresses the critical role of accurate data in enabling legitimate communications and mitigating abuse. What Inaccurate Data Does Not Prevent: It does not stop bad actors from continuing abusive domain use. Harm prevention is still possible using other tools, but accurate data improves effectiveness. Vulnerable Stakeholders: Law enforcement, cybersecurity firms, reputation service providers, researchers, brand protection teams, and operators of critical infrastructure (OS vendors, CAs, web/email/social platforms). These groups rely heavily on registration data for investigations and system protections. Problem Statement Recommendations: Current Challenge: Lack of clear definitions, measurable standards, and inconsistent accuracy. Consequences: Weakened DNS security, delayed investigations, and ineffective abuse mitigation. Objective: Improve data accuracy to strengthen trust and security. Proposal: Define “accuracy” clearly. Justify accuracy efforts through measurable benefits. Address the potential commercial impacts. Evaluate the implications of the EU’s NIS2 directive on ICANN policies. SSAC does not offer a formal problem statement but urges the GNSO to tackle key foundational issues including definitions, compliance mechanisms, and external regulatory impacts. Administrative Notes: The document reflects the consensus of the SSAC, with full transparency on contributors, disclosures, and any recusals. Link: https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committe… Best, Matthias __________________________ Ing. Mag. Matthias M. Hudobnik FIP, CIPP/E, CIPT, DPO, CIS LA matthias(a)hudobnik.at http://www.hudobnik.at @mhudobnik

1 0

Report on ICANN83 ccNSO Sessions and Council Meeting 218
by Laura Margolis July 9, 2025

July 9, 2025

Dear All: I hope you are doing fine. Regarding the ICANN 83 meeting in Prague, I would like to divide this report into 2 parts. One with some *highlights of some of the sessions*, and the second part with more details on the *Council meeting*. *PART 1: HIGHLIGHT SESSIONS during ICANN83* *ccTLD News Session * This session was held on Wednesday, June 11th. 2025 | 10:45-12:15 *Charles Noir (CIRA)* shared insights into *“CommuniFi”*, an initiative providing free community WiFi in Ottawa, Canada. Funded through CIRA’s *Net Good Grants*—which reinvests .CA revenue to bridge the country’s digital divide—the project was developed in collaboration with non-profits and government agencies. It focuses on connecting underserved and low-income communities with reliable internet access. The network also incorporates CIRA’s DNS Firewall service, ensuring user privacy by anonymizing data and offering protection against phishing, malware, and botnet threats. *Heidy Hernández (.gt)* presented the .GT registry’s recent efforts to promote digital education and its resulting benefits to both the local community and the registry’s performance. She showcased initiatives such as the launch of *Internet Week 2023*, where 25% of attendees used promotional codes to register .gt domains, and a successful *Cyber Monday* campaign featuring special renewal offers. Additional efforts include the creation of a free monthly newsletter with practical tech tips and partnerships with national telecom providers to deliver certified training programs—initiatives that have significantly enhanced digital skills in underserved areas. Other speakers included: - *Boyoung Kim (.kr)* – *“Expansion of 3rd-Level .kr Domain”* - *Antonia Chu (.cn)* – *“Tools from .CN to Fight DNS Abuse”* - *Alan Cameron (auDA)* – *“Building the Future: A Board Chair’s Retrospective”* Here you can find all the details, recordings and presentations for ccTLD News Session: https://icann83.sched.com/event/246YC *DASC (DNS Abuse Standing Committee): <https://ccnso.icann.org/en/workinggroups/dasc.htm> Online Scams and Financial Crime* Wednesday, June 11th. 2025 | 13:45-15:00 During this session, discussion focused on the connection between online scams, financial crime, and domain abuse. The session highlighted how ccTLD operators are addressing these issues and lay the groundwork for further explorations at ICANN84 among ccTLD operators, law enforcement, industry experts, and other stakeholders. The session was chaired by Nick Wenban-Smith (.uk), focused on the growing threat of online scams, financial crime, and their intersection with domain name-related abuse, particularly through the lens of country code top-level domains (ccTLDs). Panelists explored various regional approaches, challenges, and solutions aimed at curbing abuse, while emphasizing a shared global commitment to reducing malicious activity. - *Gabriel Andrews (FBI)* presented updated data on cybercrime trends. In 2024, the FBI received over 850,000 complaints, with reported financial losses totaling $16.6 billion. The largest losses stemmed from cryptocurrency fraud ($6.5 billion) and business email compromise ($2.7 billion), while spoofing and phishing were the most reported types of abuse (nearly 200,000 complaints). Andrews emphasized the importance of accurate and up-to-date WHOIS data to facilitate court orders and legal procedures, while also noting the difficulties of cross-border investigations. - *Keith Drazek (IIF)* introduced the *Internet Infrastructure Forum*, a new initiative designed to connect infrastructure operators to address shared coordination challenges, exchange experiences, disseminate best practices, and establish stronger communication channels within the ecosystem. - *Mon Perez (.sg)* outlined efforts by the Singaporean registry to combat online scams and financial crime. The .sg ccTLD implemented a domain name verification process through Singapore’s National Digital Identity system. This free security feature helps registrants safeguard against domain hijacking. Additionally, an internal monitoring system detects malicious .sg websites and alerts relevant stakeholders to take appropriate action. - *Bruce Tonkin (.au)* shared the multifaceted strategy adopted by the Australian Government and the .au ccTLD, including the implementation of a Scam Prevention Framework and collaboration with the National Anti-Scam Centre. auDA's proactive approach involves early identification of scam-related domains, strong partnerships with law enforcement, and regular reporting on domains associated with online scams. Here you can find all the details, recordings and presentations for the Online Scams and Financial Crime: https://icann83.sched.com/event/246YD If you were not able to attend, I really recommend you to take some time and listen to it. You will find it more than interesting with a lot of very useful information for our end-users community. *Joint session: ccNSO and GNSO RySG* Wednesday June 11th. 2025 | 15:30-17:00 This joint session between the *ccNSO* and the *gTLD Registries Stakeholder Group (RySG)*, moderated by *Chris Disspain* with contributions from *Alejandra Reynoso*, *Beth Bacon*, *David McAuley*, and several community members, focused on identifying and deepening collaboration across shared areas of interest. Topics included *DNS abuse mitigation*, *ICANN’s strategic and budget planning*, *Internet governance*, and *regulatory challenges*. Both groups emphasized the benefits of continued cooperation, while acknowledging structural differences—ccTLDs operate under national frameworks, while gTLDs function through contracts with ICANN. Tools like Mentimeter were used to gauge community sentiment in real-time, highlighting mutual interest in topics such as *Root Server System Governance, registrant-focused innovation*, and *engagement with governments and registrars*. The session concluded with agreement on forming a small joint working group to explore concrete collaborative actions, recognizing that alignment and shared advocacy between all registries—ccTLDs and gTLDs—could significantly strengthen their collective voice within and beyond the ICANN ecosystem. Here you can find the recordings and presentations used for this session: https://icann83.sched.com/event/246YG/ccnso-joint-session-with-ccnso-and-gn… *IGLC (Internet Governance Liaison Committee): <https://ccnso.icann.org/en/workinggroups/iglc.htm> * *20 Years of WSIS implementation and the Road ahead* Tuesday June 10th. 2025 | 10:45-12:15 This session was chaired by *Marta Moreira Dias (.pt)*, reflecting on the WSIS legacy and the evolving contribution of ccTLDs to digital governance. The session opened with a keynote by *Chris Buckridge (ICANN Board)*, who provided historical context to WSIS, highlighting its foresight in framing the concept of the "information society" and establishing the multistakeholder model. He discussed how WSIS laid the foundation for the Internet Governance Forum (IGF) and emphasized the growing importance of digital regulation, trust, and inclusive participation in a changing geopolitical and technological landscape. *Suzete Centeio (.cv)* shared the case of Cabo Verde, focusing on initiatives led by the .cv registry to foster digital inclusion, organize national and Lusophone IGFs, promote multilingual content in Portuguese and Creole, and participate in capacity-building projects like LusNIC and the Coalition for Digital Africa. *Pierre Bonis (.fr)* presented *“AFNIC – Internet Made in France”*, describing how the French registry has implemented WSIS action lines through a robust multistakeholder governance structure, its role in facilitating national IGF dialogues, and its long-standing financial and educational investment in digital literacy, online safety, and inclusion programs via the AFNIC Foundation. *Jo-Fan Yu (.tw)* discussed how TWNIC has moved beyond its traditional technical role to become a facilitator of national and regional Internet governance, highlighting efforts such as hosting APrIGF 2024, organizing the Taiwan IGF, supporting youth and civil society engagement, and developing a public-private trusted notifier framework to address DNS abuse. Throughout the session, Mentimeter was used to gather live input from the audience, and participants engaged in scenario-based reflections on the challenges and responsibilities of ccTLDs in politically sensitive multistakeholder discussions. The session concluded with consensus on the need to reposition ccTLDs as neutral but active governance actors and trust anchors in a rapidly evolving digital ecosystem. Here you can find the recordings and presentations used for this session: https://icann83.sched.com/event/246Y6/ccnso-20-years-of-wsis-implementation… *PART 2: ccNSO Council meeting #218* Date: Thursday June 12th. 2025 | 10:45-12:15 Agenda and Background Materials <https://icann-community.atlassian.net/wiki/spaces/ccNSOCWS/pages/103123987/…> Working Groups and Committees Written Updates <https://docs.google.com/document/d/1m0ekPSOwxtrLdOikwnABs62FGSoF96b-MPfys6T…> This time I will only include a brief summary of the Council meeting with main highlights for you to read. *Administrative Matters* The minutes of Council Meeting 217 were approved, and the Council reviewed a number of completed action items, many of which involved coordination with ICANN leadership and other SO/ACs, such as outreach to the GNSO and RySG regarding CSC-related matters and budget discussions with ICANN’s CFO and CEO. A letter from ICANN Legal regarding bylaw changes required for the implementation of the 2nd CSC Effectiveness Review was also noted. *Updates* Written updates were submitted covering the activities of the Empowered Community Administration (ECA), the IANA Function Review Team (IFRT), the Customer Standing Committee (CSC), and various working groups and liaisons. A brief update was provided on the redesign of the ccNSO website, with a launch projected for December 2025. The Council also received an overview of the draft ccNSO portfolio for FY26–27, which includes ongoing and new initiatives across four priority areas: policy development, organizational development, ICANN participation, and foundational operations. *Elections and Appointments* The Council adopted an updated *Council Selection Guideline* and approved the timeline for the 2026 Council elections. *Joke Braeken* (ccNSO Secretariat) was appointed as the Selection Process Manager for both the Council elections and the nomination process for *Board Seat 11*, which must conclude by April 2026. The Council also confirmed the timeline and process for the next round of *Council 360 Reviews*, appointing *Bart Boswinkel* as the Feedback Process Manager. Reviews will cover five Councillors whose terms conclude in 2026. *New Study Groups (Conclusions of PGA – Policy Gap Analisys Working Group <https://ccnso.icann.org/en/workinggroups/pga-wg.htm>)* Two study groups were formally established: - A *Study Group on Disaster Recovery* to explore the potential role of IANA in supporting ccTLD disaster recovery scenarios. - A *Study Group on IANA Public Records*, tasked with examining data accuracy, transparency, and compliance related to IANA’s ccTLD records. The Council adopted the Terms of Reference for both groups, with calls for volunteers to follow once broader workload prioritization is finalized. *Closure of ccPDP3 Review Mechanism WG and Policy Implementation Support* Following the Board’s adoption of the ccNSO’s policy on review mechanisms for delegation, transfer, revocation, and retirement of ccTLDs, the Council agreed to formally close the *ccPDP3 Review Mechanism Working Group*. At the same time, the Council launched a call for volunteers to join the *ccNSO Policy Implementation Assistance Group (ccPAIG RM)* to support implementation and clarification of the policy. *Other Appointments* The Council confirmed: - *Eberhard Lisse (.na)* as Chair of the Tech Working Group. - *Sami Mohamed Ali (.bh)* as the ccNSO appointee to ICANN’s Universal Acceptance Expert Group. *CSC Membership and Coordination* The Council approved the timeline and selection process for appointing a new ccNSO member to the CSC, with *Claudia Ruiz* appointed as Selection Process Manager. Coordination with the RySG and GNSO was confirmed, and the existing CSC Selection Committee will carry out the process. One of the remaining candidates not selected as a member will be offered the role of alternate. The Council also reaffirmed the deferral of the *3rd CSC Effectiveness Review* until June 2026 due to pending implementation of recommendations from the previous review and the required fundamental bylaw changes. *Closing Items* The Council took note of relevant developments from other ICANN83 sessions and confirmed the schedule for upcoming Council meetings through the end of 2025. Thank you for taking the time to read this report. And sorry for being this time delayed on sending it. If you would like any more information or details on any topic, please let me know and I will be happy to provide it. Best Regards, Laura Margolis *Laura Margolis* ALAC Liaison to ccNSO margolisl(a)gmail.com +59899690992 skype: lauri.margolis ccNSO Liaison Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…>

1 0

Fwd: [ccnso-council] Material prpearing special Council meeting 8 July 2025 re Community Reconsideration Request
by Laura Margolis July 5, 2025

July 5, 2025

Dear All: Complementing Justine's email regarding the ALAC Community Reconsideration Request, the ccNSO will have a special meeting for discussion, next Tuesday 10th. Below you can find the agenda. I will keep you posted. Subject: [ccnso-council] Material prpearing special Council meeting 8 July 2025 re Community Reconsideration Request To: ccnso-council(a)icann.org <ccnso-council(a)icann.org> Dear all, Please find included a note in preparation of your special Council meeting upcoming on 8 July 2025. The meeting will have a simple agenda: 1. Welcome and roll call 2. Admin matters 1. SoI 2. Quorum 3. Discussion and decision on ALAC’s Community Reconsideration request 4. AOB 5. Next meeting: 17 July 2025 6. Closure Note & draft decision ---- ------- *Proposed ccNSO Council Decision on whether to support ALAC Community Reconsideration Request* *Introduction* On 19 June 2025, the Council was approached with the question of whether the ccNSO supports the ALAC Community Reconsideration Petition that they initiated. The Petition can be found at: https://www.icann.org/en/system/files/correspondence/alac-to-eca-19jun25-en…. The petition seeks reconsideration of the ICANN Board Resolutions of 19 May 2025 published at: https://www.icann.org/en/board-activities-and-meetings/materials/approved-r… . Among others, ALAC suggests the Board decision to defer the fourth accountability and transparency review (ATR4) should be subject to Community Reconsideration. With respect to the deferral of ATR 4, in April 2025 the ccNSO Council has expressed strong support for what has come to be known as the “Review of Reviews”. This process is intended to explore the purpose and need for the ICANN Bylaw-mandated reviews, including the ATR, and this review should be conducted before launching ATR4 (see: https://ccnso.icann.org/sites/default/files/field-attached/reynoso-to-sinha… [ccnso.icann.org] <https://urldefense.com/v3/__https:/ccnso.icann.org/sites/default/files/fiel…> Per Section 4.2 (Reconsideration) and Annex D section 4.3 (Community Reconsideration Request) the ccNSO, as one of the Decisional Participants of ICANN’s Empowered Community, has to determine within 21 days after receiving the request whether it supports the Community Reconsideration Request. This date is 10 July 2026. The details on the request for support are available in Annex D: https://www.icann.org/en/governance/bylaws#annexD. Further, the Council agreed to following procedure was adopted by Council on 25 June: - *Community Reconsideration Petition Support Period* - The period to seek support ends at twenty-one (21) days after receiving the note from ALAC seeking support. The note was formally received on 19 June. The Community Reconsideration Petition Support Period ends 10 July 2025. - *Date Council decision whether to support Petition* - The Council is expected to meet no later than 20 days after receiving the request for support to discuss whether to support the Community Reconsideration Request, taking into account the ccTLD community comments and other factors. The secretariat will schedule a call for 8 July 2025. - *Posting of Request* - The ALAC request will be posted on the website/wiki. - *Solicitation community input* - starting Wednesday 25 June, until 1 July. Inform the community of the request and invite comments, if any (the Process Manager, will inform the community). Comments, if any, to be taken into account by Council at its meeting on 8 July - *Administrative Decision Council* - Due to the tight timelines the Council decisions are administrative i.e not subject to the members call for a vote. They are effective immediately upon publication. - If no support for Request Community Reconsideration, no action is needed (maybe out of courtesy inform others). If supported, ECA, other DP’s and ICANN secretariat need to be informed. The community solicitation started as agreed on Wednesday 25 June 2025, and resulted in one comment: What are the cost implications of either option (Reconsideration and ATR4, or doing a whole load of nothing)? *Decision* The ccNSO Council, after consulting the ccTLD community, and taking into account the support for a “review of reviews” process to be completed prior to ATR4 and any other ICANN Bylaw mandated specific review, decides NOT to support the Community Reconsideration Process. _______________________________________________ Ccnso-council mailing list -- ccnso-council(a)icann.org To unsubscribe send an email to ccnso-council-leave(a)icann.org _______________________________________________ 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. Thank you! Best Regards, Laura Margolis ALAC Liaison to ccNSO

1 0

GNSO Council 10 July 2025 meeting agenda is out
by Justine Chew July 5, 2025

July 5, 2025

Dear all, Please be informed that the agenda for the GNSO Council Meeting taking place on Thursday, 10 July 2025, is as follows: *GNSO Council Meeting #7 of 2025 held on 10 July 2025 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/edit-v2/265…>* *Full Agenda* <https://icann-community.atlassian.net/wiki/x/KKafBg>* | * *Documents* <https://icann-community.atlassian.net/wiki/x/4KefBg>* | * *Motions* <https://icann-community.atlassian.net/wiki/x/PKifBg> - *Item 1: Administrative Matters* - Item 2: Opening Remarks / Review of Projects Action List - 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 - - Confirmation of the GNSO-appointed Member for the Universal Acceptance (UA) Expert Working Group (EWG) - - GNSO Council Review of GAC Communiqué - *Item 4: COUNCIL BRIEFING - Second IANA Naming Function Review Team (IFR2) Draft Report* - - Item 5: COUNCIL DISCUSSION - Outcome of Transfer Policy Review PDP Human Right Impact Assessment - - *Item 6: COUNCIL UPDATE - Privacy Proxy Services Accreditation Issues Implementation Work* - *Item 7: COUNCIL UPDATE - GNSO Council Small Team on Accuracy Draft Report* - *Item 8: COUNCIL UPDATE - GNSO Council Small Team on DNS Abuse* - *Item 9: Board deferral of Bylaws-mandated Reviews and steps needed for Community Input* - Item 10: Any Other Business - - *10.1 - ccNSO Council Update* - - *10.2 - Customer Standing Committee (CSC) Effectiveness Review Deferral* - - *10.3 - Celebration of Greg DiBiase, Outgoing GNSO Chair* For more details on the marked agenda items, please visit *this link <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/edit-v2/265…>* and *click on 'Matters of Interest'* This Council meeting will take place on *10 July 2025 at 13:00 UTC for 2 hours* and is open to observers remotely in listen-only mode via Zoom: https://icann.zoom.us/j/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 Thanks for reading / considering. Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://icann-community.atlassian.net/wiki/x/fG7xBQ?atlOrigin=eyJpIjoiNDI1Y…> ------

3 6

Petition for EC Request for Reconsideration of the Board's decision on reviews
by Jonathan Zuck June 26, 2025

June 26, 2025

Folks, As discussed, here is the Empowered Community Petition for a Request for Reconsideration of the Board’s May 19 decision on reviews. We are now on the clock to find allies. Jonathan

6 12

Re: [CPWG] Re: The DNS Is Broken - Response
by Seun Ojedeji June 19, 2025

June 19, 2025

I do agree with Michael that we should not loose sight of the fact that ATRT was a process enshrined into ICANN bylaw(re:ATRT). The issue for me is not a question of whether ATRT should remain or not but how ICANN is attempting to get rid of ATRT. If the process has become such a resource guzzling activity then ICANN should come back to the community to find a fix to it. ATRT 3 still has less than 60% implementation, unless a new ATRT will be looking into a major structural review, allowing more time to implement v3 and introducing a lighter version ATRT may be a good way forward but that discussion needs to have occurred within the community (and the Board). Once a force has been able to get a vehicle jump started, it's good to let go, continuing to push the vehicle can be a waste of resources. Previous ATRTs have achieved a lot of the objective of the activity and perhaps a longer periodic trigger for ATRT would be ideal if having a lighter version with much smaller scope is not desirable by the community. Regards On Wed, 18 Jun 2025 at 13:07, michael palage.com via CPWG <cpwg(a)icann.org> wrote: > Thanks for pointing out Milton’s constructive response. > > > > I have responded to his comments to hopefully continue a constructive > dialogue. > > > > *From: *Judith Hellerstein via CPWG <cpwg(a)icann.org> > *Date: *Wednesday, June 18, 2025 at 12:08 PM > *To: *Carlton Samuels <carlton.samuels(a)gmail.com> > *Cc: *CPWG <cpwg(a)icann.org>, alac(a)icann.org <alac(a)icann.org> > *Subject: *[CPWG] Re: The DNS Is Broken - Response > > Hi Carlton, > > Very interesting. Milton is not wrong in many of his points. > > > > Judith > > Sent from my iPad > > judith(a)jhellerstein.com > > Mobile: +1202333517 > > > > On Jun 18, 2025, at 12:00 PM, Carlton Samuels via CPWG <cpwg(a)icann.org> > wrote: > > > > Y'all might have already seen on one or other of these lists the article > authored by Michael Palage and now published in CirceID. > > > > The response from one of my favourite polemicists, Milton Mueller, is as > interesting. > > > > https://circleid.com/posts/icann-is-broken > > > > Carlton > > ============================== > *Carlton A Samuels* > > *Mobile: 876-818-1799 Strategy, Process, Governance, Assessment & > Turnaround* > ============================= > > _______________________________________________ > CPWG mailing list -- cpwg(a)icann.org > To unsubscribe send an email to cpwg-leave(a)icann.org > > _______________________________________________ > 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. > > _______________________________________________ > CPWG mailing list -- cpwg(a)icann.org > To unsubscribe send an email to cpwg-leave(a)icann.org > > _______________________________________________ > 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. > -- ------------------------------------------------------------------------ *Seun Ojedeji,* Bringing another down does not take you up - think about your action!

2 1

Re: [CPWG] The DNS Is Broken - Response
by Judith Hellerstein June 18, 2025

June 18, 2025

Hi Carlton, Very interesting. Milton is not wrong in many of his points. Judith Sent from my iPad judith(a)jhellerstein.com Mobile: +1202333517 > On Jun 18, 2025, at 12:00 PM, Carlton Samuels via CPWG <cpwg(a)icann.org> wrote: > > > Y'all might have already seen on one or other of these lists the article authored by Michael Palage and now published in CirceID. > > The response from one of my favourite polemicists, Milton Mueller, is as interesting. > > https://circleid.com/posts/icann-is-broken > > Carlton > ============================== > Carlton A Samuels > Mobile: 876-818-1799 > Strategy, Process, Governance, Assessment & Turnaround > ============================= > _______________________________________________ > CPWG mailing list -- cpwg(a)icann.org > To unsubscribe send an email to cpwg-leave(a)icann.org > > _______________________________________________ > 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

Summary Report for GNSO Council 11 June 2025 meeting
by Justine Chew June 15, 2025

June 15, 2025

Dear all, Just a very short note to let you know of my summary report for the GNSO Council meeting that took place during ICANN83. Please visit this link <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/265846872/G…> and then click on the ALAC report sublink. Happy to answer questions, if any. Thanks for reading / considering. Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://icann-community.atlassian.net/wiki/x/fG7xBQ?atlOrigin=eyJpIjoiNDI1Y…> --------- On Sat, 31 May 2025, 14:58 Justine Chew, <justine.chew.icann(a)gmail.com> wrote: > Dear all, > > Please be informed that the agenda for the GNSO Council Meeting taking > place on Wednesday, 11 June 2025 during ICANN 83 is as follows: > > *GNSO Council Meeting #6 of 2025 held on 11 June 2025 during ICANN83* > > *Full Agenda* <https://icann-community.atlassian.net/wiki/x/IKafBg>* | * > *Documents* <https://icann-community.atlassian.net/wiki/x/2KefBg>* | * > *Motions* <https://icann-community.atlassian.net/wiki/x/NKifBg> > > - > > *Item 1: Administrative Matters* > - > > Item 2: Opening Remarks / Review of Projects Action List > - 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 > - Deferral of Whois Implementation Advisory Group work > - *Item 4: COUNCIL DISCUSSION - Prioritization of Upcoming Work* > - *Item 5: COUNCIL UPDATE - Update from Board Readiness Small Team* > - *Item 6: COUNCIL UPDATE - Progress Update from Council Accuracy > Small Team* > - *Item 7: COUNCIL UPDATE: Status Update from DNS Abuse Small Team* > - *Item 8: COUNCIL DISCUSSION: Update on Reviews* > - Item 9: Any Other Business > - 9.1 - Open Mic > > > For more details on the marked agenda items, please visit *this link > <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/265846872/G…>* > and > *click on 'Matters of Interest'* > As usual, non-Council members are welcome to attend the meeting as > observers only, save for item 9.1 Open Mic. If you are interested in > observing this meeting either in-person or online via Zoom, please refer t > o https://icann83.sched.com/event/246XL for meeting details, noting that > the Zoom link will only be made available 24 hours prior to the meeting.. > > Thanks for reading / considering. > > Justine Chew > ALAC Liaison to the GNSO > GNSO Liaison Report Workspace > <https://icann-community.atlassian.net/wiki/x/fG7xBQ?atlOrigin=eyJpIjoiNDI1Y…> > ------ > > > >

2 1

Re: At-Large Response to ICANN Board regarding ATRT4
by Alfredo Calderon June 4, 2025

June 4, 2025

As an At-Large community member the Request for Reconsideration (RfR) is a clear documented communication to the Board. I support the submission of the request. The second document has a solid timeline to gather support from the ICANN community to gather support to move forward on the next steps to meet the deadline as required by the bylaws for situations similar to this travesty of the Board. Alfredo Calderon At-Large community member Alfredo Calderon Email: calderon.alfredo(a)gmail.com Twitter: acalderon52 LinkedIn: pr.linkedin.com/in/acalderon52 Skype: alfredo_1212 Business Card: http://myonepage.com/acalderon Blog: https://aprendizajedistancia.blogspot.com VSIG: Virtual School on Internet Governance - https://virtualsig.org

1 0