Re: [hrpc] ***SPAM**** Re: Censorship

Bill Woodcock <woody@pch.net> Tue, 15 March 2022 15:51 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 A209D3A15AD for <hrpc@ietfa.amsl.com>; Tue, 15 Mar 2022 08:51:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level:
X-Spam-Status: No, score=-2.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, 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 kvXPz0O7nkDk for <hrpc@ietfa.amsl.com>; Tue, 15 Mar 2022 08:51:26 -0700 (PDT)
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 D587E3A15A6 for <hrpc@irtf.org>; Tue, 15 Mar 2022 08:51:26 -0700 (PDT)
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=/j0vXI8FwLSmwdr5a+DabWMGLxs4TMMUPBngpKpA2Ks=; b=DYvhN4oMM9257ElYgdd9lJt27bA2SlTI2isHSQSFQi9cvw59APgNDlg0fu6zdco4sLrg2MKR7Z9/y ylQAfQTjgTm1NaFLXpMICX2Wkez6ztWsUm+g3bja6pNuU9uQzUsuSYYgiKsv+MSFac018uqIS/Zp1G lt3wZQoTqGDLEshdGHSyChOhgwOIiB1oLQZHv6froq8vnCrzzJOFZtrn2z0zQtDHEQwvEzJq+ugpsB ztDoNEgnDy13LqvdgDIH11p5qy95CrKZNErCgoQVYQ8aSZmfM8UwJMkmT4b1zM2cDM73rtG6aCWFqJ /Bk8z7x+1pT4TJJlwQ3xrMNTxsZBRYA==
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)); Tue, 15 Mar 2022 08:51:23 -0700
Content-Type: multipart/signed; boundary="Apple-Mail=_34E27D60-756D-4945-A3C1-A487D3F03986"; 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>
In-Reply-To: <5293c470-c994-5fbb-67f5-8e996f8288f9@cdt.org>
Date: Tue, 15 Mar 2022 16:50:29 +0100
Cc: Hrpc <hrpc@irtf.org>
Message-Id: <B763FD61-A030-453E-8B19-BED0A2884778@pch.net>
References: <1779273019.188450.1647022617139@appsuite-gw2.open-xchange.com> <AF3A93BB-04A7-4E5F-B88A-CD441369874E@nohats.ca> <1bf024c5-9044-f806-9ce9-7a3377045f48@lear.ch> <25132.19040.388723.228805@gargle.gargle.HOWL> <B41A8BB3-BBF3-4D53-A14D-E1CE4BC782DF@pch.net> <20220313214033.rysyxmydzda2v3kw@crankycanuck.ca> <DgjJ0pvzPp-nRdnSldzL0wBJfaVS74YhB-k_2rln_6ucqpbfaVYynous2WNiSrd2uZ26kaBCYfL8WauDvRvD6WYVePDWrm8zpxSfgd6BRzM=@interpeer.io> <20220314151111.eird5poe2scjoywn@crankycanuck.ca> <fa9562f7-415e-a335-be05-2b137c0a3a21@nielstenoever.net> <20220314192902.fjag7xp6jkprdiyg@crankycanuck.ca> <nTwqrqnZd6czoxYmGRXMNcr-f0rxCBjA88flQjqwNM22eFfnuvGiE-dm8_LkgyhYNVb6MA4DtATpins_9JBV_9jlV7Zeb-CYUchFkeSlot8=@interpeer.io> <af2b4edb-8c23-fd0e-e2a1-b0def85ad34b@cs.tcd.ie> <5293c470-c994-5fbb-67f5-8e996f8288f9@cdt.org>
To: Mallory Knodel <mknodel@cdt.org>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/tdO70hQswGikR4Cg5Yu7w8nfF14>
Subject: Re: [hrpc] ***SPAM**** Re: 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: Tue, 15 Mar 2022 15:51:32 -0000


> On Mar 15, 2022, at 3:50 PM, Mallory Knodel <mknodel@cdt.org> wrote:
> I'll answer Bill's previous question to me about political risks. In the case of censoring, or boycotting through internet cutoff, the Russian military, you are:
> 
>  * Provoking Russia on national security and it will have ramifications at the UN on the cybercrime treaty and any future hope of a cybersecurity treaty,

You think it’s _substantially more_ prevocational to block their military than to block their whole country?

>  * Giving Russia an excuse to continue building its own internet, splintering further away,

First. they don’t need an excuse.  Second, can you present a rationale for why you believe military-only is more of an excuse than whole-country?  That seems radically counterintuitive to me.

>  * Undermining civil society's prior positioning firmly against all internet censorship even to advocate for carve outs in sanctions,

If party A and party B are in disagreement, and party C is somewhere in-between, how does party C’s position “undermine” party A’s position?  Are people not free to have disagreeing positions?

>  * Normalising blocking by intermediaries that haven't the in-house capacity to take a political position, when instead we should be helping build their capacity to resist unjust blocking,

How does blocking less normalize more than blocking more does?

>  * Moving out of alignment what is best for the internet and what is best for people,

How is blocking civilians “what is best for people?"

>  * Making more incoherent messaging and guidance about is "right" to do, not less.

?  Explain?

>  * Abstracting the nascent capacity to govern the internet with political considerations away from where those decisions should instead be made.

Where do you think they should be made?  Governments are very clear that they should be made in government.

If you don’t believe the governmentally-proposed solution is the right one, and you believe they should be made elsewhere, what’s your plan for doing that?

> You'll never get the civil society sector to come to consensus about it

Agreed.

> so you can't call it that (as you do in your letter).

Where do you see that?

> Gentle reminder to everyone in the discussion that we are meant here to identify research topics related to human rights and internet protocols.

I’m always happy to discuss in private email, I don’t have any burning desire to use public-mailing-list bandwidth.  I do want to make sure I fully understand all cautions, additional information, arguments against, etc.  So please do follow up with me if you feel like I’m not understanding what you’re saying (anyone, this isn’t specifically with respect to Mallory).

                                -Bill