- OFB-WG - lists.icann.org

ICANN Board Bylaws Amendments and matters relating to the Review of Reviews
by Olivier MJ Crépin-Leblond May 24, 2026

May 24, 2026

Dear Jonathan, I have listened to this week's OFB-WG ( https://icann-community.atlassian.net/wiki/x/NIHSQQ ) call recording since I was unable to make it, as I was in transit at the time. This message serves as the comments I would have made, had I attended the call in person. I would like to put it on record at the OFB WG and that it be noted at the next OFB-WG meeting. *Presentation: Update on “Transition Article on Reviews” - Approved Resolutions | Regular Meeting of the ICANN Board | 3 May 2026 <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> - Justine Chew - (15 mins) * In summary: * cognisant that ICANN is knowingly acting in contravention of its Bylaws by suspending its Bylaw-mandated Reviews, the ICANN Board proposed a "Bylaws Transition Article" in an attempt to retroactively legitimise this suspension. * In the Public Consultation, the ALAC commented on this proposal and raised significant concerns. * Prior to this, the ALAC had filed an Empowered Community Reconsideration Petition (June 2025) calling for reinstatement of ATRT4. * This Petition was summarily dismissed by the other members of the Empowered Community without explanation. * The ALAC has since participated in the ongoing Review of Reviews process. After consulting the Community, the Board approved a new Transition Article on 3 May 2026 (to be inserted as Article 27.6), triggering the Standard Bylaws Amendment process and therefore the Empowered Community procedures.*In proceeding with this approval, the ICANN Board has also ignored most, if not all of the ALAC Advice the ALAC provided during the Public Consultation.* Listening to the OFB-WG call recording, several points explained by Justine, have stood out that really shocked me. *Timelines and Consequences* The timelines adopted by the Board are deeply troubling: * The 12‑month suspension period begins only once the Bylaws amendment is formally approved. * This suspension can be extended by up to another year if the Board accepts Review of Reviews recommendations, or if 4 of 7 SOACs request further delay. * Only after this period would the ATR (formerly ATRT) begin - within 90 days. * The Consumer Trust Review (CCTR) would not begin until two years after 500 strings are delegated or two years (if >2000 applications are received) after 25% of them are delegated. The practical effect is stark: * ATRT3 delivered its Final Report in May 2020* - six years ago*. * The Pilot Holistic Review began in May 2024 and was halted in May 2025* - one year ago*. * One might have to wait up to another 2 years + 3 months for another ATR to take place, a process that will take 1 year to complete once it starts - thus the next recommendations from an ATR might not come before *September 2029* - a *nine‑year gap* between ATRT3 and ATR4. * With the Board unwilling to launch another Consumer Trust (CCTR) review at the same time as ATR4, we'd need to wait until ATR4 is finished for the CCTR to start. Thus the next CCTR could be delayed until *2031*, creating a *13‑year gap* since the last CCT Review (2018). This is an *unacceptable *erosion of ICANN’s accountability mechanisms. Review of Reviews CCG Discussion *ROR Review - Avri Doria and Jonathan Zuck- ALAC representatives on the Reviews of Reviews CCG - (10 mins)* In this Agenda Item of the call, both you and Avri drew attention to a critical issue: ICANN ORG has still not implemented Board‑approved CCT recommendations from *12 years ago*, and none of the proposed reforms to the review system address this failure. You said: "/none of the things that we're doing to reform the review system, which is changing the scope, changing the makeup of the teams, all these suggestions that have been put in there, none of them apply in any way to the recommendations that came out of the CCT review/". You then added: "/Nor are any of the… has there been any explanation as to why those things have not yet been implemented. So to me, that's still… there's still a hole, somehow/." [...] "/And we've talked about trying to review this in the future, as one of our reviews. How do we review ORG and their role in these things? But, I think that we need to do that as part of this review. / / And I don't know how to go about making that happen./" and Avri replied: "/And that's difficult. You know, there's constant pushback on the notion of reviewing ORG. / /Constantly./" *This should alarm everyone*. A system in which ICANN ORG fails to execute reviews, the Board wilfully suspends Bylaw‑mandated accountability mechanisms, and community advice is ignored, is not functioning as intended. *_Does this not immediately raise a red flag? _* We have a Board that wilfully ignores ICANN Bylaws and is unilaterally rewriting Bylaws "on the fly" to something that suits them - and disregards formal ALAC advice, preferring options that are further distancing ICANN from its key accountability mechanisms and pushing the whole concept of Reviews restarting further and further into the future. It is increasingly evident that ICANN’s resources (both ORG and significant parts of the Community) are *overwhelmingly *focused on launching the *next round of gTLDs*, which many expect to generate substantial revenue. This prioritisation is occurring at the expense of: * Policy development processes, * Implementation work, * Bylaw‑mandated Reviews, * Even At‑Large’s own rotation of RALO General Assemblies and Global At‑Large Summits. Meanwhile, the ICANN‑funded business-focussed Contracted Parties Summit continues uninterrupted. Had NTIA oversight still existed, *these governance failures would have triggered intervention long ago*. The Empowered Community was created precisely to replace that oversight and ensure the Board remains accountable to the Community - these changes being officially integrated into the ICANN Bylaws on 27 May 2016. One of these Rules is included in Article 25.1 of the ICANN Bylaws: Amendments to the Standard Bylaws This *requires *that the Empowered Community should give its green light for a standard Bylaw amendment to take place: /"25.1(d) Within seven days after the Board's approval of a Standard Bylaw Amendment ("*Standard Bylaw Amendment Approval*"), the Secretary shall (i) provide a Board Notice to the EC Administration and the Decisional Participants, which Board Notice shall contain the form of the approved amendment and the Board's rationale for adopting such amendment, and (ii) post the Board Notice, along with a copy of the notification(s) sent to the EC Administration and the Decisional Participants, on the Website. The steps contemplated in Article 2 of Annex D shall then be followed." /The Board approved the Standard Bylaw Amendment on 3 May 2026. Under Bylaws Article 25.1(d), the Board was required to notify the EC Administration and Decisional Participants within seven days of approving the Bylaws amendment—by 10 May 2026. I have seen no such notification, nor any posting on the EC website on https://www.icann.org/ec If this notice has not been issued, this constitutes yet another breach of the Bylaws, or at minimum an opaque process inconsistent with ICANN’s transparency obligations. *Next Steps* My proposed next step is clear: According to the ICANN Bylaws 25.1(e): /"(e) A Standard Bylaw Amendment shall become effective upon the earliest to occur of the following: [...] / /(iii) (A) An EC Rejection Notice is not timely delivered by the EC Administration to the Secretary pursuant to and in compliance with Section 2.4 of Annex D or (B) a Rejection Process Termination Notice is delivered by the EC Administration to the Secretary pursuant to and in compliance with Section 2.4(c) of Annex D, in which case the Standard Bylaw Amendment that is the subject of the Standard Bylaw Amendment Approval shall be in full force and effect as of the date immediately following the expiration of the Rejection Action Decision Period relating to such Standard Bylaw Amendment and the effectiveness of such Standard Bylaw Amendment shall not be subject to further challenge by the EC pursuant to the EC's rejection right as described in Article 2 of Annex D./ /(f) If an EC Rejection Notice is timely delivered by the EC Administration to the Secretary pursuant to and compliance with Section 2.4 of Annex D, the Standard Bylaw Amendment contained in the Board Notice shall be deemed to have been rejected by the EC. A Standard Bylaw Amendment that has been rejected by the EC shall be null and void and shall not become part of these Bylaws, notwithstanding its approval by the Board." /Under Article 25.1(e)–(f), the Empowered Community has the right to *reject a Standard Bylaws Amendment*. If the ALAC believes the Board’s action *undermines *ICANN’s accountability framework, then the ALAC *must *exercise this right. *In view of all of the above, I propose that the ALAC issue an EC Rejection Notice. **Rationale:* * The Board has wilfully ignored ALAC advice aimed at strengthening accountability. * The proposed changes unnecessarily prolong the suspension of Reviews. * The CCTR restart is pushed far into the future, despite Bylaw‑mandated implementation of the previous CCTR. * The Holistic Review - ICANN’s only comprehensive mandated review of ORG in over 20 years - has not been done. * The Board’s actions fail to comply with the requirements of the accountability mechanisms the Empowered Community was created to protect. The EC Powers were designed by the Community specifically to *make sure that the ICANN Board is subjected to Community Oversight* and the ALAC is only affirming this oversight. Rejecting the amendment is not confrontational; it is a legitimate, Bylaw‑mandated oversight function, a Right that the ALAC has - and if this Community feels that there is something *seriously wrong* with that is happening at the moment, then *it needs to act*. If the ALAC does not act when accountability is being eroded, then what purpose does the Empowered Community serve? What message does this send to the 6 billion Internet end users out there? In view of the serious consequences of inaction, the question before us is simple and unavoidable: *YES or NO. *Kindest regards, Olivier Crépin-Leblond (own views)

7 12

Call for Volunteers – by Monday May 18 – 15 UTC Review of SOI Code of Conduct-related Documents for ICANN86 Prep Week Board Engagement Session
by ICANN At-Large Staff May 17, 2026

May 17, 2026

Dear OFB WG members, On behalf of the OFB Co-Chairs and Justine Chew, we are seeking volunteers to review and comment on two related documents, which are: [1] ICANN Community Participant Code of Conduct Concerning Statements of Interest [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1FrejFxVF0VBl…>; which has been in operation since October 2025<https://www.icann.org/en/blogs/details/applying-icanns-community-participan…>; and {2] RySG's Draft ICANN Community Enforcement Guidance on the Code of Conduct Concerning Statements of Interest [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1Ci4xRHPLw_zK…> In preparation for ICANN Board Engagement Session [icann86.sched.com]<https://urldefense.com/v3/__https:/icann86.sched.com/event/2Lm0R/__;!!PtGJa…> during ICANN86 Prep Week, scheduled for Thursday, 21 May, from 18:00–19:00 UTC, volunteers are asked to consider the following questions during their review: 1. What can we share with the ICANN Board in response to their question below, in respect of document [1] ICANN Community Code of Conduct? 2. Is there anything that we can draw from document [2] RySG's Draft ICANN Community Enforcement Guidance, to include in our response to the Board's question below? ICANN Board's Question Transparent participation: Has there been any noticeable impact of the Community Code of Conduct on how your SOAC group or the community in general handle Statements of Interest (and their equivalents)? What does the community believe is needed as next steps, either from the SO/ACs or ICANN org, to support further integration and implementation of the Code? 3. Separately but related, what input can we provide to the RySG regarding their [2] Draft Enforcement Guidance document? As the preparation time for the ICANN Board Engagement session is extremely short, we ask that if you wish to volunteer, please send an email to the At-Large staff at ICANN (staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>), copying Claire Craig, (claireccraig(a)gmail.com<mailto:claireccraig@gmail.com>) and Bukola Oronti (bukkiepharworley(a)gmail.com<mailto:bukkiepharworley@gmail.com>) by Monday 18 May 2026, 15:00 UTC. Thank you for your support and participation! At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<http://atlarge.icann.org/> [signature_4211409830]

1 0

WEBINAR 21 MAY 14:00 UTC –From Access to Agency: Rethinking Digital Inclusion for Persons with Disabilities in the Age of AI--10am Eastern, 7am Pacific
by Judith Hellerstein May 14, 2026

May 14, 2026

HI All, Here is the information about the webinar I was mentioning to all today it is on May 21 at 1400 UTC. Title is "From Access to Agency: Rethinking Digital Inclusion for Persons with Disabilities in the Age of AI :. Registration is listed below Please register for Zoom meeting at https://us02web.zoom.us/meeting/register/KFURWYPUR1y838puqmLxpA <https://us02web.zoom.us/meeting/register/KFURWYPUR1y838puqmLxpA> RTT can be found here -- https://www.streamtext.net/player?event=cfi-dcad We will also have Sign interpretation for this event. We hope you will join us on May 21 at 1400 UTC (10am Eastern) . W Best, Judith _________________________________________________________________________ Judith Hellerstein, Founder & CEO Hellerstein & Associates 3001 Veazey Terrace NW, Washington DC 20008 Phone: (202) 362-5139 Skype ID: judithhellerstein Mobile/Whats app: +1202-333-6517 E-mail:Judith@jhellerstein.com Website:www.jhellerstein.com Linked In:www.linkedin.com/in/jhellerstein/ Opening Telecom & Technology Opportunities Worldwide Blue event banner for an Internet Governance Forum accessibility event. The graphic includes the IGF Dynamic Coalition on Accessibility and Disability logo in the upper left and a large faded GAAD logo with a keyboard icon in the background on the right. The main title reads: “From Access to Agency: Rethinking Digital Inclusion for Persons with Disabilities in the Age of AI.” The date, 21 May 2026, appears at the lower left. The a11ySIG logo is displayed in the lower right corner. <https://i0.wp.com/www.a11ysig.org/wp/wp-content/uploads/2026/05/dcad-gaad20…> REGISTER <https://us02web.zoom.us/meeting/register/KFURWYPUR1y838puqmLxpA> | REAL TIME TEXT <https://www.streamtext.net/player?event=cfi-dcad> | ADD TO CALENDAR <https://addcal.co/e/dcad-gaad2026> | PERMALINK <https://isoc.live/21073> On Thursday May 21, 2026 at 14:00-15:00 UTC the Internet Governance Forum Dynamic Coalition of Disability and Accessibilit <https://igf-dcad.org/>y (IGF-DCAD) and the Accessibility Special Interest Group <https://www.a11ysig.org/> (A11ySIG) will commemorate Global Accessibility Awareness Day <https://accessibility.day/> (GAAD) 2026, via webinar conversation with Dr. Vint Cerf titled ‘From Access to Agency: Rethinking Digital Inclusion for Persons with Disabilities in the Age of AI <https://www.a11ysig.org/gaad2026/%20%E2%80%8E> ‘ Over the past decade, global policy discourse has increasingly focused on expanding “internet access” as a cornerstone of digital inclusion. Yet for persons with disabilities, connectivity alone does not translate into meaningful participation. A user may be connected, possess a device, and have basic digital skills—and still remain excluded due to inaccessible design, incompatible platforms, or poorly implemented technologies. This gap calls for a conceptual shift: from access to agency. At the same time, the rapid integration of artificial intelligence into digital ecosystems is reshaping how users interact with technology. AI-powered tools—such as automated captioning, voice interfaces, and assistive agents—hold transformative potential. However, they also introduce new risks, including bias, unreliable outputs, and inaccessible design layers that may deepen exclusion if left unaddressed. Against this backdrop, accessibility must be reframed not as a technical afterthought, but as a governance, rights, and development issue—central to debates on AI, digital public infrastructure, and inclusive innovation. GUEST Dr. Vint Cerf – Chief Internet Evangelist, Google HOSTS Dr. Muhammad Shabbir – Co-cordinator, IGF-DCAD Judith Hellerstein – Co-cordinator, IGF-DCAD #gaad #dcad @a11sig #accessibility #pwds #ai _________________________________________________________________________ Judith Hellerstein, Founder & CEO Hellerstein & Associates 3001 Veazey Terrace NW, Washington DC 20008 Phone: (202) 362-5139 Skype ID: judithhellerstein Mobile/Whats app: +1202-333-6517 E-mail:Judith@jhellerstein.com Website:www.jhellerstein.com Linked In:www.linkedin.com/in/jhellerstein/ Opening Telecom & Technology Opportunities Worldwide -------- Forwarded Message -------- Subject: WEBINAR 21 MAY 14:00 UTC –From Access to Agency: Rethinking Digital Inclusion for Persons with Disabilities in the Age of AI--10am Eastern, 7am Pacific Date: Thu, 14 May 2026 13:47:38 -0400 From: Judith Hellerstein <judith(a)jhellerstein.com> Reply-To: judith(a)jhellerstein.com Organization: Hellerstein & Associates To: NA Discuss <na-discuss(a)atlarge-lists.icann.org> HI All, I thought NARALO Members might be interested in joining this webinar I am hosting From Access to Agency: Rethinking Digital Inclusion for Persons with Disabilities in the Age of AI :. Registration is listed below We will have human captioning and also International Sign interpretation for this event. We hope you will join us on May 21 at 1400 UTC (10am Eastern) . We will send the stream text links later. Please register for Zoom meeting at https://us02web.zoom.us/meeting/register/KFURWYPUR1y838puqmLxpA <https://us02web.zoom.us/meeting/register/KFURWYPUR1y838puqmLxpA> Best, Judith _________________________________________________________________________ Judith Hellerstein, Founder & CEO Hellerstein & Associates 3001 Veazey Terrace NW, Washington DC 20008 Phone: (202) 362-5139 Skype ID: judithhellerstein Mobile/Whats app: +1202-333-6517 E-mail:Judith@jhellerstein.com Website:www.jhellerstein.com Linked In:www.linkedin.com/in/jhellerstein/ Opening Telecom & Technology Opportunities Worldwide -------- Forwarded Message -------- Subject: [DCAD] WEBINAR 21 MAY 14:00 UTC – GAAD Event – From Access to Agency: Rethinking Digital Inclusion for Persons with Disabilities in the Age of AI Date: Tue, 12 May 2026 22:22:05 -0400 From: Joly MacFie via DCAD <dcad(a)lists.igf-dcad.org> Reply-To: Dynamic Coalition on Accessibility and Disability <dcad(a)lists.igf-dcad.org> To: Dynamic Coalition on Accessibility and Disability <dcad(a)lists.igf-dcad.org> CC: Joly MacFie <admin(a)igf-dcad.org> Blue event banner for an Internet Governance Forum accessibility event. The graphic includes the IGF Dynamic Coalition on Accessibility and Disability logo in the upper left and a large faded GAAD logo with a keyboard icon in the background on the right. The main title reads: “From Access to Agency: Rethinking Digital Inclusion for Persons with Disabilities in the Age of AI.” The date, 21 May 2026, appears at the lower left. The a11ySIG logo is displayed in the lower right corner. <https://i0.wp.com/www.a11ysig.org/wp/wp-content/uploads/2026/05/dcad-gaad20…> REGISTER <https://us02web.zoom.us/meeting/register/KFURWYPUR1y838puqmLxpA> | REAL TIME TEXT <https://www.streamtext.net/player?event=cfi-dcad> | ADD TO CALENDAR <https://addcal.co/e/dcad-gaad2026> | PERMALINK <https://isoc.live/21073> On Thursday May 21, 2026 at 14:00-15:00 UTC the Internet Governance Forum Dynamic Coalition of Disability and Accessibilit <https://igf-dcad.org/>y (IGF-DCAD) and the Accessibility Special Interest Group <https://www.a11ysig.org/> (A11ySIG) will commemorate Global Accessibility Awareness Day <https://accessibility.day/> (GAAD) 2026, via webinar conversation with Dr. Vint Cerf titled ‘From Access to Agency: Rethinking Digital Inclusion for Persons with Disabilities in the Age of AI <https://www.a11ysig.org/gaad2026/%20%E2%80%8E> ‘ Over the past decade, global policy discourse has increasingly focused on expanding “internet access” as a cornerstone of digital inclusion. Yet for persons with disabilities, connectivity alone does not translate into meaningful participation. A user may be connected, possess a device, and have basic digital skills—and still remain excluded due to inaccessible design, incompatible platforms, or poorly implemented technologies. This gap calls for a conceptual shift: from access to agency. At the same time, the rapid integration of artificial intelligence into digital ecosystems is reshaping how users interact with technology. AI-powered tools—such as automated captioning, voice interfaces, and assistive agents—hold transformative potential. However, they also introduce new risks, including bias, unreliable outputs, and inaccessible design layers that may deepen exclusion if left unaddressed. Against this backdrop, accessibility must be reframed not as a technical afterthought, but as a governance, rights, and development issue—central to debates on AI, digital public infrastructure, and inclusive innovation. GUEST Dr. Vint Cerf – Chief Internet Evangelist, Google HOSTS Dr. Muhammad Shabbir – Co-cordinator, IGF-DCAD Judith Hellerstein – Co-cordinator, IGF-DCAD #gaad #dcad @a11sig #accessibility #pwds #ai -- Joly MacFie Administrator Dynamic Coalition on Accessibility and Disability https://igf-dcad.org/ +1 218 565 9365

1 0

REMINDER: Meeting invitation: At-Large Operations, Finance and Budget Working Group (OFB-WG) Call on Thursday, 14 May 2026 at 14:00 UTC
by ICANN At-Large Staff May 14, 2026

May 14, 2026

From: OFB-WG <ofb-wg(a)icann.org> Reply-To: ICANN At-Large Staff <staff(a)atlarge.icann.org> Date: Friday, May 8, 2026 at 1:20 PM To: OFB-WG <ofb-wg(a)icann.org> Subject: [OFB-WG] Meeting invitation: At-Large Operations, Finance and Budget Working Group (OFB-WG) Call on Thursday, 14 May 2026 at 14:00 UTC Dear All, The next At-Large Operations, Finance and Budget Working Group (OFB-WG) Call is scheduled for Thursday, 14 May 2026 at 14:00 UTC for 60 mins. For other time zones: [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2p8e9d4__;!!PtGJab4!575kn4wk…> [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/y9wp3u7u__;!!PtGJab4!575kn4w…>HERE [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/38cn8v6m__;!!PtGJab4!575kn4w…> The agenda (to be updated) and call details can be found at: https://icann-community.atlassian.net/wiki/x/NIHSQQ [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/NIH…> Zoom Room: https://icann.zoom.us/j/92139943237?pwd=RR7XGoRSXgUGFm2K4QKyAFEp54AzQb.1 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/92139943237?pwd=RR7XGoRS…> / Password: OFBC#12345 Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN [streamtext.net]<https://urldefense.com/v3/__https:/www.streamtext.net/player?event=ICANN__;…> Wiki Workspace: https://community.icann.org/x/koTsBw Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community www.icann.org<http://www.icann.org/>

1 0

Meeting invitation: At-Large Operations, Finance and Budget Working Group (OFB-WG) Call on Thursday, 14 May 2026 at 14:00 UTC
by ICANN At-Large Staff May 8, 2026

May 8, 2026

Dear All, The next At-Large Operations, Finance and Budget Working Group (OFB-WG) Call is scheduled for Thursday, 14 May 2026 at 14:00 UTC for 60 mins. For other time zones: <https://tinyurl.com/2p8e9d4> <https://tinyurl.com/y9wp3u7u> HERE<https://tinyurl.com/38cn8v6m> The agenda (to be updated) and call details can be found at: https://icann-community.atlassian.net/wiki/x/NIHSQQ Zoom Room: https://icann.zoom.us/j/92139943237?pwd=RR7XGoRSXgUGFm2K4QKyAFEp54AzQb.1 / Password: OFBC#12345 Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN Wiki Workspace: https://community.icann.org/x/koTsBw Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community www.icann.org<http://www.icann.org/>

1 0

At-Large Operations, Finance and Budget Working Group (OFB-WG)
by ICANN Policy Calendar May 8, 2026

May 8, 2026

Dear All, The next At-Large Operations, Finance and Budget Working Group (OFB-WG) Call is scheduled for Thursday, 14 May 2026 at 14:00 UTC for 60 mins. For other time zones: <https://tinyurl.com/2p8e9d4> <https://tinyurl.com/y9wp3u7u> HERE<https://tinyurl.com/38cn8v6m> The agenda (to be updated) and call details can be found at: https://icann-community.atlassian.net/wiki/x/NIHSQQ Zoom Room: https://icann.zoom.us/j/92139943237?pwd=RR7XGoRSXgUGFm2K4QKyAFEp54AzQb.1 / Password: OFBC#12345 Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN Wiki Workspace: https://community.icann.org/x/koTsBw Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community www.icann.org<http://www.icann.org/>

1 0

Statement of Interest - Public Service Annoucement & Call to Action
by mike palage.com May 7, 2026

May 7, 2026

Hello All, After today’s CPWG call, Avri and I were talking, and we were both inspired to review and update our ALAC SOIs. Just a friendly reminder to those of us who participate in the GNSO, that the ALAC SOI is separate and distinct from your GNSO SOI. While I regularly update my GNSO SOI, I was surprised to find my ALAC SOI blank, as I genuinely recall completing it when I joined NARALO. However, in the interest of openness and transparency, I have now updated and published (that may have been the previous snafu) my ALAC SOI, see https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99734312/Mi… While I still believe the revision to the SOI process is inherently gameable, it is an improvement, and we should all embrace it and put it into practice. During last week’s Contracting Party Summit in Manchester, on the panel I moderated, I made a point of listing each panelist’s SOI; see screenshot below. [Screenshot 2026-05-06 at 2.02.49 PM.png] During the last several CPWG calls, I was unable to find SOIs for several participants. I think it would be good for ALAC leadership not only to ask for SOI updates at the beginning of calls, but also to remind ALAC community members to regularly update their SOIs. I think ALAC should set the bar high and lead by example within the ICANN community. On this issue of SOI compliance, please see the email communication that I sent to ICANN’ Board Chair and General Counsel in March regarding ICANN increasing openness and transparency in connection with the army of contractors, consultants, and lobbyists it employs. Sadly, I have not heard back from any recipient, although, to be fair, things have been a little hectic with the launch of the new gTLD window. I would really like to hear the view from ALAC about whether ICANN should have an obligation to publicly disclose their growing army of contractors, consultants and lobbyists in the letter and spirit of the SOI modifications? Two phrases keep reverberating in my mind: 1) Practice what you preach and 2) What is good for the goose is good for the gander. Just because these contractors, consultants, and lobbyists may not be actively participating in a policy work group does not mean that they are not impacting ICANN policy in the hallways of ICANN meetings or in other fora. Best regards, Michael P.S. Given the policy and governance implications of this email, I have decided to cross-post to CPWG and OFB. From: Michael Palage Date: Thursday, March 26, 2026 at 3:36 PM To: John Jeffrey ; Fiona Alexander; Tripti Sinha Subject: ICANN Contractors and SOI Requirements Hello John, Tripti and Fiona, I am doing research in connection with an upcoming article on ICANN’s updated Statement of Interest policy. And I had some questions I was hoping that you all might be able to answer. I believe the current SOI policy applies to ALL participants in the ICANN community, including ICANN contractors. Upon information and belief, I believe ICANN has/had a contractual relationship with Salt Point Strategies. The current policy provides a non-exhaustive means for community members to make a disclosure. However, I don’t see a mechanism or repository for ICANN contractors and other non-GNSO/non-ccTLD/non-ALAC community members to declare their Statements of Interest. During ICANN85, Fiona participated in a panel session. In the Zoom chat I recall making a statement about not seeing an SOIs from any of the panel participants other than Bruce Tonkin. I do not believe anyone, including ICANN staff, responded to my inquiry. Question/Request to Tripti - If the Board is serious about enhancing SOI transparency within the ICANN community, no person should be listed as a speaker/panelist at an ICANN event unless they have posted a corresponding SOI, absent extraordinary circumstances e.g. last-minute fill-in for another speaker. Do you think this is something that the ICANN Board could direct staff to implement? Question to John - Could you work with ICANN Org to provide a fail-over SOI repository for those community members that do not neatly fall within the GNSO, ccNSO, or ALAC? If you agree with this recommendation, could you give a potential ETA on when this might be available and where it would be located? Friendly suggestion, I would like to recommend SOI.ICANN.ORG as a default landing page for all SOs, AC, and other community members. If you disagree with this recommendation, I think it would be helpful to provide a public response to the ICANN Board explaining why staff chose not to implement it. Question to Fiona - Fiona, I just wanted to make sure I didn't miss where you previously posted an ICANN SOI. If you have posted one, I would greatly appreciate it if you could point me to it. I also wanted to confirm the previous/existing relationship between Salt Point Strategies and ICANN. Thank you for your attention to this matter. Best regards, Michael

5 6

Meeting invitation: At-Large Operations, Finance and Budget Working Group (OFB-WG) Call on Thursday, 07 May 2026 at 18:00 UTC
by ICANN At-Large Staff May 7, 2026

May 7, 2026

Dear All, The next At-Large Operations, Finance and Budget Working Group (OFB-WG) Call is scheduled for Thursday, 07 May 2026 at 18:00 UTC for 90 mins. For other time zones: <https://tinyurl.com/2p8e9d4> HERE<https://tinyurl.com/y9wp3u7u> The agenda (to be updated) and call details can be found at: https://icann-community.atlassian.net/wiki/x/PoBQQQ Zoom Room: https://icann.zoom.us/j/92139943237?pwd=RR7XGoRSXgUGFm2K4QKyAFEp54AzQb.1 / Password: OFBC#12345 Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN Wiki Workspace: https://community.icann.org/x/koTsBw Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community www.icann.org<http://www.icann.org/>

2 3

Meeting on 7th - Apologies
by Vanda Scartezini May 5, 2026

May 5, 2026

Dear friends from OFB WG, Every first Thursday, from each month, I have Board Meeting, F2F at the organization office, where I am International Director, always from 2PM till 6 PM. For my time zone, OFB WG on this Thursday 7th, will be at 3 PM, so I will not be able to attend. My apologies, and successful meeting to all. Kisses Vanda Scartezini ABES ( a Business Constituency Member) Diretora de Internacionalização + 55 11 98181-1464 www.abessoftware.org.br<http://www.abessoftware.org.br>

1 0

Fwd: [SubPro-IRT] New gTLD Program: 2026 Round now accepting applications
by Justine Chew May 1, 2026

May 1, 2026

*My apologies for the receipt of duplicates or triplicates due to cross posting* For your attention -- 2026 Next Round application submission window is now open and *will close on 12 August 2026*. Kind regards, Justine ---------- Forwarded message --------- From: Jared Erwin via SubPro-IRT <subpro-irt(a)icann.org> Date: Fri, 1 May 2026 at 01:10 Subject: [SubPro-IRT] New gTLD Program: 2026 Round now accepting applications To: subpro-irt(a)icann.org <subpro-irt(a)icann.org> Dear IRT Members, The New gTLD Program: 2026 Round application submission period is now open. Please see the announcement here: https://www.icann.org/en/announcements/details/icann-opens-application-wind…. Congrats to all on this tremendous achievement! Best Jared -- Jared Erwin Senior Director, New gTLD Program Global Domains & Strategy (GDS) Internet Corporation for Assigned Names and Numbers (ICANN) jared.erwin(a)icann.org _______________________________________________ SubPro-IRT mailing list -- subpro-irt(a)icann.org To unsubscribe send an email to subpro-irt-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