Re: [hrpc] Censorship

Andrew Sullivan <ajs@anvilwalrusden.com> Sun, 13 March 2022 21:41 UTC

Return-Path: <ajs@anvilwalrusden.com>
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 D11953A1756 for <hrpc@ietfa.amsl.com>; Sun, 13 Mar 2022 14:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 (1024-bit key) header.d=yitter.info header.b=MgtJdj5S; dkim=pass (1024-bit key) header.d=yitter.info header.b=ioOu1NI+
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 3b2h_aDn4-Dx for <hrpc@ietfa.amsl.com>; Sun, 13 Mar 2022 14:41:11 -0700 (PDT)
Received: from mx5.yitter.info (mx5.yitter.info [159.203.31.152]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8804F3A1758 for <hrpc@irtf.org>; Sun, 13 Mar 2022 14:41:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id A95ADBD5C5 for <hrpc@irtf.org>; Sun, 13 Mar 2022 21:40:37 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1647207637; bh=FOAEdxWAjgk1gj5lpdzzWKEgnoDpHLpUPSLLGPppmcs=; h=Date:From:To:Subject:References:In-Reply-To:From; b=MgtJdj5S37bjGuT9KzYeuawPgdw445A3orcfN7a0A5PNP7NTDmxWA398N8qSE7epb Yv+4nBTcXDMO/TiqyGw5J3U1oSbajLE/tIBy0/xWBDv1yYKVp17BpPGSj4oHDQAd4b W9Y/nFyf1K9dZ35kQM0nLUp0ag54ZYUr3Yw2goAE=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx5.yitter.info ([127.0.0.1]) by localhost (mx5.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yVuCoDiFN4Q9 for <hrpc@irtf.org>; Sun, 13 Mar 2022 21:40:35 +0000 (UTC)
Date: Sun, 13 Mar 2022 17:40:33 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1647207635; bh=FOAEdxWAjgk1gj5lpdzzWKEgnoDpHLpUPSLLGPppmcs=; h=Date:From:To:Subject:References:In-Reply-To:From; b=ioOu1NI+lNj22bZ6JNgRunpjA8N15bMcjO0DfoGKhP1cpFjT3761QWcRCloxQUC7H ryT3y0d75vEa+keVOdPMk16g5ahRvuWZQfyYfHBsNa71Ee6Ssezlba4t6PXeoB5SzL DleJFInz3f1cv9N+9NOvcn6gyhS17c7PEFPbC8Mk=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: hrpc@irtf.org
Message-ID: <20220313214033.rysyxmydzda2v3kw@crankycanuck.ca>
Mail-Followup-To: hrpc@irtf.org
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <B41A8BB3-BBF3-4D53-A14D-E1CE4BC782DF@pch.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/peykp_iAkpN7F37Xyk22btTWL_E>
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: Sun, 13 Mar 2022 21:41:18 -0000

Dear colleagues,

ObDisclaimer: I work at the Internet Society, but I am not speaking for them in this posting and do not participate in the work of this RG in my professional capacity either.

On Sat, Mar 12, 2022 at 10:18:22AM +0100, Bill Woodcock wrote:

>Exactly.  There is no authority.  Merely a lot of mechanisms that do different things.  This is a proposed mechanism, which may achieve an end for some people.  Anyone who doesn’t need it or doesn’t like it is free to ignore it.

That is not what "sanction" means, or at least not what it means in this context.

The "sanctions statement" as written starts out comparing the case of possible sanctions to be imposed by "the global Internet governance community" to the ones imposed by governments.  Governments impose economic sanctions through the force of law, and anyone subject to that government's jurisdiction and who does not comply with the sanctions faces penalties that usually include things like serious fines and jail time.

If parties A, B, and C curtail their economic activity with party T, and invite any other party to come along, but do not use any coercive effort to bring those others along, it's not "sanction".  It's a boycott.  If the proposal were for a new list to be published that enabled the rest of the world to understand the official Western Internet goodguys' opinion of who on the Internet is an official Internet badguy who ought therefore to be boycotted, I might still think it gross but I might not think it a mortal threat to the Internet.  This sanctions statement, however, does threaten the Internet because of the very use of the word "sanction". That will automatically be read by governments as "Here's the list you should encode in your laws of people not to talk to."

In any case, in the hope of talking here about something related to this RG's charter, I went and had a look at the latest at https://datatracker.ietf.org/doc/draft-irtf-hrpc-association/, in light of the sanctions statement.

It seemed to me that, if there is some kind of freedom of association on the Internet, then protocols that tend to create advantages for connectivity would be preferable to those that do not. Now, the sanctions statement proposes a kind of "shunning shutdown" in which an official list of networks to be shunned on political grounds is to be published and, presumably, acted upon by other networks under some kind of threat. One supposes that networks who did not operate in the desired way would also find themselves on the political sanction list, because there isn't really another threat possible.  Such effects would erode connectivity.

It follows from this that one should prefer protocols that are resistant to this sort of shunning shutdown, because they are better enablers of people's freedom of assiciation than protocols that enable shunning shutdown.

I was surprised that this fairly straightforward entailment did not ring out clearly to me from the text of draft-irtf-hrpc-association.  (To be honest, I find the dcument extremely wooly and hard to follow, so nothing really rings out clearly from it.)  There was, however, a tantalizing observation in the conclusion that

		non-interoperable
    platforms in chat and social media networks have a significant impact
    on the distributed and open nature of the Internet.

A protocol by which some networks are targetted for shunning shutdown will, by its very nature, lead to an increase in non-interoperation.  I therefore conclude that the sanctions statement proposes that a new protocol should be designed that would be harmful to human rights on the Internet.

By the way, I note that I appear in the Acknowledgements of draft-irtf-hrpc-association.  If it's all the same to the editors, I don't think I had anything to do with the document and I'd just as soon not be associated with it.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com