IETF Logo Mail Archive

[hrpc] Censorship

Vittorio Bertola <vittorio.bertola@open-xchange.com> Fri, 11 March 2022 08:58 UTC

Return-Path: <vittorio.bertola@open-xchange.com>
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 816603A0897 for <hrpc@ietfa.amsl.com>; Fri, 11 Mar 2022 00:58:09 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=open-xchange.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 Nty0VHiGXwyS for <hrpc@ietfa.amsl.com>; Fri, 11 Mar 2022 00:58:04 -0800 (PST)
Received: from mx3.open-xchange.com (mx3.open-xchange.com [87.191.57.183]) (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 94A9B3A0828 for <hrpc@irtf.org>; Fri, 11 Mar 2022 00:58:04 -0800 (PST)
Received: from imap.open-xchange.com (imap.open-xchange.com [10.20.28.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx3.open-xchange.com (Postfix) with ESMTPSA id B62646A0F3 for <hrpc@irtf.org>; Fri, 11 Mar 2022 09:57:59 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1646989079; bh=eHbqsYBn9YH4zppjuJnBZAqw78uM8fEjQwsjr1USfs0=; h=Date:From:To:Subject:From; b=6vdR5eKjQzqd1Z+dCOjflYE07DJiplYHtG4f66i12XVJaeUiOWtZugx5aFbY0j3B9 Z1N21bIAywZM9L4GgeMPMi6AUzMQ14cVBy/QbkApVH4GkZptF+5xO/MygiA2a0MQUm AbeLs89MKtHt+6r13A0tBds6K2UP1B1u1HykCf3rZV6UY+YLLs6Ys+qGhdDhznb+4m CicJoa4YerbD9kLgoNpSzIRNVx34UfMLbBt1fRVXqNsnI35cpR2ALYgZ9+5C+NrQQU +toFv5TOlfn7/3CiSghrkDdRZo4+/h2w9Se6u7zNCi0olm/GE1BM5XFRzZGNHEAWvO em9G2BkGmrmGA==
Received: from appsuite-gw2.open-xchange.com ([10.20.28.82]) by imap.open-xchange.com with ESMTPSA id 7KIqKxcPK2JQGwAA3c6Kzw (envelope-from <vittorio.bertola@open-xchange.com>) for <hrpc@irtf.org>; Fri, 11 Mar 2022 09:57:59 +0100
Date: Fri, 11 Mar 2022 09:57:59 +0100
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: "hrpc@irtf.org" <hrpc@irtf.org>
Message-ID: <669686052.184329.1646989079672@appsuite-gw2.open-xchange.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_184327_919975714.1646989079660"
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.6-Rev9
X-Originating-Client: open-xchange-appsuite
Autocrypt: addr=vittorio.bertola@open-xchange.com; prefer-encrypt=mutual; keydata= mQENBFhFR+UBCACfoywFKBRfzasiiR9/6dwY36eLePXcdScumDMR8qoXvRS55QYDjp5bs+yMq41qWV9 xp/cqryY9jnvHbeF3TsE5yEazpD1dleRbkpElUBpPwXqkrSP8uXO9KkS9KoX6gdml6M4L+F82WpqYC1 uTzOE6HPmhmQ4cGSgoia2jolxAhRpzoYN99/BwpvoZeTSLP5K6yPlMPYkMev/uZlAkMMhelli9IN6yA yxcC0AeHSnOAcNKUr13yXyMlTyi1cdMJ4sk88zIbefxwg3PAtYjkz3wgvP96cNVwAgSt4+j/ZuVaENP pgVuM512m051j9SlspWDHtzrci5pBKKFsibnTelrABEBAAG0NUJlcnRvbGEsIFZpdHRvcmlvIDx2aXR 0b3Jpby5iZXJ0b2xhQG9wZW4teGNoYW5nZS5jb20+iQFABBMBAgAqBAsJCAcGFQoJCAsCBRYCAwEAAp 4BAhsDBYkSzAMABQMAAAAABYJYRUflAAoJEIU2cHmzj8qNaG0H/ROY+suCP86hoN+9RIV66Ej8b3sb8 UgwFJOJMupZfeb9yTIJwE4VQT5lTt146CcJJ5jvxD6FZn1Htw9y4/45pPAF7xLE066jg3OqRvzeWRZ3 IDUfJJIiM5YGk1xWxDqppSwhnKcMOuI72iioWxX0nGQrWxpnWJsjt08IEEwuYucDkul1PHsrLJbTd58 fiMKLVwag+IE1SPHOwkPF6arZQZIfB5ThtOZV+36Jn8Hok9XfeXWBVyPkiWCQYVX39QsIbr0JNR9kQy 4g2ZFexOcTe8Jo12jPRL7V8OqStdDes3cje9lWFLnX05nrfLuE0l0JKWEg8akN+McFXc+oV68h7nu5A Q0EWEVH5QEIAIDKanNBe1uRfk8AjLirflZO291VNkOAeUu+dIhecGnZeQW6htlDinlYOnXhtsY1mK9W PUu+xshDq7lXn2G0LxldYwyJYZaJtDgIKqVqwxfA34Lj27oqPuXwcvGhdCgt0SW/YcalRdAi0/AzUCu 5GSaj2kaGUSnBYYUP4szGJXjaK2psP5toQSCtx2pfSXQ6MaqPK9Zzy+D5xc6VWQRp/iRImodAcPf8fg JJvRyJ8Jla3lKWyvBBzJDg6MOf6Fts78bJSt23X0uPp93g7GgbYkuRMnFI4RGoTVkxjD/HBEJ0CNg22 hoHJondhmKnZVrHEluFuSnW0wBEIYomcPSPB+cAEQEAAYkBMQQYAQIAGwUCWEVH5QIbDAQLCQgHBhUK CQgLAgUJEswDAAAKCRCFNnB5s4/KjdO8B/wNpvWtOpLdotR/Xh4fu08Fd63nnNfbIGIETWsVi0Sbr8i E5duuGaaWIcMmUvgKe/BM0Fpj9X01Zjm90uoPrlVVuQWrf+vFlbalUYVZr51gl5UyUFHk+iAZCAA0WB rsmACKvuV1P7GuiX3UV9b59T9taYJxN3dNFuftrEuvsqHimFtlekUjUwoCekTJdncFusBhwz2OrKhHr WWrEsXkfh0+pURWYAlKlTxvXuI7gAfHEQM+6OnrWvXYtlhd0M1sBPnCjbyG63Qws7Rek9bEWKtH6dA6 dmT2FQT+g1S9Mdf0WkPTQNX0x24dm8IoHuD3KYwX7Svx43Xa17aZnXqUjtj1
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/O9OyvXaJQYYObKNFZ5OMwFeLJqg>
Subject: [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 08:58:10 -0000

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  mailto:vittorio.bertola@open-xchange.com 
Office @ Via Treviso 12, 10144 Torino, Italy

v2.46.0 | Report a Bug | By Email | System Status