Re: [hrpc] wg adoption of draft-giuliano-blocking-considerations

Niels ten Oever <mail@nielstenoever.net> Tue, 19 July 2022 20:57 UTC

Return-Path: <mail@nielstenoever.net>
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 B06DCC13194E for <hrpc@ietfa.amsl.com>; Tue, 19 Jul 2022 13:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DmFCV1U0YEH7 for <hrpc@ietfa.amsl.com>; Tue, 19 Jul 2022 13:57:51 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.88]) (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 62E35C14F74A for <hrpc@irtf.org>; Tue, 19 Jul 2022 13:57:50 -0700 (PDT)
Message-ID: <100fd88b-c5f1-841b-55b9-f1b8bc3fc1d9@nielstenoever.net>
Date: Tue, 19 Jul 2022 22:57:45 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
To: hrpc@irtf.org
References: <Pine.LNX.4.64.2207190935350.29130@mail.lenny.net>
From: Niels ten Oever <mail@nielstenoever.net>
In-Reply-To: <Pine.LNX.4.64.2207190935350.29130@mail.lenny.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Authenticated-As-Hash: f1842a279235a42f6aa2a2a81130733515c5a4ec
X-Virus-Scanned: by clamav at smarthost1.greenhost.nl
X-Scan-Signature: e462de357cb394d64966911c06262bc8
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/DWmhSYcUYzsaLMXabltpqo-wY9M>
Subject: Re: [hrpc] wg adoption of draft-giuliano-blocking-considerations
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.39
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, 19 Jul 2022 20:57:56 -0000

I think it is not correct to say that there seemed to be interest in this draft during the hrpc session in Vienna. Only the ISE showed interest. If you want to take this further (which I think you should not because draft-irtf-pearg-censorship does the job of this draft much better), I suggest you take it up with the ISE.

To make it more clear, I hope hrpc will not make this a work item.

Best,

Niels

On 19-07-2022 15:38, Lenny Giuliano wrote:
> 
> <Sorry for cross-posting, but wasn't sure if HRPC or PEARG was the more appropriate WG>
> 
> In IETF113, we presented draft-giuliano-blocking-considerations-00 in HRPC (as well as in int-area).  The purpose of this draft is to document the well-known approaches for blocking the Internet connectivity of regions/nations (eg, for the purpose of sanction).  This doc does not advocate for/against such a policy, but rather explains what is technically possible, how it might work, how effective it might/might not be and what might be the potential intended/unintended consequences. This doc is intended to provide sober, unbiased information for those who do advocate/implement such policies- a "read this first before taking action" document to help inform a policy-maker when deciding whether such a policy is a good idea or not.
> 
> In HRPC in Vienna, there seemed to be some interest in this work in some form. One suggestion was to add parts of it to draft-irtf-pearg-censorship, but looks like that train has left the station.  Another option would be adopt this draft in HRPC or PEARG. Looking at the charters of each, HRPC seems like a better fit (albeit, more "deployment considerations" than "protocol considerations") but we're fairly new to both WGs.
> 
> Here's a link to the draft. Comments and suggestions for next steps would be most welcome: https://datatracker.ietf.org/doc/draft-giuliano-blocking-considerations/
> 
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc

-- 
Niels ten Oever, PhD
Postdoctoral Researcher - Media Studies Department - University of Amsterdam
Affiliated Faculty - Digital Democracy Institute - Simon Fraser University
Non-Resident Fellow 2022-2023 - Center for Democracy & Technology
Associated Scholar - Centro de Tecnologia e Sociedade - Fundação Getúlio Vargas
Research Fellow - Centre for Internet and Human Rights - European University Viadrina

Vice chair - Global Internet Governance Academic Network (GigaNet)

W: https://nielstenoever.net
E: mail@nielstenoever.net
T: @nielstenoever
P/S/WA: +31629051853
PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3

Read my latest article on understanding power in standardization in the Journal of Standardisation here: https://journals.open.tudelft.nl/jos/article/view/6205/5361