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

Eliot Lear <lear@lear.ch> Wed, 19 April 2023 10:02 UTC

Return-Path: <lear@lear.ch>
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 D8945C14CE22 for <hrpc@ietfa.amsl.com>; Wed, 19 Apr 2023 03:02:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.087
X-Spam-Level:
X-Spam-Status: No, score=-7.087 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, 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=lear.ch
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 wDXGL-oBLdu7 for <hrpc@ietfa.amsl.com>; Wed, 19 Apr 2023 03:02:01 -0700 (PDT)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [IPv6:2a00:bd80:aa::2]) (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 500EBC14CF15 for <hrpc@irtf.org>; Wed, 19 Apr 2023 03:02:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1681898517; bh=vzYGEgAvOm2xu/mp5ODh4goDtZlEMnz0U7JTMpPBPvs=; h=Date:To:References:From:Subject:In-Reply-To:From; b=biBsakh1XFq1RWb9dmkMgQJsbakWky6nRw0eNevhfNhbXGCQLMkiTHygen00DeqYN 9SrpKiMPcXTFL1vG3w2hHAJwnBSHVxGO1Ql8KSVSoJBGW6X3u4tcPfQNVN9Lr6vbEz E8maAG49RhMpZKnT2gR0OLEbeHZnIOZ5XKvs0/Dc=
Received: from [192.168.0.99] (77-58-144-232.dclient.hispeed.ch [77.58.144.232]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-22ubuntu3) with ESMTPSA id 33JA1ufp695898 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Wed, 19 Apr 2023 12:01:56 +0200
Message-ID: <d2263d8d-5a6e-a82f-a9be-1339890168b4@lear.ch>
Date: Wed, 19 Apr 2023 12:01:56 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.10.0
Content-Language: en-US
To: Niels ten Oever <mail@nielstenoever.net>, 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> <bcc258f8-1f6c-3bf0-3ade-d6c8cc91c025@nielstenoever.net> <6c5ce62f-7645-3efd-f61c-c687983f38b5@lear.ch> <bcb10e98-accd-9670-20c7-71408d53daff@nielstenoever.net>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <bcb10e98-accd-9670-20c7-71408d53daff@nielstenoever.net>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------gukPDmw0mESrnTgl1FRfJBtp"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/zvQELmUnM6_e62U3oA8xgMAbCI0>
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 10:02:06 -0000

Top posting:

My primary point was that most of us are not adroit at communicating 
with policy makers, and so we have to make it easier to avoid that.  I 
accept Andrew's experience that there has been confusion.

Let's accept that there is a tussle going on between the importance of 
doing HR / policy research.

So..... what could be done?  This is just a suggestion on how to move 
the discussion forward.  Take it, leave it, or modify it as you or 
others see fit.

This seems to call for care in all assertions that are made.  In fact 
almost no assertions need be made in the charter.  The focus should be 
on research and questions that *perhaps* have policy implications.

There are many cases where the charter text could be evolved along those 
lines.  For example:

OLD:

> The Human Rights and Policy Considerations Research Group is chartered 
> to research of protocol development that is responsible towards and 
> mindful of the human rights of others and whether standards and 
> protocols can enable, strengthen or threaten human rights [...]

Presuming conflict among rights, how about:

> The Human Rights and Policy Considerations Research Group is chartered 
> to research the human rights implications of protocol 
> development.[1,2]  Which rights are strengthened by design decisions 
> and which are weakened?  Which design choices require external policy 
> or value systems/ethical models to facilitate those decisions?
>
Note the questions.  I am sure there are more, and the best are the ones 
that I haven't considered.

Drop the next paragraph and then ask the question in turn;

> What are those external or ethical models and how do they apply to 
> standards development?

Going this route obviates the need for "policy" to be in the title, btw, 
but allows for some policy discussion.

Anyway, that's my attempt at a Solomonesque split.

Eliot


On 18.04.23 18:07, Niels ten Oever wrote:
> Hi Eliot,
>
> On 18-04-2023 17:53, Eliot Lear wrote:
>> Hi Niels,
>>
>> On 18.04.23 17:10, Niels ten Oever wrote:
>>> Dear Andrew,
>>>
>>> You argue that there (still) is a lack of understanding among 
>>> governments about the work of the IETF, isn't that exactly 
>>> illustrating why an RG charter change is needed?
>>
>> I don't think that follows.  An RG charter change cannot solve 
>> confusion between the IETF and IRTF, nor can it commit the IETF to 
>> anything> 
>
> I fully agree! But work in an RG can help elucidate it.
>
>>>
>>> Apparently the work of other organizations to increase understanding 
>>> about the workings of the IETF haven't sufficiently succeeded.
>>
>> I am not sure that the IETF inner workings should need to be visible 
>> to those who don't wish to involve themselves, and I think Andrew's 
>> point is that making the distinction is hopeless *anyway*. And this 
>> is where it gets tricky.  I wouldn't fault anyone in the least for 
>> eliding the IETF and IRTF when talking to policy makers.  Our 
>> structure and “branding” simply doesn't make that easy for others to 
>> comprehend.
>>
>> But that means we have to be quite precise as to what We (for our 
>> aggregated definition of "We") say we are doing.  And that isn't easy.
>>
>
> I fully agree - and that is why I think it is exactly useful to have 
> an RG doing this work and helping explain it - because this is clearly 
> not sufficiently communicated through existing channels.
>
> Best,
>
> Niels
>
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc