Re: [hrpc] HRPC recharter

Mallory Knodel <mknodel@cdt.org> Wed, 04 January 2023 19:46 UTC

Return-Path: <mknodel@cdt.org>
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 370E8C1522AA for <hrpc@ietfa.amsl.com>; Wed, 4 Jan 2023 11:46:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=cdt.org
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 gOFxnsbUK2pQ for <hrpc@ietfa.amsl.com>; Wed, 4 Jan 2023 11:46:43 -0800 (PST)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 CE28CC14F741 for <hrpc@irtf.org>; Wed, 4 Jan 2023 11:46:43 -0800 (PST)
Received: by mail-qt1-x82e.google.com with SMTP id j16so28116145qtv.4 for <hrpc@irtf.org>; Wed, 04 Jan 2023 11:46:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=content-transfer-encoding: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=ZWtPQS7MNwkq3OldnqOSgRqevnN3nResjHhd/fkp7RQ=; b=On03GJJUwFp5ol8JoIgO85h6chknluVmntdF2E7mwDjehsCuhCWhN1C4RLGV34CSjp MmWalYeBhK8nU/Bs/+oxBW2iBP/iQv20xMvUOv7dwVAprmt+9rKVJl9USV0PDPvp7WK7 L4jNC1cjEzejkqx1vG23XDPHQlfOIUyZUk0bM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding: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=ZWtPQS7MNwkq3OldnqOSgRqevnN3nResjHhd/fkp7RQ=; b=oKETfuvJDRctf9oGWQIt0RK21sYVvmKQyJ+ccBaSt3gls+oOtD4npcaszz/Kiv5Hk+ l/QkeIlXEf90pJfnk26EFXVftslco64MwPZZFjp2OqnDlVKAzoa8XCeuEujFunMhmHX0 2A9xivkbeXjLPfZ2obQPMUsWg/cCsQUix3+OrLlgRLMnoX9PNLExozoumMr2UuXyW7OF 1mn2oLTIX7ivJ+AY71DV0hyhOBCwZ6AlkFSMU5JHQzNtPXFWqphxtgRE9FNdZwkr9Rsp Qgw07EhT5LNMLPIamYGgiuuxjtEZTJYCFv9GL4DxLpoliC836qBtWURHj3+Qn/O8Q+R8 SJfA==
X-Gm-Message-State: AFqh2koSimAOn3E31ZW25tS/4pyg8WMf1hFsNkYGr6ufVWopaq+b6i8w RMQhud5+mganYw7iARWEq0TS54e3Z3yO+OQd
X-Google-Smtp-Source: AMrXdXtfy/nnYj7r8XDzoGx0xQUz1wqYruCa7lVCcH23Si8lKfyIZlnjMbYCTLwxVjzacCU6oKiU1w==
X-Received: by 2002:a05:622a:1e1b:b0:3a7:f9a3:b86b with SMTP id br27-20020a05622a1e1b00b003a7f9a3b86bmr80971516qtb.13.1672861602135; Wed, 04 Jan 2023 11:46:42 -0800 (PST)
Received: from [10.0.3.199] ([50.239.129.122]) by smtp.gmail.com with ESMTPSA id g4-20020ac87744000000b003a7f597dc60sm20681196qtu.72.2023.01.04.11.46.41 for <hrpc@irtf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 04 Jan 2023 11:46:41 -0800 (PST)
Message-ID: <bb3c3a96-c1cb-8b9d-6b9d-efd814ff385f@cdt.org>
Date: Wed, 04 Jan 2023 14:46:40 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:106.0) Gecko/20100101 Thunderbird/106.0
Content-Language: en-US
To: hrpc@irtf.org
References: <6ddd480d-76ed-a05e-066d-d740fee61441@cdt.org> <77659609-7e3e-fb5d-0ded-ce0f205204b6@nielstenoever.net> <CANYRo8h55Ki_2LK4p3DRHtUCiNVw+eckRY_jsJqv-2kZ2eTn4g@mail.gmail.com> <5425efa7-2424-27a1-2102-07d813f968a9@cdt.org> <acaf99ef-eb25-82d4-c53a-58cf3b55244b@briarproject.org> <984568805.3021391.1672854857598@mail.yahoo.com> <97d2dcfb-ff21-db06-27f8-24058bf31802@nomountain.net>
From: Mallory Knodel <mknodel@cdt.org>
In-Reply-To: <97d2dcfb-ff21-db06-27f8-24058bf31802@nomountain.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/C-UEcOVzIOXpq6My-Eb0rgNbcls>
Subject: Re: [hrpc] 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, 04 Jan 2023 19:46:48 -0000

Hi,

On 1/4/23 2:31 PM, Melinda Shore wrote:
> "
>    * To increase the awareness in both the human rights community and
>      the technical community on the importance of the technical workings
>      of the Internet and its impact on human rights.
> "
> (https://datatracker.ietf.org/doc/charter-irtf-hrpc/)
>
> So I think part of the issue with this discussion is lack of agreement
> on who the "audience" is, and whether "audience" is the right thing to
> be thinking about at all.  I think it's difficult to balance a research
> focus with the sort of advocacy activities being argued here, especially
> in the absence of broad consensus about policy questions, difficult
> tradeoffs, etc., but maybe one of the things that can come out of this
> rechartering discussion is a better sense of how folks want to balance
> these somewhat incompatible interests. 

I just wanted to comment that while the re-charter is broadening the 
scope from

human rights -> human rights and policy

The re-charter text does *not* further broaden the scope of our 
activities beyond research into advocacy.

Perhaps what Melinda is saying is that all along we have had an 
underlying tension between advocacy and research, and if so I would 
admit that as a self-described advocate at an advocacy organisation I am 
much less certain of particular outcomes in the IETF than I am in policy 
spaces. Speaking from my own experience, I do genuinely approach the 
research questions we raise in HRPC with curiosity and am deeply tuned 
into unresolved questions that we can build consensus around-- though as 
most will recall I do not believe the research outcomes of this RG need 
to attain consensus. That is all to say that HRPC does not feel to me 
that it is a vehicle for advocacy, or that it is trying, or trying and 
failing, to balance research with advocacy goals.

If there's a way to reflect that in the charter, I think that we should. 
But I am not sure that this dynamic is really a function of the charter 
language more than it is a reflection on the folks and their expertise 
who have come to the RG.

-Mallory

-- 
Mallory Knodel
CTO, Center for Democracy and Technology
gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780