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

Sofía Celi <cherenkov@riseup.net> Wed, 19 April 2023 09:23 UTC

Return-Path: <cherenkov@riseup.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 B7B58C15C510 for <hrpc@ietfa.amsl.com>; Wed, 19 Apr 2023 02:23:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=riseup.net
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 MBkaw9x7C9L5 for <hrpc@ietfa.amsl.com>; Wed, 19 Apr 2023 02:23:15 -0700 (PDT)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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 53484C14068D for <hrpc@irtf.org>; Wed, 19 Apr 2023 02:23:15 -0700 (PDT)
Received: from fews01-sea.riseup.net (unknown [10.0.1.109]) (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 mx1.riseup.net (Postfix) with ESMTPS id 4Q1b1Z50WFzDqZn for <hrpc@irtf.org>; Wed, 19 Apr 2023 09:23:14 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1681896194; bh=J1+0l7/OdCxOSGAF88U51IhM+qzo5C1F1wWcF62s3GQ=; h=Date:Subject:To:References:From:In-Reply-To:From; b=Cy62xtSmO+P1+bt66kV0gc31J1rlV9O9A8VGQEhu31/OskTlhlvieN0RUjeg3vQxG njHdoH0EElzRBtA7FYs/KwrsZTWDcB9UaL9ckkfkS4aDZem1Fr1GOdK5B/KLHZ/zyA szWNQxdMwD7hLvjojMh9V/Zx/Ydd0jwEIaZCIl5U=
X-Riseup-User-ID: F5BFDBBF71A1022ED7D6E4A60DEF54D3B401F18D94F104C3B7B1043A559C9705
Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4Q1b1Z1l63zJqDY for <hrpc@irtf.org>; Wed, 19 Apr 2023 09:23:14 +0000 (UTC)
Message-ID: <c87f0c5e-6d0d-452d-f113-cfc3f6c6c872@riseup.net>
Date: Wed, 19 Apr 2023 10:23:11 +0100
MIME-Version: 1.0
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> <uzngfhbmwm6zmkqh6533qyqdhghooxj2ili5bhkqixtdmm7ua4@xl5egznow756>
From: Sofía Celi <cherenkov@riseup.net>
In-Reply-To: <uzngfhbmwm6zmkqh6533qyqdhghooxj2ili5bhkqixtdmm7ua4@xl5egznow756>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/ToAoY2QRPkB-_Zs0pwGq7fbq1yc>
Subject: Re: [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: Wed, 19 Apr 2023 09:23:19 -0000

Hi, Andrew and all,
>> 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. 

Thank you.

> 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.

Several corrections here:

1. The discussion did not happen during any discussion of rechartering 
(Mallory showed a slide about what a new name for HPRC will look like 
and then moved to the current objectives of HRPC, which is the timestamp 
you refer to). We didn't have time at IETF116 to talk about in depth 
about recharting, so that context that you start with is not the correct 
one. The timestamp you point out to at 7.20 is about what the HPRC 
objectives are.
2. The UN didn't only invite people from HRPC but also from the IAB and 
IETF, and I think, in general, researchers. How they chose to invite 
people and in which framing is something that I guess only they know, 
and I will not like to speculate on this as I don't like to pretend to 
know what organizations and/or people intend or not ;)
> 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.  

I will like to see data about this. Again, I personally don't like 
speculation and, as this is a research group, I prefer to see 
quantifiable and representive data that backs up claims. I haven't heard 
this from any policy marker, in fact many of them don't seem to know 
what the IETF is (which is sad).

I do think that sometimes for people considered "new" to the IETF/IRTF, 
like myself, when speaking and being nervous, can confuse different 
acronyms (I tend, for example, to forget how to pronounce PEARG). I 
think that if we want a community that embraces new-comers and is open 
for them, we should help them instead of publicly stating if they made a 
mistake or not. We can also create more templates on chairs slides or 
agendas (which I'm happy to start some work on). I think a degree of 
that is needed or else less and less new people will be joining 
IRTF/IETF. But I do see that when speaking about HRPC is good to always 
frame it in the IRTF setting (which again we try hard to do).

Thank you,

-- 
Sofía Celi
@claucece
Cryptographic research and implementation at many places, specially Brave.
Chair of hprc at IRTF and anti-fraud at W3C.
Reach me out at: cherenkov@riseup.net
Website: https://sofiaceli.com/
3D0B D6E9 4D51 FBC2 CEF7  F004 C835 5EB9 42BF A1D6