Re: [hrpc] Censorship

Bill Woodcock <woody@pch.net> Fri, 11 March 2022 11:05 UTC

Return-Path: <woody@pch.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 5F3D03A10CF for <hrpc@ietfa.amsl.com>; Fri, 11 Mar 2022 03:05:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.11
X-Spam-Level:
X-Spam-Status: No, score=-7.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=pch.net
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 BZVUup-B1oef for <hrpc@ietfa.amsl.com>; Fri, 11 Mar 2022 03:05:33 -0800 (PST)
Received: from mail.pch.net (keriomail.pch.net [206.220.231.84]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9024D3A107C for <hrpc@irtf.org>; Fri, 11 Mar 2022 03:05:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=pch.net; s=mail; h=from:subject:date:message-id:to:cc:mime-version:content-type:in-reply-to: references; bh=VDAtdmAFfr7mN3ehIgicSaKWPh9XWjgUh55BRRydSQ8=; b=ZHVl3kyk/01Mp4rCkyWPcp3+VBK0V21Tk/62h46s31dVeER04rl1oaFkmiG+sWQL2j4ev+OCU1/P8 /22yyX6YlfoXhBUls47iXVPRw2SLNefVa0wetEAgNW3IAZIcth0fBD42442n9QiTWBrqLCHE382NBw LaGkdbEA9o8XQWCnmyf4dZcldehreOBj1oRhxqkpdwiLN44lu/oeYjt+fPGU+NOMC/1Zm78fdeL2gu jq230jb/yh58hUxamGCdrKVYwnSdvuNty83PZPLNpMJVmV2GaYqiBzWMAFn81mjt/p/1PujrOS1MoV w6csVvg97VsMl5rUBnq+IAzrqByMJhw==
X-Footer: cGNoLm5ldA==
Received: from smtpclient.apple ([69.166.14.6]) by mail.pch.net (Kerio Connect 9.2.7 patch 3) with ESMTPS (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256 bits)); Fri, 11 Mar 2022 03:05:31 -0800
Content-Type: multipart/signed; boundary="Apple-Mail=_D997C381-430F-48AB-8E9A-6730599AA0AB"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Bill Woodcock <woody@pch.net>
X-Priority: 3
In-Reply-To: <254407218.184957.1646992776229@appsuite-gw2.open-xchange.com>
Date: Fri, 11 Mar 2022 12:05:25 +0100
Cc: "hrpc@irtf.org" <hrpc@irtf.org>
Message-Id: <EA324F84-FAE9-4F76-A25A-0044BD5BE34C@pch.net>
References: <669686052.184329.1646989079672@appsuite-gw2.open-xchange.com> <AFDE14D7-A5A1-4009-9E8D-C77D4984EDDA@pch.net> <254407218.184957.1646992776229@appsuite-gw2.open-xchange.com>
To: Vittorio Bertola <vittorio.bertola@open-xchange.com>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/j4wH2swo6EncWp3SLxXetAoPHDU>
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 11:05:39 -0000


> On Mar 11, 2022, at 10:59 AM, Vittorio Bertola <vittorio.bertola@open-xchange.com> wrote:
> 
> 
> 
>> Il 11/03/2022 10:38 Bill Woodcock <woody@pch.net> ha scritto:
>> 
>> 
>>> On Mar 11, 2022, at 9:57 AM, Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org> wrote:
>>> I think that this call for a global, multistakeholder process to block access to Russian military and news websites
>> 
>> I encourage you to all read it for yourselves, because, as one of the authors and one of the signatories, that’s not what we said.
> 
> Indeed people should read it, that's why it was linked.

Thank you, I appreciate that, and I appreciate that you’re arguing in good faith, as I’ve always observed you to do before.  I respect your opinion, and I want to make sure that both you understand what the goals of the letter were, and that I understand your objections or considerations.

> The document itself calls for a public discussion, though it does not specify where.  I am happy to join the public discussion wherever the signatories want it to happen.

I don’t believe any of us had any thought that we had any authority to dub anywhere the “correct” place.  But I think that, more specifically, we all share the view that Internet multistakeholder governance is bottom-up and non-exclusionary.  So there is no “wrong place” except perhaps forums that, as you point out, may deem it off-topic:

> The points you raise could be off topic for this group, but if the chairs think differently, I am happy to continue the discussion in detail here.

I as well, and I believe there are other signatories and authors on this list.  Also happy to try to constrain discussion here to aspects which lie at the intersection of the thoughts we expressed and the topic of this list.

> If all Internet protocols and services were designed in the way we advise in draft-guidelines, then the sanctions proposed by the document would be technically impossible

Can you explain that in more detail?  As someone who works in this field, and who has read https://datatracker.ietf.org/doc/draft-irtf-hrpc-guidelines/ it is not clear to me what portion of the proposed mechanism you believe would be made impossible.  Or for that matter, touched at all.  If you can direct me to something specific, I can give a more considered response.

> Perhaps we should recognize in draft-guidelines that, after all, censorship is sometimes desirable and there should be technical and policy hooks to implement it; so protocol designers should rather think at how to address this need while preventing such practices from becoming overbroad. I would be much in favour of this, as I do think that censorship is sometimes desirable, including in this case; but this did not seem to be the consensus of this group (and of PEARG) in the past.

I feel that others in this group have far deeper intellectual backgrounds upon which to draw on this topic.  Myself, I feel that it’s self-evident that there’s a moral imperative to choose the lesser of two possible evils, when one is compelled to make a choice on behalf of another.  That is, when one is making a choice with consequences only for one’s self, one is free to suffer a greater evil in order to support a rhetorical point.  But when the sacrifice is someone else’s, doing so is anathema.

If viewed in this light, _sufficiently constrained_ sanctions are the proper choice.  They may involve some minor sacrifice on the parts of some actors (if, for example, they are selling services to the Russian military, as Cloudflare recently reiterated their commitment to continuing to do), but relative to kinetic warfare and atrocities, it is an essentially deescalatory response, which is good.  It shows moral conviction and provides some allyship with victims, while simultaneously removing subsidies (in the form of societally-borne common costs) from the aggressor.  This is shunning, or outlawing, as Icelandic law established more than a thousand years ago. If someone flagrantly transgresses societal norms, they cannot expect to benefit from societally-provided goods, at society’s common expense.

Removing Russian military routes from our routing tables reduces a collective cost to society, and transfers those costs back to the Russian military and those who are selling them services, to carry individually.

You raised, initially, the question of whether this constituted “censorship.”  I would distinguish between individual efforts which have the effect of being in the direction of censorship, versus censorship as a measured effect.  The Internet famously “routes around damage” and “censorship is indistinguishable from damage.”  Thus if a network chooses to no longer carry Russian military routes, the Russian military has not been disconnected from the Internet… they simply have to carry a greater share of the cost of their connection individually, and leave less of the cost to be shared communally.  Every single one of some thirty thousand networks would have to withdraw Russian military routes before they became truly unreachable.  So in that sense, I would actually disagree that this is censorship, in that it’s not truly effective as censorship.  It is exactly effective as a sanction, however, since the sanction is intended to transfer the costs of aggressors’ actions back into their own wallets.

                                -Bill