Re: [Pearg] Research Group Last Call for "A Survey of Worldwide Censorship Techniques"

Christopher Wood <caw@heapingbits.net> Fri, 29 May 2020 14:31 UTC

Return-Path: <caw@heapingbits.net>
X-Original-To: pearg@ietfa.amsl.com
Delivered-To: pearg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CAD53A091C for <pearg@ietfa.amsl.com>; Fri, 29 May 2020 07:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=heapingbits.net header.b=JxmPi6cr; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=q7Qc5/br
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 LCkXPjECrZr5 for <pearg@ietfa.amsl.com>; Fri, 29 May 2020 07:31:01 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBFE03A0912 for <pearg@irtf.org>; Fri, 29 May 2020 07:30:53 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 5471617FF; Fri, 29 May 2020 10:30:52 -0400 (EDT)
Received: from imap4 ([10.202.2.54]) by compute1.internal (MEProxy); Fri, 29 May 2020 10:30:52 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heapingbits.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type:content-transfer-encoding; s=fm1; bh=33 X9cyJsTO3AojAHeITXi3ak3qo8Sj+eiMXYdyd0alM=; b=JxmPi6crv143HlM8Vh WRAvUlWdgQ7pTeNp2yewsQZgxQzvdHZIvLvsyMgOz5wfJnBiGvCXN8t0zBsF8iH5 7CzTbdDKT+f4tqQzToVUa1nsaUAbMf/2bFDtWowhkoJs6/gElAVgvs+zA/X739ac jwpLWkOgtXrJ2WiHGESSUcAtanCdwsGL/xLGq7NUyFRZuPCDUHrmWz4SHDj6k6ss 6UtYzgcImgGUtTtGZVXm4y8MTAYtedaOtS2jpYT14pzirU+V1UMnMolJh+AD358q HrCVE9UgdQUnT58oUBZSPc6kZigtBBw7Ipw0gdVK8NzaR4A8KbE0hEPn3sN1txw+ yIqw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=33X9cyJsTO3AojAHeITXi3ak3qo8Sj+eiMXYdyd0a lM=; b=q7Qc5/bruR+s6mqcq59kBxG+0hoX+0i/XCJXN25+pKwjAadwXEheBYWtw MS46kzZ9TiDfqFJiifNXYSWwOvPAruYyyvAMVKSjVb5yFbEFuywEsukhi3SCa0TV PkFHTd6psGe4XV1wYU8u/dqdjk4LGVYcHN8hiwwhhM+JRD19w4s49ez19qa1mNsc ua9qSkaLYiw7HDfBkiOpJ57gv8edIVXZHlzUA7UjePqwnKG0WhJyjJW/UfNCGf/3 iIhRPyeAMu79LnyOPKIaATc3oLDz/KFpkzriBLxlCwNEzCqXcugYTSWLrcp4qNyZ cKRLMIkKRVFYQLz+CXFBDpz8GedYw==
X-ME-Sender: <xms:mxzRXtZO4UNAH_W0KP-HJqoT7tyfCV5IsvEM2cVbEljdCagGwL1iew>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedruddvkedgheegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgfgsehtqhertderreejnecuhfhrohhmpedfvehh rhhishhtohhphhgvrhcuhghoohgufdcuoegtrgifsehhvggrphhinhhgsghithhsrdhnvg htqeenucggtffrrghtthgvrhhnpeekffekveeghffgtdffieevudfgledthefhfedvvdeh leeivdegveegleefteejudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegtrgifsehhvggrphhinhhgsghithhsrdhnvght
X-ME-Proxy: <xmx:mxzRXkbxAN0sa5QrUluMnLW8Shz3ALYd77_zLGhkL-E1SeJFn4nXUQ> <xmx:mxzRXv_2EwpfFF4MZs8dbM8GeSjtWqpRquT-PLy7l4v50aAlUwuqtw> <xmx:mxzRXrqwYFT9Foqj-3by2knBK1bL3SYIdJ4vxARcqQiV48E3A-i2hA> <xmx:mxzRXl1-QIuiJBAjijiUgtGpi4dKkP-hvE8ZAxOxyn_4tIFY408UHA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 586733C00A1; Fri, 29 May 2020 10:30:51 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-504-g204cd6f-fm-20200527.002-g204cd6f2
Mime-Version: 1.0
Message-Id: <dd708213-cb04-4279-a48a-229a5663957b@www.fastmail.com>
In-Reply-To: <5F07139C-6493-4A4B-B690-5C807C0A63A0@cisco.com>
References: <08f43a37-2b7b-418e-95a8-ed57484c66be@www.fastmail.com> <F466D238-BCC9-476B-A876-1A72E5B1EEFD@cisco.com> <434A7CA0-DCE1-42A1-89B0-E9B8959B9343@isoc.org> <35B3B2B9-B1E7-41EF-B082-5F5EEF101B0D@cisco.com> <A05941FD-A44A-41DC-90ED-E79E6213700D@isoc.org> <79C21420-970E-46E2-9129-1886597924B1@cisco.com> <eb0f96dc-be68-3473-3a65-39b69e794b5c@cdt.org> <4A68E41D-EF4C-4675-8CFF-ECE0D708661C@cisco.com> <BY5PR06MB645197C9990FB76EA6734BFDB18E0@BY5PR06MB6451.namprd06.prod.outlook.com> <B502F2A7-0444-42D5-A33A-48007BDF8453@cisco.com> <BY5PR06MB6451A72C9AB698391B4A3340B18E0@BY5PR06MB6451.namprd06.prod.outlook.com> <0dff13b6-079e-4cbb-bab7-284cd3bc81da@www.fastmail.com> <5F07139C-6493-4A4B-B690-5C807C0A63A0@cisco.com>
Date: Fri, 29 May 2020 07:30:03 -0700
From: Christopher Wood <caw@heapingbits.net>
To: Eliot Lear <lear@cisco.com>
Cc: pearg@irtf.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/PAvXBCURxaKj5I_FVVuqSOGb3rQ>
Subject: Re: [Pearg] Research Group Last Call for "A Survey of Worldwide Censorship Techniques"
X-BeenThere: pearg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Enhancements and Assessment Proposed RG <pearg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/pearg>, <mailto:pearg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pearg/>
List-Post: <mailto:pearg@irtf.org>
List-Help: <mailto:pearg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/pearg>, <mailto:pearg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 May 2020 14:31:03 -0000

Hi Eliot,

Please see inline below.

On Fri, May 29, 2020, at 1:34 AM, Eliot Lear wrote:
> 
> > To try and sharpen this point a bit: this document will certainly have gaps, and it's not a goal to fill all those gaps. This field moves quickly enough that trying to doing so would likely be futile. 
> 
> I agree, and I am not suggesting that all gaps be covered. That was a 
> straw man put forth by the author.

Great!

> > The chair decision to begin RGLC was based on the document's content and history, which was deemed sufficiently thorough with respect to relevant issues that protocol designers might consider going forward. That said, concrete suggestions to fill in those gaps are welcome! The authors and RG should certainly review them if provided, though we won't block progress waiting for additional content that doesn't substantially change the document's purpose.
> 
> I am sorry I didn’t catch this earlier, but I presumed that last call 
> was meant to address these sorts of matters. 

Indeed it is! I didn't mean to imply that other comments raised were not up for discussion. On the contrary, I think they're helpful contributions that can help improve the document. 

> I would ask that it be 
> noted that there is not a firm consensus on the document as it stands, 
> as several of us have raised substantial issues. Were I to explore them 
> outside of this group in the broader IETF or research communities, I 
> feel certain that you would not find consensus over the terminology. 
> You needn’t take my word for this.
> 
> To restate my concerns, there are three major points and one further 
> down that may or may not be a major point:
> 
>  * The definition of censorship itself does not match common usage.
>  * There is no definition of “censorship regime”.
>  * The one reference I checked was clearly not appropriate in its 
> usage, leading me to wonder about the others.
> 
> On terminology
> 
> It seems that it is being claimed that these are terms of art. 
> Regardless, a properly justified definition with an appropriate 
> reference is in order. This has not happened here. There are two 
> specific problems with the first sentence and its reference. First, the 
> text doesn’t match the reference given. It is never appropriate to 
> mislead the reader in this way. Second, Wikipedia is not a primary 
> source. It is especially important to get the definition right in 
> interdisciplinary work, especially when we are talking about defining a 
> very politically charged term that the rest of the document is 
> dedicated to ameliorating. Beyond the academic matter, as I have 
> previously alluded, by not setting that context, the authors risk 
> offending many practitioners dedicated to infrastructure protection in 
> the very first sentence of the first section.
> 
> Unless you find fault with my reasoning above, and I readily allow for 
> such a possibility, we must agree that this is an issue.  If you place 
> the onus on me to solve it and I refuse, the issue would remain. Of 
> course I am happy to be a part of solving the problem. As it happens, 
> Joe himself put forth a perfectly fine way to put the work into 
> context, to which I readily agreed, but then he himself rejected, even 
> though what he proposed is a close variant of what appears in the 
> document’s abstract. The substance here is the difference between 
> “content" and “information” and perhaps motivation. I am not suggesting 
> a full exploration of what censorship is, but some justification for 
> the language. Same for “censorship regime”, given its similar negative 
> connotations.

With no hat on, I mostly agree. I'll take a stab at addressing this in a PR and share it on the list. We can iterate on the details there. :-)

> On references
> 
> We have previously seen sloppy use of references in at least one other 
> RG. By chance, I have spotted two errors, one to the WP reference and 
> the other only because I know one of the authors of the referenced 
> work. I have not checked the others, but the pass rate right now is 
> 0/2. I would strongly suggest that the other references be checked 
> through broader review.

Yep, these too are good issues to raise now. I'll file an issue to review all references carefully before progressing. 

> Adding the additional non-technical example
> 
> On “Non-Technical [Prescription/Interference]”. As I wrote above, I 
> don’t expect the authors to be exhaustive, but I am told that the topic 
> is out of scope, and yet the text remains. I would suggest an add, 
> perhaps around “swaying public thought”, to include something like 
> “adding financial liability”. The reason I think the point is important 
> enough to raise is that from a scale perspective, the financial attack 
> may be the most effective attack of all against profit-based platforms. 
> Is it major or minor? I don’t know. I lean toward “minor” only because 
> the document might stand up without its mention, even though I would 
> view it as an opportunity lost.

If you have time, could you please suggest concrete text (ideally in the form of a PR)? I think that'll make this discussion easier. 

Thanks again for your review, feedback, and help improving the document!

Best,
Chris