Re: [hrpc] HRPC recharter

Andrew Sullivan <ajs@anvilwalrusden.com> Fri, 06 January 2023 02:10 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 5F5F6C1516E1 for <hrpc@ietfa.amsl.com>; Thu, 5 Jan 2023 18:10:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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_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=i3JX2SLs; dkim=pass (1024-bit key) header.d=yitter.info header.b=R4FBmgxc
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 E15TlOtMfC0e for <hrpc@ietfa.amsl.com>; Thu, 5 Jan 2023 18:10:00 -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 14786C151534 for <hrpc@irtf.org>; Thu, 5 Jan 2023 18:09:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id 5BB24BD534 for <hrpc@irtf.org>; Fri, 6 Jan 2023 02:09:55 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1672970995; bh=MpX/gBxFUVrm7wtQK67WW4XAre3PNBN6Zsuyi27fNPc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=i3JX2SLs+evCsjQdHCw58VFJm7mCOBaIH4DPAOCJjvkmA851l1njSvHcIOgX9aZjO WW7+8aPAulPkniKeP7nIuCLXlInTYDpiiCW7Bq7m/umZy4CrE/+N5PBTMU9u/4BbDg 8M6ve+2uPDfsWZ3qjsr9R23Gx/rkmJjHbTQLmxsc=
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 fViyf5vdXNcw for <hrpc@irtf.org>; Fri, 6 Jan 2023 02:09:53 +0000 (UTC)
Date: Thu, 05 Jan 2023 21:09:51 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1672970993; bh=MpX/gBxFUVrm7wtQK67WW4XAre3PNBN6Zsuyi27fNPc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=R4FBmgxc9YXhMQge6EPteQFXO830soAdud7k4U4N7RVPDiijgheenm1MN98bQdDMj SoL2VgPIIyhDxu8pL+DaZS9/7avHL68eydoMMMFdRG6vvhuFhpWL3eLuwk8rigHQbt tInPvCqanu+k/x5t2yKSnt3smzHo6Z6TJLs6EJ1E=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: hrpc@irtf.org
Message-ID: <20230106020951.wrv6cgr6eci4lqoo@crankycanuck.ca>
Mail-Followup-To: hrpc@irtf.org
References: <6ddd480d-76ed-a05e-066d-d740fee61441@cdt.org> <CABcZeBO-kN+KmNcGuiAxv5ZidvuZW5A5yjB2mP_ZJCiF1qNLyg@mail.gmail.com> <f727a6c8-7f1e-0db8-46d0-36248b921b79@cdt.org> <CABcZeBPuGUXcAo6z+uSCn=99ct7ALxOP8aQHYX+ncViLitMciw@mail.gmail.com> <ff338456-b2b5-0eec-f18f-be81ef1afe99@cdt.org> <CABcZeBO_9tjxDTurFr-uaN6OAPR1=Qo7aJNNHMprLPBUyrsAEg@mail.gmail.com> <68dab8e6-b17c-4ceb-5267-d4edb62f3eea@cdt.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Disposition: inline
In-Reply-To: <68dab8e6-b17c-4ceb-5267-d4edb62f3eea@cdt.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/sgfSnJZUNSZtLbJbssupOLg7QJQ>
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 02:10:05 -0000

Dear colleagues,

Still employed, still just my opinion.

On Thu, Jan 05, 2023 at 11:01:07AM -0500, Mallory Knodel wrote:

>Understood that this is your view. On the other hand, the feedback we 
>are consistently getting in our actual meetings and through our most 
>recent IAB review is that in fact HRPC is contributing and doing well 
>and we don't need to be overwrought in our attempts to do more work.

My reading of the minutes of the IAB meeting from 2022-11-08 is doubtless more poorly informed than yours would be, since I wasn't in the meeting. Nevertheless, when I read them what I do not see is a lot of encouragement of scope changing.  What I read, on the contrary, is some hesitation about the wisdom of expanding the scope in this way. The person on the IAB who was arguing for that explicit scope expansion is also a chair of this RG (i.e. you.  BTW, the minutes aren't linked at https://www.iab.org/wiki/index.php/RG_Reviews but are in the main IAB minutes pages).

>This is why I want to make very incisive changes to the charter that 
>very slightly expand the work into policy

But this is the concern I was trying to raise in my prior note to the list: I don't think the text you have proposed is incisive change or very slight expansion.  Instead, if I read it correctly, it appears to turn the RG into a (not to say "yet one more") venue where people come together to talk "policy" without much in the way of bounds on what is in or out of scope or even what kind of policy is involved.  I don't wish to be provocative, but I am sceptical that the IRTF needs to reproduce the Internet Governance Forum.  

>are those that disagree that we even need to specify this change given 
>that policy already is under the purview of talking about human 
>rights.

It seems to me that restricting the policy discussions to ones that have direct human rights implications might help in making the scope of the charter somewhat more manageable, even if it would still be an enormous ocean to boil.

>In other words: I don't believe it is widely accepted that HRPC has a 
>misguided view of its own purpose. Others may, but that has 
>unequivocally improved since it was first chartered.

I must say that I very strongly disagree with that "unequivocally improved" claim.  I thought the original charter discussion was pretty good because of the way it whittled the space down to a set of questions that one could imagine answering through research.  I was indeed frustrated over time by the way the RG resisted sticking to those questions, but at least there was something to hang on to.  I don't think officially giving up on such scope limitations is an unequivocal improvement.  (Maybe I'm just old-fashioned.  I also believe that, say, musical forms often provide a better structure for creativity than a total lack of such structure.)

I suppose I will receive a suggestion that I make a PR at the github, but if I am honest I don't really understand why the charter text needs to change except perhaps to remove bullet 2 under "Objective".

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com