Re: [hrpc] ***SPAM**** Re: Censorship

Mallory Knodel <mknodel@cdt.org> Tue, 15 March 2022 19:56 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 1B9843A1738 for <hrpc@ietfa.amsl.com>; Tue, 15 Mar 2022 12:56:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.11
X-Spam-Level:
X-Spam-Status: No, score=-7.11 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, NICE_REPLY_A=-0.001, 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=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 AgSORzaGEUGu for <hrpc@ietfa.amsl.com>; Tue, 15 Mar 2022 12:56:04 -0700 (PDT)
Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) (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 BF6393A1206 for <hrpc@irtf.org>; Tue, 15 Mar 2022 12:56:04 -0700 (PDT)
Received: by mail-oi1-x22c.google.com with SMTP id q189so429318oia.9 for <hrpc@irtf.org>; Tue, 15 Mar 2022 12:56:04 -0700 (PDT)
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 :cc:references:from:in-reply-to:content-transfer-encoding; bh=oIzakMtr6sNN/23eW5irO4o63WMVhCE5B4Ajr8CRpgU=; b=snMGWxsyCUf4qwTdVPP6OZVMAN/qiYQ8YVLbuwNtsRjeWjL9XW2sKYnglbpBmuxmSH fnOFnFhmuS0Rl+45WtWHm6P1iae2RTT7ki+vI4rgqaMszbgW/H9tuvzXdAlRvQ9bs0Q/ 0Ff71I7IJzSIAQPFXDMakb0ZKWTUf5mg3uE5U=
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:cc:references:from:in-reply-to :content-transfer-encoding; bh=oIzakMtr6sNN/23eW5irO4o63WMVhCE5B4Ajr8CRpgU=; b=3bhWXBYjREvGGV0Wo0vtnuZnR1/Byh0665nDijasa5bi5fBXAqriobED6hgxGoTHT7 nrACupKh5JYlipTUEX66J41azu1BN1A/aLJIiKQM2UNK0/NcbwRzcT1ouFZASuc/Q3hB qzyu+TlAUHiEoaNq9QEsGM/tFL7wITlNp2+KCd17CpTdHzY1RantjmG6nOnqJKuwrLyL GvwI0s0cgzRrTkwkT11QLTrYG4CuW0FzlZvU0w+ugJE5r3B7hxgZGmvFFe8sOTXWtwO9 fcqUEXOU0csHrGk9hLjEsPwYG9SjbQzTod22Tn6wLXWzo7mNurLO8AX1C+oWf5oT73JO d2lQ==
X-Gm-Message-State: AOAM533xElv1q4lrr83+9Vy4N4iImltECYmyc1hzQyARWmzT32addkvY pFo4FM2z/I/co9odiq5uSHTvaSkGMSEi+g==
X-Google-Smtp-Source: ABdhPJxE8UQU5Cu5n9wgbz1Sli+rgDWv5qV+DQScqyWMoU6JJfC0WeJREQmOfd9xD1tvqn7N8+xcbg==
X-Received: by 2002:a05:6808:3008:b0:2d9:a0c7:dd3c with SMTP id ay8-20020a056808300800b002d9a0c7dd3cmr2440428oib.181.1647374163591; Tue, 15 Mar 2022 12:56:03 -0700 (PDT)
Received: from [172.20.4.70] ([4.17.95.171]) by smtp.gmail.com with ESMTPSA id 184-20020a4a03c1000000b003240492fc15sm5972061ooi.36.2022.03.15.12.56.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 15 Mar 2022 12:56:02 -0700 (PDT)
Message-ID: <5b7efbed-699c-7da1-718c-f4af94193d19@cdt.org>
Date: Tue, 15 Mar 2022 15:56:01 -0400
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: Eliot Lear <lear@lear.ch>
Cc: 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> <20220313214033.rysyxmydzda2v3kw@crankycanuck.ca> <DgjJ0pvzPp-nRdnSldzL0wBJfaVS74YhB-k_2rln_6ucqpbfaVYynous2WNiSrd2uZ26kaBCYfL8WauDvRvD6WYVePDWrm8zpxSfgd6BRzM=@interpeer.io> <20220314151111.eird5poe2scjoywn@crankycanuck.ca> <fa9562f7-415e-a335-be05-2b137c0a3a21@nielstenoever.net> <20220314192902.fjag7xp6jkprdiyg@crankycanuck.ca> <nTwqrqnZd6czoxYmGRXMNcr-f0rxCBjA88flQjqwNM22eFfnuvGiE-dm8_LkgyhYNVb6MA4DtATpins_9JBV_9jlV7Zeb-CYUchFkeSlot8=@interpeer.io> <af2b4edb-8c23-fd0e-e2a1-b0def85ad34b@cs.tcd.ie> <5293c470-c994-5fbb-67f5-8e996f8288f9@cdt.org> <b5e6c3e8-ce86-7459-583a-43ea53f8b8cf@lear.ch>
From: Mallory Knodel <mknodel@cdt.org>
In-Reply-To: <b5e6c3e8-ce86-7459-583a-43ea53f8b8cf@lear.ch>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/ihm4f2GOq5gQzYwna_4X41TcyKw>
Subject: Re: [hrpc] ***SPAM**** Re: 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: Tue, 15 Mar 2022 19:56:10 -0000

Hi,

On 3/15/22 2:57 PM, Eliot Lear wrote:
> On 15.03.22 15:50, Mallory Knodel wrote:
>>
>>  * Provoking Russia on national security and it will have 
>> ramifications at the UN on the cybercrime treaty and any future hope 
>> of a cybersecurity treaty, 
>
> This in and of itself is worthy of discussion.  Is the UN the right 
> venue for such a treaty?  What do we envision the teeth in such a 
> treaty would be?  I have seen argument out of Sec. Blinken and his 
> State Department that there is room for either direction.
>
We have already the Budapest Convention from the EC but it is old (22 
years!) and has not-so-great bits (intellectual property gets 
disproportionate treatment, etc). Cybercrime treaties are easier to 
create and "enforce" than cybersecurity because their teeth are almost 
all incentives, not punishments. Those incentives are expanded 
jurisdiction and increased cooperation between law enforcement and 
intelligence agencies.

The best we can do in the public interest is limit scope and mandate as 
much as possible or else 'every crime in the digital age is a 
cybercrime'. Civil society has consistently held the line that 
cybercrime must not touch content issues and rather focus on 
core-cybercrimes and it undermines our efforts when there is discord 
about what where content issues are handled, how, and by whom. For 
example, if a cybercrime treaty MUST NOT deal with issues like hate 
speech and incitement to violence because those are already covered by 
other treaty mechanisms and have nothing at their core to do with the 
internet, then we ought not to be seen recommending that we mitigate 
them with internet-specific mechanisms.

Rather than "let god sort them out", can we start saying "let the 
content layer sort them out".

-Mallory

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