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

Melinda Shore <melinda.shore@nomountain.net> Tue, 18 April 2023 16:07 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 06294C14CEFC for <hrpc@ietfa.amsl.com>; Tue, 18 Apr 2023 09:07:04 -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_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 nuwmIj2zwf4O for <hrpc@ietfa.amsl.com>; Tue, 18 Apr 2023 09:06:59 -0700 (PDT)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (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 A3CAAC14CF09 for <hrpc@irtf.org>; Tue, 18 Apr 2023 09:06:59 -0700 (PDT)
Received: by mail-pf1-x42f.google.com with SMTP id d2e1a72fcca58-63b8b19901fso1452920b3a.3 for <hrpc@irtf.org>; Tue, 18 Apr 2023 09:06:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomountain-net.20221208.gappssmtp.com; s=20221208; t=1681834018; x=1684426018; 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=t+KSkQAQpKloJcksgALi5wyT0Jl06motS73zabORoUk=; b=y22YlIaamd0yQJnCNINvPAWQoKr9KmZd3C0cpBXKBSDVWf/tK20wxHMntgcrimGtMn SQIShy8V36N0xYeBP/oJKBMoiol9GsugIy+Rck7D0pFixXOJkxGY+zCwijtw9Mg3RsiE WqfSJxX2RVVbe4h0Y9B1lE97Pu7HdwRto0T4tAWd2CswdTPtw/zGg2D7m8abaOx4555y hmmTJXf6FjpDFGbhfl6yTgIDf/NDA0ef6Sy+7NyznT6q1nhy7jy49FvnG0pJTAvfjhay BzXCaSeFwtm0XCbB2fDcSE/AVjOoKl1fcSIi6wFCeBswirwV0wqqe13lQl1JVtUHSA03 33hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681834018; x=1684426018; 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=t+KSkQAQpKloJcksgALi5wyT0Jl06motS73zabORoUk=; b=UQMV+ff/HUHeGuhClprHHWO4dWE+VMm3scfqZqxbmAvXfJsdWHz/F+O2/WryHZXRYk VF5/2x5oftkDT/hYTsmFDRsHntE3REUnG+k+8LvwhAXAABt94L5Dl9tTTD+375T5OMG3 BbLgdDodc3gH1qQlm4RuxZwhu8bpP0ysBCca0G32tMWfM2kugSny3C/mmDVVh6EpgOgA IdcqAcfLTyNsZ3/Kl/bOMXLsTntjGO1wGbFTkk8hIwSaD/KVxypA4/l50JSRbOkmCSpp xyA7gIYT7YnK6HMm6U6eMNP+fjF6T97Y7gXCnGFFDMRwH7VzX/ryHadgs5KwMT6291KX 6yCg==
X-Gm-Message-State: AAQBX9cSZqzmpH3BP+TA3bVy2DnEoEECf1JLbZruPvjbu8YZAn0KUFY8 wuz/o1MYVADZpjlLw26ouc4zCm5VaW+sS33ZKQ==
X-Google-Smtp-Source: AKy350bMSsm0fwa4ns0ZShZnb6UvUcRChoAcnQEB24fi7esKP3MZQdSoo6ELEdEQv5uqN8oLHJGNNA==
X-Received: by 2002:a05:6a00:2388:b0:63b:5496:7b1a with SMTP id f8-20020a056a00238800b0063b54967b1amr375995pfc.6.1681834018513; Tue, 18 Apr 2023 09:06:58 -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 n25-20020aa78a59000000b006396be36457sm9535793pfa.111.2023.04.18.09.06.57 for <hrpc@irtf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 18 Apr 2023 09:06:57 -0700 (PDT)
Message-ID: <04a67d95-0c67-84c0-b589-9f5907d74ca7@nomountain.net>
Date: Tue, 18 Apr 2023 08:06:55 -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>
From: Melinda Shore <melinda.shore@nomountain.net>
In-Reply-To: <6369b6fc-8e15-babb-c1e3-1405213b051c@nielstenoever.net>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------96ZVFIyRizOwA5oakwssMP1N"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/d_x4-EDa6qEhHqOEbJaxpUKro30>
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:07:04 -0000

On 4/18/23 7:47 AM, Niels ten Oever wrote:
> How can you then attribute the misunderstanding to the co-chair or the 
> proposed charter change ?

I don't see that it does, but it also pretty clearly doesn't help.

People both inside and outside the various I*TF organizations
misunderstand the distinctions between the IETF and IRTF.  In
general that's not actually a problem in practice, but it may
be in the HRPC case.  If you take, for example, CFRG, it is
very commonly misunderstood in the cryptographic community to
be an IETF activity (CFRG does produce standards).  But, that
doesn't really affect any other activities or, arguably, CFRG
itself.  However, to the extent that HRPC is misunderstood to
be influencing standards production in the IETF, that can
be (and has been) a problem, in terms of friction with IETF
working groups and the incorrect assumptions being made
about human rights activities in the IETF by governments and
policy makers.  So, I'd argue that the lack of understanding
about the differences is not inherently much of a problem
generally but that it is a problem in the specific case of
HRPC.

Melinda

-- 
Melinda Shore
melinda.shore@nomountain.net

Software longa, hardware brevis