Re: [hrpc] HRPC recharter

Andrew Sullivan <ajs@anvilwalrusden.com> Fri, 06 January 2023 16:31 UTC

Return-Path: <ajs@anvilwalrusden.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 29C82C14CE24 for <hrpc@ietfa.amsl.com>; Fri, 6 Jan 2023 08:31:50 -0800 (PST)
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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=QJMh3U+C; dkim=pass (1024-bit key) header.d=yitter.info header.b=Hg2v9FJd
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 CMuUued5Fmkk for <hrpc@ietfa.amsl.com>; Fri, 6 Jan 2023 08:31:45 -0800 (PST)
Received: from mx5.yitter.info (mx5.yitter.info [159.203.31.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DA7DC1522C6 for <hrpc@irtf.org>; Fri, 6 Jan 2023 08:29:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id 85FE6BD534 for <hrpc@irtf.org>; Fri, 6 Jan 2023 16:28:27 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1673022507; bh=9DlO5cFD/zXcbrtoD/Qqgdng73vqjY94DfPCRYaQQVg=; h=Date:From:To:Subject:References:In-Reply-To:From; b=QJMh3U+CgNj/oWmlfjDdKPBcoU8qs6wlyMjE8hTmGifqCrixdW9DPMu6k+U51m5p3 VbPKMLnpLe9/hKuluATM8uCHRDaBLYBqj+iFoFGMCwDgEiy7AVCSgEnBCHKnQcP9QC cadRPYVxQ03djWGxv386RP/fDBQ/tFakCSgkmh+s=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx5.yitter.info ([127.0.0.1]) by localhost (mx5.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ihzZdxdy12Ph for <hrpc@irtf.org>; Fri, 6 Jan 2023 16:28:25 +0000 (UTC)
Date: Fri, 06 Jan 2023 11:28:25 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1673022505; bh=9DlO5cFD/zXcbrtoD/Qqgdng73vqjY94DfPCRYaQQVg=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Hg2v9FJdZSE914AVO4qa9WFtIUZSh8LNrdMS5hWgD3jBgxOSqQPG8WJBtM+MYEVuG 4lQOSMiCRzPSCtDtew0yZWwF1RBwnkM2nOs/H+Z/3gbEvr1/9nc9YQAT+/GI02YqGK RLr/AUcO7Ws0Yc7iQ2Nl33x2KpqEtcheNnhYme5o=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: hrpc@irtf.org
Message-ID: <20230106162825.canpeuncoy2y4p7u@crankycanuck.ca>
Mail-Followup-To: hrpc@irtf.org
References: <6ddd480d-76ed-a05e-066d-d740fee61441@cdt.org> <20230104215936.5exwsmtztk2shnzb@crankycanuck.ca> <63464538-4d40-a946-bcbe-570a6a3b49f9@lear.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <63464538-4d40-a946-bcbe-570a6a3b49f9@lear.ch>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/n4iFIpg-Ns5VCvkP4-g450HxAvc>
Subject: Re: [hrpc] HRPC recharter
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: Fri, 06 Jan 2023 16:31:50 -0000

Hi,

obligatory disclaimer still in effect.

On Fri, Jan 06, 2023 at 09:49:29AM +0100, Eliot Lear wrote:

>2014 had in mind.  However, there is, at least in my mind, no doubt 
>that protocols and policies *can be* highly intertwined (cf SHAKEN and 
>STIR).  Clearly this must have been what you folk on the IAB had in 
>mind when you created this group in the first place, no?

I can't speak for the thoughts of the IAB at the time, but as I understood things then our job was only to review and not to establish or govern the plans of RGs.  I remember participating in the early discussions for the RG.  Early on I was sceptical about the scope then, because it wasn't clear to me what it had to do with protocols, and I thought the chartering discussion helped tighten that up to the point where I thought it would be a useful RG.

>suggestion about using the word "explore".  Also, I have, as you have 
>seen, been concerned about this group addressing only *some* human 
>rights and not *all* human rights.

Right, and the trouble is that the set of rights under the UDHR is not necessarily consistent, as you note.  I have thought it'd be quite conceivably useful for someone to produce guidance for protocol designers on how to evaluate such trade-offs during protocol design.  (I am emphatically not volunteering, because I have no idea.)

>Nevertheless, if I understand the lay of the land correctly, nobody is 
>arguing that this group should have a political advocacy function. 

Hmm.  I have been under the impression that some people do think that, so perhaps I am confused.

>NEW:
>
>>  * Academic papers, for in-depth analysis and discussion of the
>>    values embedded in the Internet architecture and their policy
>>    implications, as well as the impact of policy on protocol development.
>>
>"Policy papers" is often used for papers that are shills for 
>advocacy.  Let's not invite those here.  But both input and output 
>need to consider policy implications.

I think that may be a useful distinction, yes.

>>But it is obscure to me what the research question is in such cases.
>
>Strictly speaking, the RG charter needn't define a research question; 
>it can leave that up to the individual researchers themselves.

Sure.  Perhaps I should have said "topic" rather than "question", though.  The point is still that I don't understand the extent to which such things qualify as research rather than advocacy.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com