- ALAC - lists.icann.org

Launch of The Internet Ecosystem Book
by Nikesh B. Simmandree Aug. 18, 2025

Aug. 18, 2025

Dear Community, I am thrilled to announce the launch of my book, The Internet Ecosystem — a comprehensive exploration of the history, architecture, governance, and future of the Internet. This book distills decades of technological evolution — from ARPANET and packet switching, to AI, Web3, quantum networks, and beyond — into a clear, engaging narrative accessible to both technical and non-technical readers What the Book Covers * The Past: How Cold War research, ARPANET, and packet switching gave birth to the Internet we know today. * The Present: The intricate roles of ISPs, backbone providers, cloud infrastructure, AI, cybersecurity, and global governance shaping our daily online experiences. * The Future: Insights into 5G/6G, blockchain, immersive technologies, quantum security, and the Internet in 2050. With 49 detailed chapters, the book provides a definitive yet approachable reference for students, professionals, policymakers, and curious readers alike. My mission with The Internet Ecosystem is to make the Internet’s complexity understandable — showing not only how the Internet works, but also why it matters and has become one of the most transformative human inventions — while sparking dialogue on how we build a secure, inclusive, and sustainable digital future. In the 21st century, understanding the Internet is not optional — it’s essential. Whether you’re a business leader, policymaker, educator, student, or everyday Internet user, this book provides the context and clarity you need to navigate the opportunities and challenges of our connected world. Get Your Copy The Internet Ecosystem is now available: https://payhip.com/b/hfvYg Thank you, Best Regards, Nikesh B. Simmandree +230-5-907-3413 nikeshbs(a)outlook.com This message and its attachments are intended only for the person or entity to which it is addressed and are strictly confidential. If you have received this in error, please delete it from any devices after having informed the sender.

1 0

Summary Report for GNSO Council 14 August 2025 meeting
by Justine Chew Aug. 17, 2025

Aug. 17, 2025

Dear all, Please find below, the updated agenda for the GNSO Council 14 August 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/spaces/atlarge/pages/265846872/G…> under the relevant tabs. While the meeting agenda was lengthy, as usual, Council made decisions on 6 topics. I'd be happy to answer and questions on this thread or during the next ALAC Monthly Call on 26 August. *GNSO Council Meeting #8 of 2025 held on 14 August 2025 (updated 8 Aug 2025)* *Full Agenda* <https://icann-community.atlassian.net/wiki/x/MKafBg>* | * *Documents* <https://icann-community.atlassian.net/wiki/x/6KefBg>* | * *Motions* <https://icann-community.atlassian.net/wiki/x/RKifBg> - *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 CSC Effectiveness Review* - Confirmation of GNSO Non-Registry Liaison and Alternate to the Customer Standing Committee (CSC) - Adoption of Team 14 outcomes document - Board Seat 14 appointment - *Confirmation of Support for the Board’s Proposed Non-Adoption of Select IGO Recommendations* - *Item 4: COUNCIL VOTE - Approval of IANA Review Function 2 (IFR2) Final Report* - *Item 5: COUNCIL VOTE - Approval of Recommendations from GNSO Council Small Team on Accuracy * - *Item 6: COUNCIL VOTE - Request for Issue Report on DNS Abuse* - *Item 7: COUNCIL VOTE - Approval of the Review of Reviews Cross Community Group Charter* - *Item 8: COUNCIL UPDATE - Privacy Proxy Services Accreditation Issues Implementation Work - Questions for GNSO Council* - *Item 9: COUNCIL UPDATE - Outcome of Transfer Policy Review PDP Human Rights Impact Assessment* - Item 10: Any Other Business - 10.1 - ICANN84 planning and GNSO Draft schedule - 10.2 - WSIS Update - 10.3 - GNSO Liaison to the GAC update - 10.4 - Question re: GNSO Liaison to the GAC * Summary to the ALAC on GNSO Council Meeting #8 of 2025 held on 14 August 2025* For brevity, I will just highlight outcomes on key issues here. For some of the issues, you can get more information under the Matters of Interest and/or Meeting Records tabs. Council resolved <https://icann-community.atlassian.net/wiki/x/RKifBg> quite a few issues at this meeting. 1. Deferred the *Third CSC Effectiveness Review* for one year; this decision will be revisited in August 2026. 2. Approved the 3 recommendations contained in the *Second IANA Naming Function Review Team (IFR2)* Final Report, covering: 1. Presence of specific Domain Name System Security Extensions (DNSSEC) policy details in the IANA Naming Function Contract 2. Transparency and availability of Contract amendments 3. Frequency of reviews 3. Does not object to the Board’s intention to reject 2 pending recommendations related to *International Governmental Organization (IGO) names protections *(i.e. Recommendations 3.3.5 and 3.3.7 from the 2013 Top & Second Level Protections for IGOs, Red Cross, Int’l Olympic Committee, and international NGOs (INGOs) PDP) on the basis that they have been superseded by subsequent policy development (i.e. the 2019: IGO & INGO Curative Rights PDP and the 2022 Expedited PDP on IGO Curative Rights). 4. Adopted the 4 recommendations on *Registration Data Accuracy (RDA) *as recommended by Council’s Accuracy Small Team. These recommendations were last discussed <https://icann-community.atlassian.net/wiki/download/attachments/351535105/2…> by Justine on CPWG 2 Jul 2025 call <https://icann-community.atlassian.net/wiki/x/AQD0F>. 5. Adopted the 3 recommendations on *DNS Abuse* as recommended by Council’s DNS Abuse Small Team. These recommendations were last discussed <https://icann-community.atlassian.net/wiki/download/attachments/389906434/2…> by Justine on 30 Jul 2025, with the key recommendations being (i) a Request for an Issue Report based upon the catalogue of issues the Small Team has developed (with input from SG/C/ACs); and (ii) elevating three prioritized gaps for a draft Charter development. At-Large input was provided per 1. *CPWG high-level update, 30 Jul 2025* <https://icann-community.atlassian.net/wiki/download/attachments/389906434/2…> (covers At-Large Position on DNS Abuse mitigation gaps) 2. *CPWG high-level update, 16 Jul 2025* <https://icann-community.atlassian.net/wiki/download/attachments/370246404/2…> (covers notes on DNS Abuse mitigation gaps; and At-Large priorities) 6. Approved the Charter for the *Review of Reviews* Cross Community Group (CCG) <https://gnso.icann.org/sites/default/files/policy/2025/correspondence/final…>, following the ICANN Board’s 19 May 2025 resolution <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> to continue the deferral of the ATRT4, and other Specific Reviews, pending community dialogue to inform next steps, and notwithstanding the timing mandated under the Bylaws for the commencement of ATRT4. The CCG will undertake the review of reviews per the Charter. 1. Council’s Standing Selection Committee will identify and select two (2) GNSO member participants of the CCG, at least one of whom should be a GNSO council member, for Council’s approval. 2. Recall that 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 preferred the path of the CCG. Other than that: 7. Council discussion on *Privacy Proxy Services Accreditation Issues Implementation (PPSAI) *Work continues. 8. Council will draw learnings from a *Human Rights Impact Assessment (HRIA) *conducted on the recommendations in the Transfer Policy Review Working Group’s Final Report, such as the need for including a reference to HRIA in the GNSO Operating Procedures and as part of the GNSO Council Liaison to a PDP’s job description. 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

Re: SAC130: SSAC Comments on Name Collision Guidelines in the Proposed Language for the Draft Next Round Applicant Guidebook
by Justine Chew Aug. 6, 2025

Aug. 6, 2025

👍🏼 Justine Chew reacted via Gmail <https://www.google.com/gmail/about/?utm_source=gmail-in-product&utm_medium=…> On Wed, 6 Aug 2025 at 22:05, James Galvin <galvin(a)elistx.com> wrote: > Thank you Matthias. > > And now that we know from yesterday’s meeting that Topic 29 will be > discussed on 20 August at 18:30 UTC, I can confirm I will be there as > SSAC’s representative. > > I’m happy to answer any questions or have any discussion anyone may have > before then. > > Jim > > On 27 Jul 2025, at 6:04, Matthias M. Hudobnik wrote: > > Dear colleagues, see some infos between the lines. > > Best, > Matthias > > __________________________ > Ing. Mag. Matthias M. Hudobnik > FIP, CIPP/E, CIPT, DPO, CIS LA > matthias(a)hudobnik.at > http://www.hudobnik.at > @mhudobnik > > On 25.07.2025, at 01:39, Justine Chew <justine.chew.icann(a)gmail.com> > wrote: > > > Hi Avri, > > I understand SAC130 to be SSAC's public comment to the draft AGB public > comment proceeding that just closed. > > > Yes, see here: > https://www.icann.org/en/public-comment/proceeding/final-proceeding-for-pro… > . > > > NCAP Study 2 was an SSAC output. It doesn't go through the GNSO but the > recommendations (except one) was approved by the Board. These then went to > org for implementation. Hence the new Name Collision Management Framework > was established as it appears in the draft AGB, as discussed by the IRT. > > > Here the info: > https://www.icann.org/en/board-activities-and-meetings/materials/approved-r… > . > > > What I understand from SAC130 is SSAC suggests the that implementation of > its NCAP Study 2 is either incomplete or hasn't gone far enough. I trust > this position will be discussed when the IRT reconvenes to review public > comments and we should once again have Jim Galvin for those IRT calls. > > > Yes, indeed. > > > > Kind regards, > Justine > --------- > > On Fri, 25 Jul 2025, 05:06 avri doria, <avri(a)doria.org> wrote: > >> Hi, >> >> Was this advice approved by anyone (i.e. GNSO & Board) and designated as >> part of the SubPro recommendations? Or does it have the nebulous status of >> most advice? Did the GNSO act on NCAP2 "recommendations?" >> >> As neither the Board nor the SSAC have policy making authority, I am >> curious. >> >> thanks >> >> avri >> On 7/24/2025 11:35, Justine Chew via ALAC wrote: >> >> Thanks for this, Matthias. I am hopeful that Jim Galvin will discuss >> these with the IRT when the IRT reconvenes to review input from the most >> recent public comment proceeding. >> >> Kind regards, >> Justine >> >> >> >> On Thu, 24 Jul 2025 at 21:28, Matthias M. Hudobnik via ALAC < >> alac(a)icann.org> wrote: >> >>> Dear Colleagues, >>> >>> The SSAC welcomes the opportunity to comment on ICANN’s Draft Applicant >>> Guidebook (AGB) for the New gTLD Program: Next Round. Our comments focus on >>> improving *Section 6.7 on Name Collisions*, with an emphasis on risks >>> arising from *collisions between DNS and alternative naming systems* >>> (e.g., blockchain-based systems), as outlined in the Name Collision >>> Analysis Project Study 2 Report (NCAP2). >>> Summary of Key Recommendations: >>> >>> 1. >>> >>> *Clarify TRT’s Role in Initial Assessments* >>> AGB §6.7.2 does not clearly state that the *Technical Review Team >>> (TRT)* conducts the initial name collision risk assessment. NCAP2 >>> indicates TRT is responsible from the outset. >>> *Recommendation:* Explicitly assign the initial assessment to the >>> TRT. >>> 2. >>> >>> *Enable Pre-Delegation Action on High-Risk Strings* >>> Current language suggests high-risk strings are identified only >>> after temporary delegation. NCAP2 supports action based on existing data. >>> *Recommendation:* Allow TRT to recommend withholding delegation if >>> early analysis shows high risk. >>> 3. >>> >>> *Broaden TRT’s Assessment Scope Beyond DNS Data* >>> Limiting analysis to DNS logs misses collisions from alternative >>> namespaces that resolve via DNS (e.g., users accustomed to *.wallet* >>> from blockchain). >>> ➤ *Recommendation:* Permit use of OSINT, qualitative assessments, >>> and external data sources per NCAP2. >>> 4. >>> >>> *Allow TRT Flexibility to Evolve Assessment Methods* >>> AGB cites four NCAP2 methods (NI, CI, VI, VIN), but doesn’t state >>> whether TRT may adopt new techniques. >>> *Recommendation:* Affirm TRT’s discretion to evolve methods to >>> address future risks. >>> >>> These updates will better align the AGB with NCAP2 and ICANN Board >>> guidance, while improving transparency, security, and technical rigor in >>> handling name collisions. >>> >>> The SSAC appreciates the efforts of the ICANN org and Subsequent >>> Procedures IRT, and we are available for further discussion. >>> >>> Link: >>> https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committe… >>> . >>> >>> >>> Best, >>> >>> Matthias >>> _______________________________________________ >>> ALAC mailing list -- alac(a)icann.org >>> To unsubscribe send an email to alac-leave(a)icann.org >>> >>> At-Large Online: http://www.atlarge.icann.org >>> ALAC Working Wiki: >>> https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… >>> _______________________________________________ >>> 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. >> >> >> _______________________________________________ >> ALAC mailing list -- alac(a)icann.org >> To unsubscribe send an email to alac-leave(a)icann.org >> >> At-Large Online: http://www.atlarge.icann.org >> ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… >> _______________________________________________ >> 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

GNSO Council 14 August 2025 meeting agenda is out
by Justine Chew Aug. 5, 2025

Aug. 5, 2025

Dear all, Please be informed that the agenda for the GNSO Council Meeting taking place on Thursday, 14 August 2025, is as follows:- *GNSO Council Meeting #8 of 2025 held on 14 August 2025 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/265846872/G…>* *Full Agenda* <https://icann-community.atlassian.net/wiki/x/MKafBg>* | * *Documents* <https://icann-community.atlassian.net/wiki/x/6KefBg>* | * *Motions* <https://icann-community.atlassian.net/wiki/x/RKifBg> - *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 CSC Effectiveness Review* - Confirmation of GNSO Non-Registry Liaison and Alternate to the Customer Standing Committee (CSC) - Adoption of Team 14 outcomes document - Board Seat 14 appointment - *Confirmation of Support for the Board’s Proposed Non-Adoption of Select IGO Recommendations* - *Item 4: COUNCIL VOTE - Approval of IANA Review Function 2 (IFR2) Final Report* - *Item 5: COUNCIL VOTE - Approval of Recommendations from GNSO Council Small Team on Accuracy * - *Item 6: COUNCIL VOTE - Request for Issue Report on DNS Abuse* - *Item 7: COUNCIL VOTE - Approval of the Review of Reviews Cross Community Group Charter* - *Item 8: COUNCIL UPDATE - Privacy Proxy Services Accreditation Issues Implementation Work - Questions for GNSO Council* - *Item 9: COUNCIL UPDATE - Update on Urgent Requests* - *Item 10: COUNCIL UPDATE - Outcome of Transfer Policy Review PDP Human Rights Impact Assessment* - Item 11: Any Other Business - 11.1 - ICANN84 planning and GNSO Draft schedule - 11.2 - WSIS Update - 11.3 - GNSO Liaison to the GAC update 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'* This Council meeting will take place on *14 August 2025 at 21: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 Passcode: mkt7*ULa9b 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

Customer Standing Committee Liaison Nominee
by Jonathan Zuck July 31, 2025

July 31, 2025

Folks, On behalf of the AASC, I would like to nominate for your approval, Houda Chihi for the position of ALAC Liaison to the Customer Standing Committee (CSC). Her Curriculum Vitae and EOI are available here<https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/376963083/S…> (please sign in to Confluence to view this page). The CSC ensures the satisfactory performance of the Internet Assigned Numbers Authority (IANA) naming function. The CSC is responsible for monitoring Public Technical Identifier's (PTI) performance of the IANA naming function against the service level expectations in the IANA Naming Function Contract. The CSC analyzes performance reports provided by PTI and publishes its findings. Please raise any concerns you have by Friday, July 1. Thank you. Jonathan Jonathan Zuck | Director, Future of Work Project | Innovators Network jzuck(a)innovatorsnetwork.org<mailto:jzuck@innovatorsnetwork.org> | O 202.827.7594 | D 202.420.7483 [See the source image]Jonathan-zuck<https://www.linkedin.com/in/jonathan-zuck/> | [See the source image] jvzuck<https://twitter.com/Jvzuck> | [See the source image] jonathanzuck<https://www.instagram.com/jonathanzuck/> | [See the source image] Jonathan.zuck<https://www.facebook.com/jonathan.zuck/> [signature_1023473624]

5 5

Re: SAC130: SSAC Comments on Name Collision Guidelines in the Proposed Language for the Draft Next Round Applicant Guidebook
by Matthias M. Hudobnik July 27, 2025

July 27, 2025

1 0

Re: SAC130: SSAC Comments on Name Collision Guidelines in the Proposed Language for the Draft Next Round Applicant Guidebook
by Justine Chew July 24, 2025

July 24, 2025

Hi Avri, I understand SAC130 to be SSAC's public comment to the draft AGB public comment proceeding that just closed. NCAP Study 2 was an SSAC output. It doesn't go through the GNSO but the recommendations (except one) was approved by the Board. These then went to org for implementation. Hence the new Name Collision Management Framework was established as it appears in the draft AGB, as discussed by the IRT. What I understand from SAC130 is SSAC suggests the that implementation of its NCAP Study 2 is either incomplete or hasn't gone far enough. I trust this position will be discussed when the IRT reconvenes to review public comments and we should once again have Jim Galvin for those IRT calls. Kind regards, Justine --------- On Fri, 25 Jul 2025, 05:06 avri doria, <avri(a)doria.org> wrote: > Hi, > > Was this advice approved by anyone (i.e. GNSO & Board) and designated as > part of the SubPro recommendations? Or does it have the nebulous status of > most advice? Did the GNSO act on NCAP2 "recommendations?" > > As neither the Board nor the SSAC have policy making authority, I am > curious. > > thanks > > avri > On 7/24/2025 11:35, Justine Chew via ALAC wrote: > > Thanks for this, Matthias. I am hopeful that Jim Galvin will discuss these > with the IRT when the IRT reconvenes to review input from the most recent > public comment proceeding. > > Kind regards, > Justine > > > > On Thu, 24 Jul 2025 at 21:28, Matthias M. Hudobnik via ALAC < > alac(a)icann.org> wrote: > >> Dear Colleagues, >> >> The SSAC welcomes the opportunity to comment on ICANN’s Draft Applicant >> Guidebook (AGB) for the New gTLD Program: Next Round. Our comments focus on >> improving *Section 6.7 on Name Collisions*, with an emphasis on risks >> arising from *collisions between DNS and alternative naming systems* >> (e.g., blockchain-based systems), as outlined in the Name Collision >> Analysis Project Study 2 Report (NCAP2). >> Summary of Key Recommendations: >> >> 1. >> >> *Clarify TRT’s Role in Initial Assessments* >> AGB §6.7.2 does not clearly state that the *Technical Review Team >> (TRT)* conducts the initial name collision risk assessment. NCAP2 >> indicates TRT is responsible from the outset. >> *Recommendation:* Explicitly assign the initial assessment to the TRT. >> 2. >> >> *Enable Pre-Delegation Action on High-Risk Strings* >> Current language suggests high-risk strings are identified only after >> temporary delegation. NCAP2 supports action based on existing data. >> *Recommendation:* Allow TRT to recommend withholding delegation if >> early analysis shows high risk. >> 3. >> >> *Broaden TRT’s Assessment Scope Beyond DNS Data* >> Limiting analysis to DNS logs misses collisions from alternative >> namespaces that resolve via DNS (e.g., users accustomed to *.wallet* >> from blockchain). >> ➤ *Recommendation:* Permit use of OSINT, qualitative assessments, and >> external data sources per NCAP2. >> 4. >> >> *Allow TRT Flexibility to Evolve Assessment Methods* >> AGB cites four NCAP2 methods (NI, CI, VI, VIN), but doesn’t state >> whether TRT may adopt new techniques. >> *Recommendation:* Affirm TRT’s discretion to evolve methods to >> address future risks. >> >> These updates will better align the AGB with NCAP2 and ICANN Board >> guidance, while improving transparency, security, and technical rigor in >> handling name collisions. >> >> The SSAC appreciates the efforts of the ICANN org and Subsequent >> Procedures IRT, and we are available for further discussion. >> >> Link: >> https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committe… >> . >> >> >> Best, >> >> Matthias >> _______________________________________________ >> ALAC mailing list -- alac(a)icann.org >> To unsubscribe send an email to alac-leave(a)icann.org >> >> At-Large Online: http://www.atlarge.icann.org >> ALAC Working Wiki: >> https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… >> _______________________________________________ >> 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. > > > _______________________________________________ > ALAC mailing list -- alac(a)icann.org > To unsubscribe send an email to alac-leave(a)icann.org > > At-Large Online: http://www.atlarge.icann.org > ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… > _______________________________________________ > 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 1

Re: Meeting invitation: ALAC Monthly Call on Tuesday, 22 July 2025 at 13:00 UTC
by Matthias M. Hudobnik July 22, 2025

July 22, 2025

Dear Colleagues, I need to apologize for not being able to attend the ALAC Call today. However, you should have received my report. Thanks a lot and have a nice day! Best, Matthias

1 0

SSAC Report
by Matthias M. Hudobnik July 22, 2025

July 22, 2025

Dear Colleagues, see below my report! Best, Matthias Publications: SAC129: SSAC Comments on GNSO Domain Name Registration Data Accuracy Concept Proposal 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. 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. SAC128: SSAC Comments on Draft Governance Document for the Recognition, Maintenance, and Derecognition of RIRs 1. General Support * SSAC supports the document's goal to clarify RIR recognition, obligations, and derecognition procedures. * The document is a significant improvement over the current ICP-2 policy. 2. General Comments * Inconsistent Detail Levels: The document alternates between high-level principles and detailed operational guidance, which may cause ambiguity. * Recommendation: Clearly separate high-level principles from operational details, and consider placing implementation specifics in supplementary documents. 3. Specific Article Comments Article 2.3(b)(i) - Derecognition Proposal Process * Concern: 25% threshold for submitting derecognition proposals could be exploited for disruptive or repetitive submissions. * Recommendation: Introduce safeguards such as cooldown periods and preliminary assessments. Article 4.1(l) - Continuity Requirements * Concern: Vague terms like "sufficient" may allow non-functional data sharing formats. * Recommendation: Define clearer standards for continuity and data sharing expectations. Article 5.3(a) - Transfer of Services Post-Derecognition * Concern: Requiring a smooth transfer from a derecognized RIR may be unrealistic in contentious situations. * Recommendation: Incorporate support structures similar to ICANN's EBERO model to ensure continuity and data escrow during transitions. 4. Transparency * The document includes disclosures of interest, acknowledgements, and identifies any member withdrawals, ensuring transparency and consensus within SSAC. SSAC127: DNS Blocking Revisited What Is DNS and DNS Blocking? * The Domain Name System (DNS) translates human-readable domain names (e.g., example.com) into IP addresses that computers use to communicate. * DNS blocking is a technique to restrict access to online content by interfering with DNS queries. This can involve: * * Pretending a domain doesn't exist. * Providing false IP addresses. Why DNS Blocking Is Used * Often implemented because it's technically simple and low-cost. * Commonly used by governments and organizations for: * * Public safety (e.g., blocking illegal content). * Censorship or regulation of online resources. How DNS Blocking Works * By altering the behaviour of recursive resolvers (DNS servers that respond to user queries). * DNS blocking modifies the translation of a domain name into an IP address, effectively preventing access via DNS. Effectiveness and Limitations * Blocking only works if users rely on the DNS infrastructure where the block is applied. * It can be bypassed through: * * Alternative DNS resolvers. * VPNs or other routing methods. * Important: DNS blocking does not remove the content--only access through DNS is affected. Potential Side Effects * Collateral damage: Can impact unrelated services or domains. * Cross-border effects: May unintentionally affect users outside the blocking jurisdiction. * User confusion: May appear as a technical error, leading to risky behavior. * Legal ambiguity: Laws vary; determining whether DNS blocking is lawful or constitutes censorship depends on local context. SSAC Recommendations Recommendation 1: Any entity implementing DNS blocking should fully understand its technical and policy implications. Recommendation 2: Entities implementing DNS blocking (governments, ISPs, organizations) should follow these principles: * Clear Objectives: Ensure DNS blocking aligns with intended goals. * Defined Policy: Maintain transparent, reviewed processes for deciding what to block. * Minimize Damage: Use methods that avoid overblocking or harming unrelated users. * Respect Boundaries: Do not affect users or networks outside your administrative control. Recommendation 3: Recursive DNS server operators should use Extended DNS Error (EDE) codes to inform users when DNS blocking is active and aid troubleshooting. This report updates previous SSAC advisories (SAC050 and SAC056 from 2011-2012) to reflect changes in technology and growing use cases for DNS blocking. Final reviews: SSAC's comment on the New gTLD Applicant Guidebook (AGB) has closed and the document is finalized as SAC130 * It will be published this week. Ongoing work parties: * DNSSEC Operational Considerations Work Party * Open-Source Software Work Party * Responsible Integration of External Technologies into the DNS SSAC Membership Applications: The application deadline is closed now and potential candidates are being assessed by the Membership Selection Committee. SSAC Workshop: Will be held in September in Mexico City.

1 0

Re: [ALAC-Announce] ALAC Monthly Call
by Pari Esfandiari July 22, 2025

July 22, 2025

Dear Colleagues, Please find the EURALO Regional Report pasted below. I’m sharing it in advance, as I’m traveling today and will be joining the meeting late. Warm regards, *Pari Esfandiari* *EURALO Regional Report – July 22, 2025 - Prepared by Pari Esfandiari* Over the past two months, Europe has experienced a high level of Internet governance activity, with strong engagement from EURALO and its members across key regional and global events. - *EuroDIG 2025 (Strasbourg, May):* Regional stakeholders addressed pressing issues. Olivier Crépin-Leblond and I co-hosted a flash session titled *"From Principles to Practice: Core Internet Values in the Age of AI."* - *RIPE 90 (Lisbon, May): *This meeting offered opportunities for cross-community outreach and closer collaboration between RIPE NCC and the At-Large community. Work is currently underway to revise our existing MoU and co-organize joint webinars to strengthen engagement. - *ICANN83 (Prague, June): *EURALO held its Annual General Meeting and the NextGen program. EURALO also hosted a well-attended Readout session to reflect on key developments. - *IGF 2025 (Lillestrøm, June):* EURALO had strong visibility and presence: - I participated in the GigaNet high-level debate *“Should WSIS End?”* - Represented the Dynamic Coalition on Core Internet Values (DC-CIV) and other DCs during the Main Session. - Moderated panel on *“Bridging Internet & AI Governance”*, with speakers including Vint Cerf. - *WSIS+20 High-Level Event (Geneva, July):* The formal WSIS+20 review process was launched. EURALO members contributed to discussions. - *Policy and Legislative Developments:* The European Parliament continues to shape major digital legislation with significant implications for DNS policy, Internet governance, and end-user rights. - *Looking Ahead: *ICANN84 will be held in Dublin in October, providing an opportunity to elevate European priorities and voices in global policy discussions. EURALO is finalizing its FY26 Outreach Strategy, strengthening cooperation with RIPE NCC, and actively preparing for WSIS+20 and ICANN84 to ensure the continued visibility of regional perspectives in global forums. - We will be holding a EURALO Board meeting immediately following this session, where additional issues and strategic actions will be discussed. -- Pari Esfandiari President *Global TechnoPolitics Forum <http://www.technopolitics.org> * *Pario <http://www.parioconsultants.com>- Architects of Ideas* info(a)TechnoPolitics.org <info(a)technopolitics.org> *Linkedin Profile <https://www.linkedin.com/in/pariesfandiari/>* Tel: +1-202*-735-1415* (Office) : +1-310-435-0888 (Cell) : +44-731-210-4049 (Cell)

1 1