May 2025 - ALAC - lists.icann.org

ALAC Liaison to the GAC updates: GAC Joint Webinar Invitation, Prague Bilateral Agenda, and May Briefing – Request for Input by 5 May
by Joanna Kulesza July 21, 2025

July 21, 2025

Dear Colleagues, I hope this message finds you well. I am writing to share several updates and to seek your input on key upcoming ALAC engagement opportunities with the GAC: ------------------------------ *1. Invitation to ASO-GAC Webinar on the RIR Governance Document (13 May, 13:00 UTC)* Marco Hogewoning, GAC VC, has extended an invitation to ALAC to participate in a *joint ASO-GAC webinar* on the proposed *Governance Document for the Recognition, Maintenance, and Derecognition of RIRs* (a revision of ICP-2). The session will take place on *Tuesday, 13 May at 13:00 UTC* for 90 minutes. The webinar will provide an overview of the draft, which is currently open for public comment until *27 May 2025*: 🔗 ICANN Public Comment Page <https://www.icann.org/en/public-comment/proceeding/governance-document-for-…> 🔗 ICP-2 Background <https://www.nro.net/policy/internet-coordination-policy-2/> Given the relevance of this topic to ALAC, I strongly encourage participation. Please also consider whether ALAC should offer a brief intervention during the session—perhaps by *Jonathan Zuck*, ALAC Chair, should he be willing and available. ------------------------------ *2. GAC-ALAC Bilateral Meeting at ICANN83 – Draft Agenda and Speaker Suggestions* Kristina has proposed the following agenda for our bilateral session, with two suggested ALAC speakers: - *Applicant Support Program (ASP) – Equity in the Next gTLD Round [recommended]* *Suggested Speaker: Avri Doria* - *DNS Abuse Mitigation – Policy, Enforcement, and End User Protection* - *Universal Acceptance (UA) and the Multilingual Internet* - *Domain Name Registration Data – RDRS, Accuracy, and Access* - *Digital Inclusion and Capacity Building* - *Public Interest Frameworks and Advisory Roles * *[recommended]* *Suggested Speaker: Justine Chew* Your comments and additional suggestions are welcome. Please kindly note that given our usual, limited timing for these sessions, we are likely to cover no more than two topics of shared interest. My recommendations, as your liaison to the GAC, are noted above. ------------------------------ *3. May Regulatory Updates Briefing – Call for Input* Together with our GAC colleagues, we are ready to welcome your suggestions for the topic to be covered during our May Regulatory Updates Briefing <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/180715827/G…> session, the last one before our Prague meeting. Zeina has originally proposed a focus on *infrastructure governance in the Middle East* as one of the topics for us to consider during these sessions, whereas we await further ideas from the Governmental Engagement team. I would appreciate any additional suggestions from the ALAC regarding policy topics or regional insights that should be reflected in this session. ------------------------------ *Kindly provide your feedback on the above items by Monday, 5 May.* Thank you for your attention to this matter and lasting support. -- Kind regards, Joanna Kulesza ------------------- Joanna Kulesza, PhD Professor of International Law Lodz Cyber Hub / University of Lodz Law School / Poland www.cyber.uni.lodz.pl (EURALO ALS 341) ALAC / EURALO / ALAC Liaison to the GAC

10 18

URGENT: Approved Resolutions | Special Meeting of the ICANN Board | 19 May 2025 // ICANN Reviews Program Path
by Olivier MJ Crépin-Leblond June 2, 2025

June 2, 2025

Dear Colleagues, I don't often write to the ALAC mailing list as I mostly observe what's going on here, but seeing what seems to be no action on a Core Accountability measure of ICANN being simply cast aside, and with possibly only three days to go, with neither action on the OFB working group, or the ALAC mailing list, it is time for me to point something out urgently. On 19 May 2025, the ICANN Board held a special meeting in which it passed Resolutions 2025.05.19.01 – 2025.05.19.06. These can be read at: https://www.icann.org/en/board-activities-and-meetings/materials/approved-r… Summarised: The ICANN Board has directed its President and CEO to design a review program aimed at improving *accountability, transparency, and effectiveness* within ICANN, with an emphasis on community-led processes. To achieve this, a *community dialogue* will be initiated to identify key areas for improvement. Key resolutions include: * *Progressing the Continuous Improvement Program* (CIP) while deferring Organisational Reviews until the first cycle is complete. * *Concluding the Pilot Holistic Review* (PHR), allowing ongoing work within SOs and ACs on continuous improvement. * *Deferring ATRT4, SSR, and RDS Specific Reviews* until the community dialogue informs next steps. * *Considering future actions* on Organisational Reviews after one CIP cycle. * *Planning a community dialogue* on ICANN Reviews, incorporating input from the ICANN84 Public Meeting. * *Recognising contributions* from the PHR Team and the broader ICANN community in shaping review processes. The rationale says that the Board's decisions reflect a commitment to *collaborative review mechanisms* that ensure ICANN remains effective and transparent. Unfortunately, in practice, the resolution that the Board has passed is likely to foster exactly the opposite. This decision was transmitted to SO/AC Chairs and can be read at: https://atlarge.icann.org/en/advice_statements/14007 The Board took this decision *against *ALAC Advice provided at: https://atlarge.icann.org/en/advice_statements/14003 So what are we to do, as an Advisory Committee, besides being shocked and stunned? The ICANN Board has a duty to act according to the ICANN Bylaws. The ICANN Bylaws mandate Periodic Review Mechanisms and also mandate Reconsideration Requests as part of Article IV of its Bylaws published on https://www.icann.org/en/governance/bylaws#article4 * Section 4.2. RECONSIDERATION * Section 4.4. PERIODIC REVIEW OF ICANN STRUCTURE AND OPERATIONS * Section 4.5. ANNUAL REVIEW * Section 4.6. SPECIFIC REVIEWS The periodicity of Reviews is mandated in order to avoid situations where reviews would be stopped altogether. "Section 4.6 (b) (vi) The Accountability and Transparency Review shall be conducted no less frequently than every five years measured from the date the previous Accountability and Transparency Review Team was convened." The last Accountability and Transparency Review Team (ATRT3) was appointed on 20 December 2018: https://www.icann.org/en/announcements/details/members-announced-for-the-th… Thus the next ATRT should have been appointed by "no less frequently than every five years" thus by *20 December 2023*. The Board at the time decided to delay the start of ATRT4. We are now *18 months late* to start this. It is now continuing to extend the delay to the start of ATRT4, thus contravening Bylaw Section 4.6 (b) (vi). According to: /Section 4.2 (c) A Requestor may submit a request for reconsideration or review of an ICANN action or inaction ("Reconsideration Request") to the extent that the Requestor has been adversely affected by: (i) One or more Board or Staff actions or inactions that contradict ICANN's Mission, Commitments, Core Values and/or established ICANN policy(ies);/ The Board is acting against its own Bylaws. The ALAC should submit a *Reconsideration Request *without further delay, based on the fact that the Board is now acting against its own Bylaws. A *Community Reconsideration Request* might have even more weight, but we have to be quite lucid about the fact that some other SOs/ACs/SGs, such as the Country Code Name Supporting Organisation (ccNSO) and the Registries Stakeholder Group (RySG) would oppose such Community Reconsideration as they have expressed their support for interrupting the review cycle. I have marked this message as "URGENT" because whilst the Bylaws mention a 30 day period for Reconsideration Requests, the Web Page explaining the reconsideration process ( https://www.icann.org/resources/pages/mechanisms-2014-03-20-en ) mentions only 15 days - obviously an error somewhere, but you never know, with ICANN... I'll remind everyone: whilst Bylaw-mandated Reviews might be tedious, repetitive and introduce a large workload on the Community, they are *Bylaw-mandated* for a reason: in order to make sure that *ICANN remains Accountable, Transparent, enhancing Public Trust*, and to ensure its decision-making processes remain *open, fair, and aligned with the public interest.* The reason given in relation to delaying ATRT4 is that ICANN Org is struggling to implement all of the recommendations made in past reviews, and ATRT3 in particular. This failure of ICANN Org to implement recommendations is unacceptable. It is about time that the ALAC calls this out. It used to be the US Department of Commerce (DoC) that used to do this and bang on the table. Unfortunately we now are reaching a level of complacency that is contravening ICANN's own Bylaws and this has to stop. I trust that you, the ALAC acting in the best interests of Internet users worldwide, will support filing a Reconsideration Request as soon as possible. Kindest regards, Olivier Crépin-Leblond (writing in my own personal capacity)

12 22

GNSO Council 11 June 2025 meeting agenda is out
by Justine Chew May 31, 2025

May 31, 2025

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 to 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…> ------

1 0

ccNSO Newsletter Issue 60 Is Out Now!
by Laura Margolis May 27, 2025

May 27, 2025

Dear All, Issue 60 of the ccNSO Newsletter (May 2025) is out now. In this issue: - Final report and recommendations from the Policy Gap Analysis Working Group - Abuse and Universal Acceptance: A reminder about useful resources for ccTLDs - A preview of ccNSO sessions at ICANN83 in Prague - Details on the ccNSO Buddy Program to support newcomers - Highlights from the latest ccNSO Council meeting - Interview with Jodi Anderson (.nz) on “How We Meet” - A warm welcome to Sri Lanka’s IDN ccTLD (.ලංකා) as the newest ccNSO member Read the newsletter now: https://icann-community.atlassian.net/wiki/x/Jht2Bg I cannot upload it to the wiki space now because I have some issues with that, but will post it shortly. Thank you! Best regards, -- *Laura Margolis* ALAC Liaison to ccNSO margolisl(a)gmail.com +59899690992 Teams: lauri.margolis ccNSO Liaison Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…>

1 0

SSAC has published SAC127: DNS Blocking Revisited
by Matthias M. Hudobnik May 24, 2025

May 24, 2025

Hi colleagues, the SSAC has published SAC127. ### SSAC has published SAC127: 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: o Pretending a domain doesn't exist. o 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: o Public safety (e.g., blocking illegal content). o Censorship or regulation of online resources. How DNS Blocking Works · By altering the behavior 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: o Alternative DNS resolvers. o 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: o A. Clear Objectives: Ensure DNS blocking aligns with intended goals. o B. Defined Policy: Maintain transparent, reviewed processes for deciding what to block. o C. Minimize Damage: Use methods that avoid overblocking or harming unrelated users. o D. 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. Link to the report: https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committe…. Have a nice day! 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

Summary Report ccNSO meeting #217
by Laura Margolis May 21, 2025

May 21, 2025

Dear All, I hope you are doing well. Please find below a summary of recent developments within the ccNSO Council, including highlights from the latest Council Meeting (#217), which took place on Thursday, 15 May 2025. 🔹*Background and supporting documents* Council workspace for this meeting: https://icann-community.atlassian.net/wiki/x/D4wlBg ccNSO correspondence: statements and responses: https://ccnso.icann.org/en/about/statements.htm Zoom recording <https://icann.zoom.us/rec/play/Ukw6vuNynQ1QWuN5QTE1DRNUrwgvsexzpV7d4-b0pcsK…> *Agenda* <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99711461/AL…> In this opportunity, I would like to *highlight* the following topics: - A new application from IDN ccTLD from Sri Lanka was accepted and it is a new member of the ccNSO. - Special Council Election (Europe): Nigel Roberts appointed without election as sole candidate. - Chris Disspain will be the new chair of the Triage Committee. - Guillermo Lama will be the new TLD-OPS Vice Chair - ICANN UA Expert Working Group Nomination: A call for Expressions of Interest has been launched; selection by 30 May 2025. 🔹*How we meet:* Here is a link to the document ccNSO worked on How we meet <https://docs.google.com/document/d/141FfWTZFaPhUDSd1cAmQSN8Xt2VEtczbdH15t5U…> 🔹*PGA Working Group:* This group ended the PGA Final Report <https://docs.google.com/document/d/1ouZnDqzikDxnuhlz5VPw0uWvqdCxX2Giy5mEGN4…> and the council adopted final review. The 3 topics that group will be working on are: · Maintain an Overview of policies, related guidelines and best practices relevant for ccTLDs. · Establish Study groups on IANA Public Records and disaster recovery. · Implement a Process to document and handle Gaps. 🔹 *Public Comments:* · How we meet <https://docs.google.com/document/d/141FfWTZFaPhUDSd1cAmQSN8Xt2VEtczbdH15t5U…> · RIR’s Governance – by consensus, no comment will be submitted, agreement to monitor impacts and engage informally with ASO. · CSC Changes for amending IANA Naming Service Level Agreement A support comment will be submitted 🔹*Budget Concerns Raised - FY26 approved Budget:* After the discussion at the council meeting, on May 15th., a letter was sent to Xavier Calvez and Kurtis Lindqvist, regarding the ccNSO concerns on the recently approved FY26 ICANN Budget. https://www.icann.org/en/system/files/files/adopted-icann-budget-fy2026-pub… The ccNSO Council and the SOPC expressed concerns regarding the recently approved FY26 ICANN Budget, noting a significant increase in expected funding and expenses—from $142 million in the December 2024 draft to approximately $150 million in the final version. Key issues include the projected 3% increase in transactions, a rise in staffing levels shortly after prior cost-cutting layoffs, and the introduction of major changes after the public comment period. The groups have requested an urgent meeting with ICANN leadership to address these concerns within the 21-day rejection action period. 🔹*Policy Development ccPDP4-IDN and ccPDP3-RM:* ccPDP3-RM likely to be adopted by the Board at ICANN Prague. PDP4 progressing at a faster pace. 🔹*Priorities Moving Forward* - Engage with ICANN leadership regarding the FY26 budget. - Continue advancing work plans across working groups. - Support community involvement in active policy development processes. - Prepare for *ICANN83 in Prague*. Please reach out if you have any questions or would like more information on any of the topics mentioned above. Thank you! Best Regards, *Laura Margolis* ALAC Liaison to ccNSO margolisl(a)gmail.com Mobile +59899690992 ccNSO Liaison Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…> alac.icann.org

3 3

Fwd: [council] GNSO Policy Briefing ICANN83 Edition
by Justine Chew May 20, 2025

May 20, 2025

For everyone's attention. Kind regards, Justine --------- ---------- Forwarded message --------- From: Devan Reed via council <council(a)icann.org> Date: Wed, 21 May 2025, 04:34 Subject: [council] GNSO Policy Briefing ICANN83 Edition To: council(a)icann.org <council(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Dear All, On behalf of the GNSO Team, I am happy to report that the GNSO Policy Briefing for ICANN83 is now available for download at: https://go.icann.org/gnsobriefing. Happy Reading! All the best, John R. Emery, Ph.D. Policy Development Support Senior Specialist Generic Names Supporting Organization (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org _______________________________________________ council mailing list -- council(a)icann.org To unsubscribe send an email to 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.

1 0

Summary Report for GNSO Council 15 May 2025 meeting
by Justine Chew May 19, 2025

May 19, 2025

Dear all, Please find below the updated final agenda for GNSO Council's 15 May 2025 meeting, followed by my summary report on Matters of Interest. Happy to answer and questions on this thread or during the next ALAC Monthly Call on 20 May. *GNSO Council Meeting #5 of 2025 held on 15 May 2025 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/265846872/G…>* *Full Agenda* <https://icann-community.atlassian.net/wiki/x/GKafBg>* | * *Documents* <https://icann-community.atlassian.net/wiki/x/0KefBg>* | * *Motions* <https://icann-community.atlassian.net/wiki/x/LKifBg> - 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 * - Aspirational Statement - *Item 4: COUNCIL VOTE - Deferral of the Next Steps of Phase Two of the Review of All Rights Protection Mechanisms (RPMs) in All New gTLDs Policy Development Process (PDP)* *for an Additional Six Months* - *Item 5: COUNCIL DISCUSSION - Han Script Character gTLDs (Recommendation 3.17)* - *Item 6: COUNCIL DISCUSSION - Council Alignment on the Future of Reviews* - *Item 7: COUNCIL UPDATE: Subsequent Procedures Implementation Review Team on Recommendation 36.4* - *Item 8: Any Other Business* 8.1 - ICANN83 Planning - 8.2 - GAC Liaison updates - *8.3 - Update on the WSIS+20 work* - 8.4 - Whois Implementation Advisory Group update - *8.5 - Registration Data Request Service (RDRS) Standing Committee Report - open question of public comment* - *8.6* - HRIA of Transfer Policy Review <https://gnso.icann.org/sites/default/files/policy/2025/draft/draft-transfer…> - 8.7 - Chair update * Summary to the ALAC on GNSO Council Meeting #5 of 2025 held on 15 May 2025* For brevity, I will just highlight a few things here. *1. Consent Agenda* - Council adopted its aspirational statement <https://gnso.icann.org/sites/default/files/policy/2025/draft/draft-updated-…> . *2. Review of All Rights Protection Mechanisms (RPMs) in All New gTLDs* - Council resolved to defer next steps on Phase Two of the RPMs PDP – specifically the launch of a Charter Drafting Team – for an additional 6-month period beginning on 15 May 2025. Council may revise the deferral period depending on the progress of the RPM Phase 1 IRT and/or the outcome of Council’s prioritization exercise. *3. Han Script Character gTLDs* - During Council deliberations at its April meeting, some Councilors suggested an Expert Working Group (EWG), as an alternative to the GGP, to determine the guidance necessary to allow Han single characters to proceed. Staff had provided an update to the Council where an additional mechanism was identified - the External Expert Advice (EEA) process as captured in Article 13 of the ICANN Bylaws. - After much deliberation, Council decided to the matter be referred back to ICANN org with a recommendation for ICANN to establish an Expert WG using the EEA process. Council Leadership offered to draft a letter to org, to that effect, to address the need for guidance necessary to allow Han single characters to proceed without introducing confusion risks that rise above commonplace similarities. *4. Future of Review* - Council discussed the potential options on the status of Reviews, including: - Status Quo: Continue on the current path, kick off ATRT4 and bifurcate out the Pilot Holistic Review (structural review) and the Continuing Improvement process. - Change Option 1: Repurpose ATRT4 to have it undertake the structural review, and as a result wind down the Pilot Holistic Review (with the Continuing Improvement process independent and functioning). - Change Option 2: Suspend all reviews and kick off a Review of Reviews to determine what reviews are necessary at this time (including a structural review). - After some discussion, Council leaned towards both Change Option 1 and Change Option 2. *5. Registration Data Request Service (RDRS)* - After some discussion, it was decided that the RDRS Standing Committee Report should be put out for public comment considering that it may contain some recommendations. 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 Mon, 5 May 2025 at 23:34, Justine Chew <justine.chew.icann(a)gmail.com> wrote: > Dear all, > > Due to technical issues with my GNSO Liaison workspace which prevent me > from updating its webpage, I am informing you of the agenda of the GNSO > Council 15 May 2025 meeting (as set out below), followed by a curation > of the matters of interest therein, by way of a googledoc. > > GNSO Council Meeting #5 of 2025 held on 15 May 2025 > > Full Agenda <https://icann-community.atlassian.net/wiki/x/GKafBg> | > Documents <https://icann-community.atlassian.net/wiki/x/0KefBg> | > Motions <https://icann-community.atlassian.net/wiki/x/LKifBg> > > - > > 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 > - > > Aspirational Statement > - > > Item 4: COUNCIL VOTE - Deferral of the Next Steps of Phase Two of the > Review of All Rights Protection Mechanisms (RPMs) in All New gTLDs Policy > Development Process (PDP) for an Additional Six Months > - > > Item 5: COUNCIL DISCUSSION - Han Script Character gTLDs > (Recommendation 3.17) > - > > Item 6: COUNCIL DISCUSSION - Council Alignment on the Future of Reviews > - > > Item 7: COUNCIL UPDATE: Subsequent Procedures Implementation Review > Team on Recommendation 36.4 > - > > Item 8: Any Other Business > - > > 8.1 - ICANN83 Planning > - > > 8.2 - ccNSO and GAC Liaison updates > - > > 8.3 - Whois Implementation Advisory Group update > - > > 8.4 - Registration Data Request Service (RDRS) Standing Committee > Report - open question of public comment > - > > 8.5 - Chair update > > > *Matters of Interest *can be found at this link: GNSO Council 15 May 2025 > Meeting > <https://docs.google.com/document/d/158vXTzz7eJvj_9Gi2zanaGxBMk0nRcFuDl2sSdX…> > > This Council meeting will take place on *15 May 2025 **at 05:00 UTC*: > https://tinyurl.com/knke3w 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…> > ------ > > > >

1 0

SSAC2025-02: SSAC Public Comment on How we Meet: An Initial Project
by Matthias M. Hudobnik May 12, 2025

May 12, 2025

Hi colleagues, the SSAC has published SSAC2025-02: SSAC Public Comment on How we Meet: An Initial Project Report. The SSAC submitted its response to the public comment proceeding on 09 May 2025. This correspondence provides a summary of the SSAC’s positions on the specific proposals detailed within the "How We Meet: An Initial Project Report." Proposals SSAC Supports: · Topic #1: Shorten the Community Forum by one day o 1.1 Shortening the Community Forum by one day. o 1.2.a Moving the Public Forum and Geopolitical Forum earlier in the meeting, to the same day as the Welcome Ceremony and Executive Q&A session, to limit the need for the main ballroom to a single day. o 1.2.b Scheduling any community wrap-up sessions that may be needed in the final block at the end of the fifth and last day. o 1.2.c Adding a new Board-community engagement session open to everyone, to discuss issues of broad common interest, to limit the need for the Board to discuss the same topics in isolation with individual groups. · Topic #2: Prioritize economical and predictable meeting locations o 2.1.a Prioritizing meeting locations that offer economical travel, venue, and accommodation options while respecting the need to rotate ICANN Public Meetings across the various geographic regions, and on the understanding that this could mean returning to the same venue within a specific geographic region. o 2.1.b Returning to previous locations where this is feasible and within the geographical rotation requirement. ■ SSAC Additional Feedback: In selecting venues, countries that are not consistent with ICANN core values of diversity and inclusion should not be selected. · Topic #3: Establish a policy for automatic shift to online meetings o 3.1 Establishing a policy to automatically shift an ICANN Public Meeting to an online format, should unforeseen circumstances arise that necessitate moving a meeting from a planned venue. Proposals SSAC Does Not Support: · Topic #4: Convert one ICANN Public Meeting to a virtual-only format o 4.1 Converting one ICANN Public Meeting per year to an online format. o 4.2.a Conducting an online-only meeting once every few meetings (e.g., every fourth/fifth/sixth ICANN Public Meeting). Proposals for which SSAC Did Not Provide a Response: · Topic #1: Shorten the Community Forum by one day o 1.3 Suggestions for how a reduced 5-day Community Forum can also accommodate improved Board-community interactions while maintaining an adequate number of intra-community work sessions. · Topic #4: Convert one ICANN Public Meeting to a virtual-only format ○ 4.2.b Starting with a pilot of a fourth ICANN Public Meeting in a calendar year, but holding this fourth meeting online. · ○ 4.2.c Exploring a mixed-model where all the sessions are held online but attendees have the option of gathering in one physical location to maximize networking and relationship-building opportunities. The SSAC appreciates the opportunity to provide input on the "How We Meet" initiative and looks forward to continued engagement on this important topic. Link here: https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committe… This correspondence mirrors the SSAC’s public comment submission. Link here: https://www.icann.org/en/public-comment/proceeding/how-we-meet-reviewing-th… Have a nice day! Best, Matthias ______________________________ Ing. Mag. Matthias M. Hudobnik FIP • CIPP/E • CIPT • DPO • CIS LA HYPERLINK "mailto:matthias@hudobnik.at"matthias(a)hudobnik.at http://www.hudobnik.at @mhudobnik

1 0

Excellent article by Joanna Kulesca
by Judith Hellerstein May 12, 2025

May 12, 2025

4 3