[At-Large] Ukraine, .RU, and internet governance

Sun Mar 13 21:19:38 UTC 2022

Indeed Holly .
 For me Russian users of internet as well as Ukraineans users deserve to be connected- not all Russians are in favor of this war.
As many of us saw,in each of our own country, lots of absurd and cruel things done to other countries some time by our own governments and did not agree, but had no power to make anything but use the internet to complain, if the government in question was not the one to persecute and kill those who dare to write against it, but even so,  many of us used the internet to do so!!
Both sides have the right to use this weapon in favor of peace.
We are also seeing lots of hackers ( we have condemn they for their cybercrimes …) doing a good service using their capacity helping refugees and others in this war.. so,  there are always several ways to use your knowledge for the benefit of world peace, without damage one side..

Vanda Scartezini
Polo Consultores Associados
Av. Paulista 1159, cj 1004
Mobile: + 55 11 98181.1464
Sorry for any typos.

From: At-Large <at-large-bounces at atlarge-lists.icann.org> on behalf of 'At-Large Worldwide' <at-large at atlarge-lists.icann.org>
Reply-To: Holly Raiche <h.raiche at internode.on.net>
Date: Sunday, March 13, 2022 at 02:08
To: 'At-Large Worldwide' <at-large at atlarge-lists.icann.org>
Subject: Re: [At-Large] Ukraine, .RU, and internet governance

Folks

Please read the statement from the ISOC CEO - a very well argued statement about why cutting off .ru is not the answer, regardless of how much we all deplored the actions Russia has taken

Holly

https://www.internetsociety.org/blog/2022/03/why-the-world-must-resist-calls-to-undermine-the-internet/

On Mar 12, 2022, at 7:59 PM, Roberto Gaetano via At-Large <at-large at atlarge-lists.icann.org> wrote:

Unfortunately, it is not an international law issue, otherwise it would be solved without any responsibility by ICANN - just follow the order of the judge.

The problem lies elsewhere, and is whether ICANN is or not an independent authority that can be trusted for following basic principles and apply them evenly in all cases.

If ICANN decides to remove .ru from the root, based on a request by Ukraine (who, by the way, is no longer insisting in asking this, maybe because they have understood the unintended consequences) I don’t see how it could resist the request of removing the ccTLDs of what the US consider “rogue” countries, like Iran, Cuba, and others.

And this besides all what has been said at length in this and other lists, like that it will not make .ru disappear, just invite operators to have their own copy of the root.

This said, there are other actions that ICANN can take, but after having decided whether it will keep its reputation of being a reliable steward for the Internet infrastructure in the global interest or indulge in actions that, while not achieving any practical result, will be emotionally satisfying.

Cheers,
Roberto

On 12.03.2022, at 04:55, SCHWEIGHOFER Erich Prof. Dr. Dr.. via At-Large <at-large at atlarge-lists.icann.org<mailto:at-large at atlarge-lists.icann.org>> wrote:

It is an international law issue and the main text for conflicts and sovereignty is the UN Charta and its practice.
In law, using the right text is decisive.
Erich Schweighofer

Am 12.03.2022 04:36 schrieb Antony Van Couvering via At-Large <at-large at atlarge-lists.icann.org<mailto:at-large at atlarge-lists.icann.org>>:
The mealy-mouthed opposition to Ukraine’s request to block .RU has exercised me so much that I called up Keith Teare to complain.  Keith is a one-time candidate for ICANN CEO, a former board member of Minds + Machines, founder of Real Names and other companies, and a very smart guy with a good grasp of history and the internet.

Keith doesn’t really agree with my position, so he suggested that we record a conversation and talk it out.  To me, it turned out well (pardon my video quality.

For those who’d like to hear a thorough discussion of the issue, here it is:

https://www.youtube.com/watch?v=uXZd6rtDHsA

Summary — all the reasons put forward as to why ICANN can’t do anything — we go through them all — are bullshit.

_______________________________________________
At-Large mailing list
At-Large at atlarge-lists.icann.org<mailto:At-Large at atlarge-lists.icann.org>
https://atlarge-lists.icann.org/mailman/listinfo/at-large

At-Large Official Site: http://atlarge.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.

_______________________________________________
At-Large mailing list
At-Large at atlarge-lists.icann.org
https://atlarge-lists.icann.org/mailman/listinfo/at-large

At-Large Official Site: http://atlarge.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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://atlarge-lists.icann.org/pipermail/at-large/attachments/20220313/f6ec30cb/attachment-0001.html>