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

Melinda Shore <melinda.shore@nomountain.net> Tue, 18 April 2023 16:41 UTC

Return-Path: <melinda.shore@nomountain.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 C6087C16B5CF for <hrpc@ietfa.amsl.com>; Tue, 18 Apr 2023 09:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nomountain-net.20221208.gappssmtp.com
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 bT_2RH8K8bJQ for <hrpc@ietfa.amsl.com>; Tue, 18 Apr 2023 09:41:26 -0700 (PDT)
Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 6F92AC151B30 for <hrpc@irtf.org>; Tue, 18 Apr 2023 09:41:26 -0700 (PDT)
Received: by mail-pj1-x1034.google.com with SMTP id 98e67ed59e1d1-2474e09fdcfso1628076a91.0 for <hrpc@irtf.org>; Tue, 18 Apr 2023 09:41:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomountain-net.20221208.gappssmtp.com; s=20221208; t=1681836086; x=1684428086; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=T61SOdlZYCn+bvOKTS8HfHyNIT4pXuWDd8Vs3mE/u3c=; b=KKyeSL0dgtDrISryVn4LZ5giepAnWB6rlTE48unqSLOJp1l8nrTf9TA7046vFFVaeG ZlPwCA/u/uU+1lBb17KYV9nei+n4XEkYDUvRtrPmMWNOiVQj7d2aYhRIF+IdeOVMzfJA OshEyWMYtLFde56RyuUqMO6Vxs+ub+NPy0RczXDkJ8/wT4BPfWpWqTaZWHzDwBq8VmAn NalkPgr6CPlZ8e6m8aMr0r02jBGNs1en32Agc06dWOK6wHtFfmhNZUiuPJKK8i4N3RD+ 6ltCVcEy1fLL7umeGDviKcWiwQABGUffbl+DKfXowq7IlBJmixsyITfKhMiyisJMrSF/ rs4A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681836086; x=1684428086; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=T61SOdlZYCn+bvOKTS8HfHyNIT4pXuWDd8Vs3mE/u3c=; b=YziRk6Ldb0Lm1vq23twjBFhS7c6RgoInvXUsx4G8AX/OFGca/SZXYc9uvjNiniv6RK tr/PdsGljVWSaKhniEHGzJ40ZRw1vRBG7xdBg8M/DvXSIakJGIJ36wXd8hodUfcRP9lx czHt3tF/ZqhUrFsttncd7Ln687KstXwEpd9z5BOMGSAm13ZMsw/34xVkA3RghC9FBK+m ImBVXL53C3ioKP/qxfTSPKocxW4qEztxHVjO709CukEIY0z08VZGllQ01LUlQtoNUSAW g7O2vnJCnXJ3wJo/GUSa5ShVP22RcPpWthbU+D/mAJNpAfEFl08+aEhh5+r2rhEi1UET CBbg==
X-Gm-Message-State: AAQBX9erWRbaOXv/e0yTTpgnr5GdcTh2OjxUVnbcFwxZ0Zpy+0WpfY0k o4wH/9j5V9lAGyeM76BECcRVgNM7kC6/p0S5Uw==
X-Google-Smtp-Source: AKy350bKLNfE0e55Ff2g809GfVcUdZx408sLg6qslBsrT2z2l14Avm75ELENq/F6rt6GZehsKx9QtQ==
X-Received: by 2002:a17:902:e848:b0:1a6:9289:6b with SMTP id t8-20020a170902e84800b001a69289006bmr3200221plg.30.1681836085621; Tue, 18 Apr 2023 09:41:25 -0700 (PDT)
Received: from [192.168.1.111] (63-140-69-230-radius.dynamic.acsalaska.net. [63.140.69.230]) by smtp.gmail.com with ESMTPSA id ji17-20020a170903325100b001a522cd8545sm9826181plb.130.2023.04.18.09.41.24 for <hrpc@irtf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 18 Apr 2023 09:41:24 -0700 (PDT)
Message-ID: <8adb28c1-3016-93eb-f43b-2abb9b8529d4@nomountain.net>
Date: Tue, 18 Apr 2023 08:41:21 -0800
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: hrpc@irtf.org
References: <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> <mdhlxm2ebnrmfq2vkxvyhzqttrzwxvhwqbwhxuejlkleft5hml@b42oy7hiwydh> <6369b6fc-8e15-babb-c1e3-1405213b051c@nielstenoever.net> <04a67d95-0c67-84c0-b589-9f5907d74ca7@nomountain.net> <f07515f3-c85e-1720-48d8-c999e21738e5@nielstenoever.net>
From: Melinda Shore <melinda.shore@nomountain.net>
In-Reply-To: <f07515f3-c85e-1720-48d8-c999e21738e5@nielstenoever.net>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------J9sXOHALnZ0IFOfCyaW6PXHl"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/Gnt4tvpANvsbGoQ8FAxLqFSBJLw>
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: Tue, 18 Apr 2023 16:41:30 -0000

On 4/18/23 8:16 AM, Niels ten Oever wrote:
> Why could it not help elucidate the difference?

By not elucidating the difference?  That said, I'm not sure it
can for people outside the process, but I do think that it
could be a lot clearer with respect to limiting RG scope.

> I don't think this was never claimed by anyone in hrpc. Why could work 
> in hrpc not actively work to explain this difference and actually 
> address the misconception and help explain the work by the IRTF and IETF ?

I think there's tremendous value in research identifying and
explaining the nexus between internet protocol standards and human
rights, and developing an understanding of how IETF standards
might help or harm those rights.  That is not the same thing
as attempting to influence the development of specific documents
in specific IETF working groups, which is something that was
a problem early in the RG's existence and which is still not
fully understood (see the discussion in the "When are HRPCs
normative in an IETF protocol?" thread as a relatively recent
example, and the existence of a human rights review team as
an early example).

Melinda

-- 
Melinda Shore
melinda.shore@nomountain.net

Software longa, hardware brevis