Re: [Pearg] I-D Action: draft-irtf-pearg-censorship-04.txt

Joseph Lorenzo Hall <hall@isoc.org> Tue, 04 August 2020 20:31 UTC

Return-Path: <hall@isoc.org>
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 90F5F3A10CA for <pearg@ietfa.amsl.com>; Tue, 4 Aug 2020 13:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.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 doq1mzMpWTrK for <pearg@ietfa.amsl.com>; Tue, 4 Aug 2020 13:31:36 -0700 (PDT)
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11on2085.outbound.protection.outlook.com [40.107.236.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89F5B3A1024 for <pearg@irtf.org>; Tue, 4 Aug 2020 13:31:36 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=anwn4yCeDxIS3ixkFJqoco+vMfnbRwyFNUI2yAsWeJzIepC5Y//6nWC2iSy6VCS5hhTWeVelNz0fdjfpdBFSqxEgk/jm1aaamKopIsFsVv3/ddAmN6GA94CPbrgfEkKp86NXSdex/lUmE2JgYkzgBV624EhjbYLRN3QI1/vqs+t6BelWPuGYIDhXw0VgObLZc7RYODGkmizfC1VJtsmRYWp5kVgfSmhFQ+3bRdgcBD1qdA7XIdbW+joinLifXboR7EA4O1WxBhh0Cl/nyWH8ONFf/YfzPxMrMo8tHpnErsK1Tpkg8nf37Mhv4Ngj+Jf8qstM+Tr+tAKIXNml4gZbcA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=IF1NwIdiD4nFMprgy9mOJX3S5JvzWhhLIr1syz/iqBw=; b=EN1HW/oOTEnDJNv04g/mzXXk3oKlJKCYsB1Dx2OSLILfhOPi6+g2Twt0HJ5TwRcbapfNLnZVHSCno9+FCxVFCefkFTdEsLwNRxCNTF+aAjODTn8FCZ8vVPBgWJRrE8s5DaDzICz09ITvDo/1TlUklIBKOqHaaqY5yNV/sLNMSDYa6mOQnAmcCthK3aYbN1dz6HsfiovcIh7fQE4YFWXSg2j6ZfOfxt20DUHNMKa9+in90z/nSyRgkxLIQf6qtHzp0lXLLDJkJ14OHl4SQan+ytaSAxZ+rcA2a7XNsgT87RPiJYIduzk9WsVvHvPDqMoNIgz3AKsZYtakCjmMoQXMWA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=isoc.org; dmarc=pass action=none header.from=isoc.org; dkim=pass header.d=isoc.org; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.org; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=IF1NwIdiD4nFMprgy9mOJX3S5JvzWhhLIr1syz/iqBw=; b=MTh09Cc1EmmkQG+eWXjdx5IwnBdjOwFk93P/xpTGZj4uzsjHYhi4+mMWBY9mT3neSoH+bO9Nqh9c34Lrk8nMUAIAOBQDYo878wCr+mdy4zBOiWTlcyun0uc1x1ku78fINchbYQW7tYP+LFpZBadsssSd7Uu0k3snt5jusWlTVbE=
Received: from DM6PR06MB6460.namprd06.prod.outlook.com (2603:10b6:5:22f::17) by DM5PR06MB2732.namprd06.prod.outlook.com (2603:10b6:3:46::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.20; Tue, 4 Aug 2020 20:31:34 +0000
Received: from DM6PR06MB6460.namprd06.prod.outlook.com ([fe80::dc53:91ff:b9b8:b55]) by DM6PR06MB6460.namprd06.prod.outlook.com ([fe80::dc53:91ff:b9b8:b55%7]) with mapi id 15.20.3239.022; Tue, 4 Aug 2020 20:31:34 +0000
From: Joseph Lorenzo Hall <hall@isoc.org>
To: Eliot Lear <lear@cisco.com>
CC: Eric Rescorla <ekr@rtfm.com>, Mallory Knodel <mknodel@cdt.org>, "pearg@irtf.org" <pearg@irtf.org>, Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>
Thread-Topic: [Pearg] I-D Action: draft-irtf-pearg-censorship-04.txt
Thread-Index: AQHWWUXitt3bOHP5+EePo8fYbiXCwKkoNHqAgAADtYCAABZkgIAABHwAgAABU4CAACkrgIAADGOA
Date: Tue, 4 Aug 2020 20:31:34 +0000
Message-ID: <CC267086-1DD7-41A9-A62D-168A4252C5EC@isoc.org>
References: <159466596628.22724.642459259274073600@ietfa.amsl.com> <116747697.938.1596554741142@appsuite-gw2.open-xchange.com> <57fefee9-f3d5-cf5f-3980-2b589c0aa2e9@cdt.org> <1761878407.1099.1596560345496@appsuite-gw2.open-xchange.com> <CABcZeBO4+tVcc=TjDz44o-6SK2+e2J5E+bP_cN5UHqiKTyotzw@mail.gmail.com> <F62D3E02-510C-4AAB-A06E-E21BE83A9B74@isoc.org> <86B902F9-0222-4E6A-B75F-7E6E505BC572@cisco.com>
In-Reply-To: <86B902F9-0222-4E6A-B75F-7E6E505BC572@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3608.120.23.2.1)
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.com; dmarc=none action=none header.from=isoc.org;
x-originating-ip: [108.56.212.130]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 90314c72-c177-4c67-a341-08d838b56125
x-ms-traffictypediagnostic: DM5PR06MB2732:
x-microsoft-antispam-prvs: <DM5PR06MB2732BC00D1622C772CFAB401B14A0@DM5PR06MB2732.namprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: H+kR/wTe33fhrVxK42t/B2zshCvQN8aKtfWp8onP27D3+RaplSyDq5i1fzFXfhmzuizEViyHwY2YNAtpS9OuHI9DbuYyIZ5XVjYtwT2M+8DybyxBZvn4vaDhb3SJPdHiVXTv+fQKoiV0aFZf4qwKCN99EDPvmVMyMvATLsqKRhLgSSXEENiCVSDTIu/WXa9nql8cP/n27MF1MABzOeZB8ZzK3CR6bY9s2tyAuqItbzWvbZKNVIWjiqMWp/672BXAwiw21eB1KRjchwdykD44l8R9pRNbuIrwLReW+0G8waHHaAfar5zrtrsSOxDvMTuHTZ4jbueNQsiFOx6Ls3xGZh2cxuxvWNLMMsKU8TlWZGAX7D83vNQS+AF+w5BoGEgtlL5pjJFOdZbyi2SnDwIyTA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR06MB6460.namprd06.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(136003)(39850400004)(396003)(366004)(346002)(376002)(71200400001)(86362001)(478600001)(36756003)(4326008)(8676002)(6486002)(966005)(8936002)(6916009)(2616005)(5660300002)(166002)(6512007)(53546011)(76116006)(91956017)(66446008)(316002)(66476007)(64756008)(16799955002)(66556008)(6506007)(54906003)(33656002)(66574015)(83380400001)(2906002)(186003)(26005)(66946007); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: PLCdNEU47NPAvw7WXdsn/LlWZsa1i+ANIn5AMkpN0FFe7fUdgRAzpdzCLCQ8I+qKCuUIbu0wVwi9j8mZkw6cbMPWXRsbhscT1+chrvUnYC0w8soVkM7lpsdPe78CY8o06IrLRKOqGuhNjvz3Mest4ebs4QbplE9hJb46ss7huZz8i1lUDefZ7JyWCQZo8tLsNpSwZE48wa6QF4sMMDxHReDwByHaEmMFAfI5hRGzKXbxznJ02ooP4EEMgp82oteh3p45fFJoRWEzAak+ZZoOaMfIs75f3RgAkiGATEpL33O2tCXhLuqXwyuTgpyky3gYWawLSHiObmRKFAN3DzB++WTj1CS6Fz9c0ahQONv9STwoOPslMoP0+Xv12YLvOya8kw4IYD+KOC1npjx5vkrdnlOPkqagClO5OpYr06pRTukeLCqaEnf8dj7oo0/hbVQ0nxkf7iPIjw7FR9Vpu2hBeT5/OKGMyGFQ/ABsoOo3f4rOr2hEOJYp/7Cw7eYpeJnf8rs/i/sE5jHLVm777ECNiaPLivsXjFQuJf0KFNNAARti5qn9sIKRhoY3KsehfxsdpI+JCaV2FHF/EVsfnS6JoZ9yAGPmyMXqCPR8B2Rgc35e1EQl4GggummyIMJbcMm9kT/GHfhmcRdXoE4qygrObQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CC2670861DD741A9A62D168A4252C5ECisocorg_"
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR06MB6460.namprd06.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 90314c72-c177-4c67-a341-08d838b56125
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Aug 2020 20:31:34.1146 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: dzVwso5+bs6LFUFxjz+K8HO3+6k9CW9Ay/KPlclxGozC4tyYvSNyFKA+2WQWEK7d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR06MB2732
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/TCNBQphOXSbqfasGaXiItF-ewvM>
Subject: Re: [Pearg] I-D Action: draft-irtf-pearg-censorship-04.txt
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: Tue, 04 Aug 2020 20:31:39 -0000


On Aug 4, 2020, at 3:47 PM, Eliot Lear <lear@cisco.com<mailto:lear@cisco.com>> wrote:

Where I think we get to have more of a voice is how those terms apply to us and our industry, and that is something we shouldn’t duck.  Therefore, my view is that we should go with a definition that would be generally acceptable to appropriate experts, if there is one.  I will note that the Wikipedia one has changed in the time you wrote the document, which does lead to a concern about stability.   You could otherwise hedge along the lines Vittorio is suggesting or in some other way.

A quick clarification: When one cites wikipedia, there are specific ways to do that to make sure that the thing you cite to does not change. So, in the draft, we do this:

 [WP-Def-2020]
              Wikipedia contributors, "Censorship", 2020,
              <https://en.wikipedia.org/w/
              index.php?title=Censorship&oldid=943938595>.

Which points to a specific historical instance of the Wikipedia page on censorship (rather than whatever it is now). So, technically, the definition that we are using has not changed. That being said, the current definition differs from what we point to by one word, and I do like the more current version (changes “corporations” to “controlling bodies”) but it’s not a big enough change to me remarkable in my opinion.

But then we should also at least briefly state how the term applies in our context, so as to make clear that the intent is not to label every network administrator a censor.  Keep in mind that there are a great many devices on the network that will process content that have no UI, that have very limited ability to protect themselves.  Explaining how that protection is viewed is a bit broader than the scope of the current document, but would not be out of line for this group to cover, if only for a few lines.

There is also a human element that also needs to be captured in this context that a few of us noted: there are negative connotations with the word, as there should be (IMHO).  I would encourage HR people to appreciate those connotations and not to weaken them by attempting to stretch the definition beyond what you believe is really bad for society, as you will otherwise inure people to the very thing you wish to prevent.

All of this having been said, if you do want to continue on the discussion of the definition:


On 4 Aug 2020, at 19:19, Joseph Lorenzo Hall <hall@isoc.org<mailto:hall@isoc.org>> wrote:

I’m not sure consent vs. non-consent will address Vittorio or Eliot’s critiques here, I suspect not.


For my part it’s pretty close, my caveat being that the it would not be censorship if the owner of the device receiving the content in particular either did or would have freely and expressly given consent to certain harmful content being blocked.  I’ll readily note that is not a testable condition in advance, although it would be in retrospect.  Look at it this way: if your neighbor sees a robber breaking into your house while you are on vacation, would you like the neighbor to wait for permission to protect your property?  Surely not.

Thanks, Eliot (sorry for double-l-ing you earlier!).

I think I’m starting to see the outlines of a paragraph that capture this… I’ve heard from a few people that are on vacation that can’t opine until next week at the earliest, so I’ll wait to hear more and then take a shot at it.

best, Joe

(work at ISOC, here as my self)

--
Joseph Lorenzo Hall, Senior Vice President, Strong Internet
hall@isoc.org<mailto:hall@isoc.org> | +1-703-483-9504
internetsociety.org<http://internetsociety.org> | @internetsociety
pgp: https://josephhall.org/gpg-key
3CA28D7B9F6DDBD34B1016075F86698740A9A871