[hrpc] Politics, representation, and the charter (was Re: HRPC recharter)

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 18 April 2023 14:37 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 681F8C1516EA for <hrpc@ietfa.amsl.com>; Tue, 18 Apr 2023 07:37:46 -0700 (PDT)
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="MMZfMkQg"; dkim=pass (1024-bit key) header.d=yitter.info header.b="czcVFoQr"
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 VRW4LBW3GjKX for <hrpc@ietfa.amsl.com>; Tue, 18 Apr 2023 07:37:41 -0700 (PDT)
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 BF3EFC151530 for <hrpc@irtf.org>; Tue, 18 Apr 2023 07:37:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id F07DFBD534 for <hrpc@irtf.org>; Tue, 18 Apr 2023 14:37:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1681828629; bh=52Wo1JuAgEp/7JimlDry8fRrhwVdhUnbnxFOVFJLaDQ=; h=Date:From:To:Subject:References:In-Reply-To:From; b=MMZfMkQgrRg6NM9ccxltpwnS8TKDeD4xFd5GRbqbxKSTdloR3zSgCC5goMAOUp7dU QqYVqhE9HWRlDkxNmLNQAjjF3cFGyUKPgeg6hky5by/J4iXSSw7zdjdlzw618XABTK 3S0F+Hz4tG/CxUrqmVjAxv9FmnaJ1ykazw61t8I4=
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 WacfnuwhxRwQ for <hrpc@irtf.org>; Tue, 18 Apr 2023 14:37:08 +0000 (UTC)
Date: Tue, 18 Apr 2023 10:37:06 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1681828628; bh=52Wo1JuAgEp/7JimlDry8fRrhwVdhUnbnxFOVFJLaDQ=; h=Date:From:To:Subject:References:In-Reply-To:From; b=czcVFoQrXPNvbNE1GsOUw7T1meOAskINTeGKNHLrqnjDtLJYvW5r0rTqnhTnDH9tz ct9Q9IhphVFvMvx37PwZ/7P1TAdTfzcZ0oh6HW0O2Q9Bqz5GR0aa7N9nSqtHGbK8Ys 5VyBuaklz2RIDugHP12S73WkQ3R3RxQ/0xx1M1kk=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: hrpc@irtf.org
Message-ID: <uzngfhbmwm6zmkqh6533qyqdhghooxj2ili5bhkqixtdmm7ua4@xl5egznow756>
Mail-Followup-To: hrpc@irtf.org
References: <CABcZeBMSvWk4MOvv88dfuWtRwy_KBji6YgQG8zmVKcnyNDaqaA@mail.gmail.com> <1717379803.9766.1681364750928@appsuite-gw1.open-xchange.com> <20230413174921.iofttsu3h3gued7u@crankycanuck.ca> <1096362655.14319.1681466701602@fidget.co-bxl> <hkmdydfdj3gb5inh6yazg7dxe26bppwwditzp2mfj4gszqbgxt@eocak2d42plx> <1a7c0475-61a7-e3f3-eda8-1e8245bbbf71@nielstenoever.net> <sqbu2uhyrsvpf2lumrymdextr27ggczbjzljvtab3g44qivfls@cgsa67skzvqc> <53d25652-945a-d726-c51f-59900a78db6f@riseup.net> <kned2jnpn72qxolaoatzctlgk7upjj5dh7ztqa567pvodyjtub@lrqzkqdtgjcs> <66c21184-44c1-6a96-597c-09e8fc3d46b2@riseup.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <66c21184-44c1-6a96-597c-09e8fc3d46b2@riseup.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/IKevi6Cdru75r5dioFPwMLt6AHY>
Subject: [hrpc] Politics, representation, and the charter (was Re: 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: Tue, 18 Apr 2023 14:37:46 -0000

Hi,

Disclaimer still in effect.

On Mon, Apr 17, 2023 at 11:57:54PM +0100, Sofía Celi wrote:
>everyone) and I don't see it there either. We try to be careful when 
>making the slides, hence why I was asking ;)

I didn't go through the entire recording, but in the parts that I did I have not found confirmation of what I recall, so I hereby withdraw my claim and apologize for making the claim.  But, I ran into a part of the discussion that illustrated my point nevertheless.

In the discussion of rechartering, starting about 07:20, Mallory talks about talking to the human rights community and in particular about being in Geneva talking to the UN about what HRPCRG is doing.  If you are a deep insider of the IETF and IRTF, it's possible to understand that discussion entirely within the distinctions that we all understand, though I'm not sure the distinctions were as clear as one might like.  If, however, you come from a government or intergovernmental agency, the framing that Mallory gives it will sound something very like, "The IETF is doing something about human rights and that work is going on in the HRPC group."  This creates an expectation _of the IETF_ on the part of policy-makers.  The IETF has not actually agreed to that expectation, however, which means that the IETF is being forced into a situation where it may need to defend itself against accusations of having failed to live up to an expectation it has not committed to.

As I already noted, I have heard this message repeated back from policy-makers (some of them were in Yokohama but others were not), so this is a rhetorical effect that the RG's output is having in the world even if not intended.  Whatever that is, it is not clear to me that it is "research", and that's part of the reason I'm uncomfortable with the proposed charter text and indeed the scope of the RG.  As a general matter, it seems to me that the IETF has worked hard to build protocols and not policy, though it is not always effective at this.  I am not too convinced that creating a RG that includes "policy" in its name will, therefore, lead policy-makers to grasp the right handle when they attempt to impose policy preferences in an Internet context.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com