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

Eric Rescorla <ekr@rtfm.com> Tue, 04 August 2020 17:15 UTC

Return-Path: <ekr@rtfm.com>
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 954B63A0DAC for <pearg@ietfa.amsl.com>; Tue, 4 Aug 2020 10:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=rtfm-com.20150623.gappssmtp.com
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 Bmfvr9gy0Vq6 for <pearg@ietfa.amsl.com>; Tue, 4 Aug 2020 10:15:47 -0700 (PDT)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (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 AC41E3A0D9E for <pearg@irtf.org>; Tue, 4 Aug 2020 10:15:46 -0700 (PDT)
Received: by mail-lj1-x230.google.com with SMTP id v12so14134343ljc.10 for <pearg@irtf.org>; Tue, 04 Aug 2020 10:15:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/Vs4+yhLdVCn+spAB5Ivt8/mXyU45rnmzvaQlvBY1Bo=; b=1qMJxZPdFo8cDnFqAegZV13LB6/eHXgjtHA4QkItNCdAEdPYW2IZs+e8p+Ev3CFtcb bE8e+qAHW6/6pRJmvdHkg8rgDGrKbUtw4fjNNRXsk4fdilnH0oxqf+nxM4+7zTfgNuid lluxHF3VCqsvI6j+O2P0sdpVEK/gJUWR98Tewje6+NC8C/SUj5QZkX2xB+kWxrpCzGK7 OCyaC+PAtO/30aXaVipnxL28XmfxnNP1oLFUr54OnruUtUzLClEcs4E01LMlV9YZ0aHk iIbY5+mU6P/TY+5pj3ztJ5++XUYUDJAUmr6Tl7NdGKQwkKICatI126G9joOCwPTJMP9N G18Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/Vs4+yhLdVCn+spAB5Ivt8/mXyU45rnmzvaQlvBY1Bo=; b=fnAqiZVW7hifq7M46yypWT2C3ZEumRm6JmQMrDcfS7Oow+bxQQkZibGFBIkpHG9udb FEPjp/DiinxPGTVy6MxKEwLW9ZAsos7oIu2qnmxXuRfBRiqT2nMfk/UNNAGqzYTNpuuZ nEt8cN71wD2uZgPtnEIX5jBQN4L6OBoCW2SsyR9kgYSsHQm3G0fNRATtWOFjQgwE9ezj X7KqkbbM40EsLVB/gj22dRjl526VvDQZlax4Q0NjPzZzKan50l4gd6xG1vtBAz87wvyj GH8EuFHeYKTPKCb2s2SZzOc5bWYF1pCmYdLpNyETt/cS/Y1mXO4KkFE5WRMwWITWRVWs Zdww==
X-Gm-Message-State: AOAM533tyZn98OCUQl8ci25Y+ePUeL1jgWUP7R/qjMZXDiFKxdh/PysY 3aNnTKsqj2i9I2TnUupSPp+Es+5IX5v+mJvVGuP+jg==
X-Google-Smtp-Source: ABdhPJzJE6Ro5xkbcNdrSMih9t0feGilCAyJ/Wuf+z+6eUVBX7scU1yCT0CwXv6ADzocqXOj2Wb1PljfhVh48xQaj4A=
X-Received: by 2002:a2e:9b4a:: with SMTP id o10mr10698628ljj.199.1596561344818; Tue, 04 Aug 2020 10:15:44 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <1761878407.1099.1596560345496@appsuite-gw2.open-xchange.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 04 Aug 2020 10:15:08 -0700
Message-ID: <CABcZeBO4+tVcc=TjDz44o-6SK2+e2J5E+bP_cN5UHqiKTyotzw@mail.gmail.com>
To: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>
Cc: Mallory Knodel <mknodel@cdt.org>, pearg@irtf.org
Content-Type: multipart/alternative; boundary="000000000000d2184105ac1067f0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/IVJV8P2HSm4iuFeKK4sj-84WdkE>
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 17:15:49 -0000

On Tue, Aug 4, 2020 at 9:59 AM Vittorio Bertola <vittorio.bertola=
40open-xchange.com@dmarc.ietf.org> wrote:

>
>
> > Il 04/08/2020 17:38 Mallory Knodel <mknodel@cdt.org> ha scritto:
> >
> >
> > On 8/4/20 11:25 AM, Vittorio Bertola wrote:
> >
> > > So for a significant part of the Internet community these techniques
> can be used for legitimate purposes other than censorship, and this should
> be acknowledged from the beginning, agreeing that not everyone using these
> techniques is a censor or accepts to be depicted like that.
> >
> > It's been said in this thread that censorship can be legitimate or
> > illegitimate.
>
> But not in the draft, as far as I can recall.
>
> > It shouldn't be the aim of this draft to talk about the censors at all,
> > nor how they'd like to be depicted. The draft is about the techniques.
>
> The point is whether we can ever come to consensus on this draft and turn
> it into an RFC, which in my opinion is going to be hard if some IETF
> participants have to accept to be labelled as "censors" for using the
> techniques in the draft to, say, block access to phishing websites, or
> execute a court order.
>

As I said before, it's useful here to distinguish between blocking that is
with the consent of the user (albeit sometimes in an opt-out fashion as
with safe browsing) and that which is imposed on the user without their
consent. I don't see a problem with calling the latter censorship, even if
the content being blocked is non-political.

-Ekr