To show support to Ukraine, should the ICANN block Russia from participating in the next round of the ICANN new gTLD program?

The question of whether ICANN should block Russia from the next round of the new gTLD program to show support for Ukraine touches upon ICANN's core mission, its neutrality, and the broader debate about the "Splinternet."

Here's a breakdown of the key considerations based on ICANN's principles and previous decisions:

Arguments Against Blocking Russia (ICANN's Position and Principles):

• Neutrality and Mission: ICANN's primary mission is technical—to ensure a single, stable, and globally interoperable Internet through the coordination of unique identifier systems (domain names and IP addresses). ICANN has historically maintained a stance of neutrality in geopolitical conflicts, arguing that its role does not extend to taking punitive actions, issuing sanctions, or restricting access to the Internet based on political disputes.
• Previous Precedent: Following Russia's invasion of Ukraine, ICANN rejected a request from Ukraine to revoke Russia's top-level domains (.ru, .рф, .su) and associated SSL certificates. ICANN's leadership cited the importance of its neutrality and the need to support the global Internet's security, stability, and resiliency.
• Risk of "Splinternet": Actions that fragment the global Internet along political boundaries—often termed the "Splinternet"—are seen as dangerous. Restricting participation based on nationality or political action could set a precedent that undermines the Internet's foundational principle of being a universal resource, potentially leading to widespread negative effects on global communication and human rights.
• Focus on Technical Function: ICANN's mandate is limited to the technical administration of identifiers. Using this technical function for political or punitive purposes is seen as overstepping its authority and potentially compromising the trust essential to the multistakeholder model of Internet governance.

Arguments for Blocking or Restricting Russia's Participation:

• Showing Support and Applying Pressure: Supporters of a block would argue that excluding Russia is a powerful, visible show of support for Ukraine and a form of economic/political pressure, aligning with sanctions imposed by many countries.
• Alignment with Sanctions: While ICANN itself is non-governmental and not a sanctions body, applicants for gTLDs may be required to abide by relevant economic sanctions, such as those overseen by the U.S. Office of Foreign Assets Control (OFAC). Russian government entities or sanctioned individuals/companies could face hurdles regardless of ICANN's intent.
• Ethical or Moral Considerations: Some argue that, in extraordinary circumstances like a large-scale invasion, technical bodies should not remain completely blind to the ethical implications of allowing sanctioned states to participate fully in global programs.

Conclusion:

Based on ICANN's stated mission, its adherence to a neutral, technical role, and its previous rejection of requests to "disconnect" Russian domains, it is highly unlikely that ICANN would unilaterally block Russia from participating in the next round of the new gTLD program.

Any restrictions on Russian applicants would most likely stem from an applicant's inability to meet the financial or legal requirements—specifically, clauses requiring adherence to international economic sanctions (e.g., U.S. sanctions) that may apply to the contracting process, rather than a political decision by ICANN to exclude the country as a show of support.