Re: [hrpc] Censorship

Mallory Knodel <mknodel@cdt.org> Fri, 11 March 2022 20:29 UTC

Return-Path: <mknodel@cdt.org>
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 9059E3A0884 for <hrpc@ietfa.amsl.com>; Fri, 11 Mar 2022 12:29:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, 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=cdt.org
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 Bvq8XVm-k8CF for <hrpc@ietfa.amsl.com>; Fri, 11 Mar 2022 12:29:14 -0800 (PST)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AECED3A085E for <hrpc@irtf.org>; Fri, 11 Mar 2022 12:29:14 -0800 (PST)
Received: by mail-qt1-x82f.google.com with SMTP id n11so2639756qtk.4 for <hrpc@irtf.org>; Fri, 11 Mar 2022 12:29:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to; bh=ZoPk+x/mZCwnh6gP8qj08w1MZ8npU354z0alKaFMOwA=; b=faY5dtXaZwvDQjWlP4KWNv7NA9iHOyCGZoQ3OnRsM+FP/IXieagIifvAOWdDxnZyVV h5trOHVkr+hArDZhuFhEdXT2UVGDbZ9ueaWcRxTVS8Xkjdt02HuVJs5evFUJzThpCW3Y 5LSjehayzMLqaGZ/2gqAtAdbgHiQGiWtU0cxM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to; bh=ZoPk+x/mZCwnh6gP8qj08w1MZ8npU354z0alKaFMOwA=; b=hRt3CKcyPf/sDcAhgZij5su1sy6VQOum5xGwRMn4OoH9WY+kHvFdoU9bz91enjQZNG 3df6SyVJqcA9J27mMeRZ3rogJ4dTqTbCIe16vefSDwVPB6tnT++00TefO3Bn31mJa7Fo 74usqqb2tsk9uwSY3j4JtGdP9PquMAxPxhlhC1l4yvFrK07ZgfBCbvfDycpZU9JNdC5a MOWk6oc44nStDzBWW6bErIRBdLX/+SHZGRwQooGrmIxMZoJ4oc8ANS/w/dbtTkkg3e/y 3Qm1OjilRqdnzP1tLmeEi0UEFvRB7KLBv7L9i3DXRYYhujcLPKNV6vXSx65xcPb4rfKw PznA==
X-Gm-Message-State: AOAM531h6+d3IyJ3ryriJ+CMkDSwlVbrQdUB3Uhfd7VivWq0E3SAJxVg hyt3XWNVux2R8tqsQ9SA2Z7yd8Alxx8MfT7/
X-Google-Smtp-Source: ABdhPJxkO9+6da2MjETEeEpeFqq3X8G1to0faavZjSRsjNH2phlECNhg1NeE4VuOzi8YXp6Cq1m9eQ==
X-Received: by 2002:ac8:5e11:0:b0:2e1:c7cf:cfec with SMTP id h17-20020ac85e11000000b002e1c7cfcfecmr172528qtx.282.1647030553363; Fri, 11 Mar 2022 12:29:13 -0800 (PST)
Received: from ?IPV6:2601:14d:8300:c190:58b5:158d:1ef0:f25b? ([2601:14d:8300:c190:58b5:158d:1ef0:f25b]) by smtp.gmail.com with ESMTPSA id g14-20020ae9e10e000000b0067b520a01afsm4324118qkm.108.2022.03.11.12.29.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 11 Mar 2022 12:29:13 -0800 (PST)
Content-Type: multipart/alternative; boundary="------------UqLrY7aMtrfQbbYRWXk8800B"
Message-ID: <a1881e17-16df-5e1b-1aa8-f6af14e747e6@cdt.org>
Date: Fri, 11 Mar 2022 15:29:09 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:98.0) Gecko/20100101 Thunderbird/98.0
Content-Language: en-US
To: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>, "hrpc@irtf.org" <hrpc@irtf.org>
References: <669686052.184329.1646989079672@appsuite-gw2.open-xchange.com>
From: Mallory Knodel <mknodel@cdt.org>
In-Reply-To: <669686052.184329.1646989079672@appsuite-gw2.open-xchange.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/jpDbe0WQ9d2KhFnS6RJA0uDOxbc>
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:29:20 -0000

Hi all,

I don't mean to hijack a discussion of one document with another, but, 
as everyone has probably noticed there is no shortage of these things 
being published every day. Rather I'm sharing this other statement 
because it's relevant to the discussion and takes a different approach, 
more like what Paul Wouters said earlier.

Dozens of human rights groups call for more clarity on sanctions, 
including authorisatinos for comms/internet (as was with Syria, Cuba, 
Iran): 
https://www.accessnow.org/cms/assets/uploads/2022/03/Civil-society-letter-to-Biden-Admin-re-Russia-sanctions-and-internet-access_10-March-2022-1.pdf

If you'd like to read more of a narrative on tech sanctions, there's 
this great piece by Wikimedia Foundation VP: 
https://techpolicy.press/the-invasion-of-ukraine-is-horrific-cutting-the-russian-people-off-from-the-internet-could-make-it-worse

As for my view, I'm with Stephen in that I don't think it's a 
particularly effective approach that the PCH letter takes and yet the 
political risks are tremendous. If we are to build the capacity in 
internet governance spaces like the IRTF/IETF-- and I would argue that 
is a far better goal than a new IG body-- it had better be on rock solid 
ground in terms of understanding efficacy and tradeoffs.

I think the statements that have been issued by internet governance 
bodies have so far come to the exact right conclusion. What would have 
made them better is more political analysis of Russia as a bad faith 
actor in these spaces, enumeration of bad behaviour that is unacceptable 
and already considered actionable offenses (like DDoS, spam, a rogue 
root operator, etc), and an offer of clear guidance to implementers and 
other tech companies or organisations who would look to those bodies for 
cues on what they should do (or not do) in these troubled times.

-Mallory

On 3/11/22 3:57 AM, Vittorio Bertola wrote:
> Hello,
>
> I think that this call for a global, multistakeholder process to block 
> access to Russian military and news websites would be of interest for 
> discussion here.
>
> https://www.pch.net/resources/Papers/Multistakeholder-Imposition-of-Internet-Sanctions.pdf 
>
>
> I don't disagree with the concept, I would actually implement such a 
> blocklist. I am worried that such a structured approach, and some 
> names in the list of signatories, could weaponize the global Internet 
> governance institutions and lead to the final fragmentation of the 
> Internet, but this is not in topic here.
>
> I am however puzzled by how this call could be compatible with the 
> pretty maximalistic approach to Internet censorship that this group 
> (or PEARG, in https://tools.ietf.org/html/draft-irtf-pearg-censorship) 
> has been taking. Possibly, if we applied draft-guidelines to this 
> proposal it would not pass the test.
>
> I would like to understand the line of reasoning under which an ISP 
> blocking access to child sexual abuse material or to phishing websites 
> is a censor, but if a soon-to-be-formed Internet institution decides 
> to block access to Russia Today globally as part of a war, then it's 
> all good.
>
> Was this discussed by the proponents? I'd guess so. Can anyone explain?
>
> -- 
>
> Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
> vittorio.bertola@open-xchange.com  
> Office @ Via Treviso 12, 10144 Torino, Italy
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc

-- 
Mallory Knodel
CTO, Center for Democracy and Technology
gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780