Re: [hrpc] Censorship

Niels ten Oever <mail@nielstenoever.net> Fri, 11 March 2022 20:32 UTC

Return-Path: <mail@nielstenoever.net>
X-Original-To: hrpc@ietfa.amsl.com
Delivered-To: hrpc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6916C3A085E for <hrpc@ietfa.amsl.com>; Fri, 11 Mar 2022 12:32:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O49zja6Vb0X0 for <hrpc@ietfa.amsl.com>; Fri, 11 Mar 2022 12:32:03 -0800 (PST)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D92D93A0884 for <hrpc@irtf.org>; Fri, 11 Mar 2022 12:32:01 -0800 (PST)
Message-ID: <67721c40-268b-daac-daaf-6c8c2161456f@nielstenoever.net>
Date: Fri, 11 Mar 2022 21:31:55 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Content-Language: en-US
To: hrpc@irtf.org
References: <1779273019.188450.1647022617139@appsuite-gw2.open-xchange.com> <AF3A93BB-04A7-4E5F-B88A-CD441369874E@nohats.ca>
From: Niels ten Oever <mail@nielstenoever.net>
In-Reply-To: <AF3A93BB-04A7-4E5F-B88A-CD441369874E@nohats.ca>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Authenticated-As-Hash: f1842a279235a42f6aa2a2a81130733515c5a4ec
X-Virus-Scanned: by clamav at smarthost1.greenhost.nl
X-Scan-Signature: 2c269fdec788119c0964d98755c55204
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/hfcd0h2fNw1LEhh-McFZOFt_D48>
Subject: Re: [hrpc] Censorship
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: hrpc discussion list <hrpc.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hrpc>, <mailto:hrpc-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hrpc/>
List-Post: <mailto:hrpc@irtf.org>
List-Help: <mailto:hrpc-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hrpc>, <mailto:hrpc-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2022 20:32:09 -0000

On 11-03-2022 19:41, Paul Wouters wrote:
> The internet is infrastructure. It must always be there and when broken must be fixed. Punishing citizens for their government actions by crippling infrastructure is always wrong.

 From the statement:

● Disconnecting the population of a country from the Internet is a disproportionate and inappropriate sanction,
since it hampers their access to the very information that might lead them to withdraw support for acts of war
and leaves them with access to only the information their own government chooses to furnish.

and

● Sanctions should be focused and precise. They should minimize the chance of unintended consequences or
collateral damage. Disproportionate or over-broad sanctions risk fundamentally alienating populations.

● Military and propaganda agencies and their information infrastructure are potential targets of sanctions.

Best,

Niels

> 
> Paul
> 
> Sent using a virtual keyboard on a phone
> 
>> On Mar 11, 2022, at 13:17, Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org> wrote:
>>
>> 
>>
>>> Il 11/03/2022 17:38 Bill Woodcock <woody@pch.net> ha scritto:
>>>
>>> So, just block everybody and let god sort them out?
>>>
>>> Because that’s the status quo, and the problem we’re trying to fix.
>>
>> As that seems to be your strongest motivation, I am curious to understand why. I mean, I agree that your proposal would be far better than Ukraine's, but as far as I know, almost no one at ICANN or at RIPE has argued in favour of removing TLDs from the root, invalidating certificates or deleting IP space. Both institutions have clearly said that, while sympathizing with Ukraine's situation, they will not agree to the request. So how is that "the status quo"?
>>
>> Personally, my motivation for supporting your proposal would actually be the opposite - enabling limited but focused sanctions as an alternative to doing nothing.
>>
>>
>> -- vb.
>>
>> _______________________________________________
>> hrpc mailing list
>> hrpc@irtf.org
>> https://www.irtf.org/mailman/listinfo/hrpc
> 
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc

-- 
Niels ten Oever, PhD
Postdoctoral Researcher - Media Studies Department - University of Amsterdam
Affiliated Faculty - Digital Democracy Institute - Simon Fraser University
Non-Resident Fellow 2022-2023 - Center for Democracy & Technology
Associated Scholar - Centro de Tecnologia e Sociedade - Fundação Getúlio Vargas
Research Fellow - Centre for Internet and Human Rights - European University Viadrina

W: https://nielstenoever.net
E: mail@nielstenoever.net
T: @nielstenoever
P/S/WA: +31629051853
PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3

Read my latest article on Internet infrastructure governance in Globalizations here: https://www.tandfonline.com/doi/full/10.1080/14747731.2021.1953221