Re: [hrpc] HRPC recharter

Eliot Lear <lear@lear.ch> Thu, 13 April 2023 07:04 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 2655FC15152C for <hrpc@ietfa.amsl.com>; Thu, 13 Apr 2023 00:04:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, 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 xhb0zh7MbphO for <hrpc@ietfa.amsl.com>; Thu, 13 Apr 2023 00:04:29 -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 B6903C14CE2B for <hrpc@irtf.org>; Thu, 13 Apr 2023 00:04:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1681369457; bh=fX96y+v01aMb+DkesoHk055wOPpzBEkzhSQBx5JVA30=; h=Date:To:References:From:Subject:In-Reply-To:From; b=amEwEjNk5lT1+GE2vjiZRCP8vNQ2xtxf999s5VmQuoGZ/4Zcd/qE6uDHOD5xi4o9h 2SiFAf7p94NcPT1MpDAthSqeKtcvprEGXrR1rIYMW1fsfbxv5I2YFdlC3Q0nrYe0XY xurozM7kuj8jgVQKOl40uq+Xvd5apY11sgyzHbw8=
Received: from [IPV6:2001:420:c0c0:1011::4] ([IPv6:2001:420:c0c0:1011:0:0:0:4]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-22ubuntu3) with ESMTPSA id 33D74Gbu460998 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Thu, 13 Apr 2023 09:04:17 +0200
Content-Type: multipart/alternative; boundary="------------JYTb2qEKDtv3SOqUVk4ZWnTe"
Message-ID: <dfe28959-32d7-fac4-e08e-d2bffa6f7848@lear.ch>
Date: Thu, 13 Apr 2023 09:04:15 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.9.1
Content-Language: en-US
To: Mallory Knodel <mknodel@cdt.org>, Hrpc <hrpc@irtf.org>
References: <6ddd480d-76ed-a05e-066d-d740fee61441@cdt.org> <2e18e418-dfde-e23f-9639-1ca0ea6ad7f1@cdt.org>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <2e18e418-dfde-e23f-9639-1ca0ea6ad7f1@cdt.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/MLQycHcde4LkJoFxrOYZrqAvCC8>
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: Thu, 13 Apr 2023 07:04:34 -0000

Hi Mallory,

I've reviewed the changes to the charter, and the discussion on this 
list.  Rather than me attempt to further wordsmith the charter (I do 
have a pet peeve or two)*, at a high level, what strikes me as important 
is that there are researchers who would engage in the group with such a 
charter.  If they would find it helpful to their research, and the IAB 
thinks it will inform the IETF, perhaps that's good enough.  But is that 
engagement there?

Also, I would suggest that the publication policy of this group 
explicitly change, and be noted in the charter.  I don't believe rough 
consensus does this group or researchers or the IETF a service.  IMHO 
the bar should be accuracy and correctness.  That is- it should be fine 
to hold a controversial opinion in an RFC, but not fine to assert facts 
not in evidence.  A change in such policy also allows different people 
to explore the tussle between rights that both Eric and I have pointed 
out at different times.

Eliot

* I did enjoy reading a bit about the difference between "relations" and 
"relationships".

On 11.04.23 18:46, Mallory Knodel wrote:
>
> Hi all,
>
> Thanks very much for everyone's comments on the list and in the recent 
> meetings. We have also had some productive discussion with Colin and 
> the IAB to get this right from a whole-community perspective.
>
> Below is a paste of the current proposed text. And here is a link to 
> the diff:
>
> https://github.com/IRTF-HRPC/IRTF-HRPC/compare/01ba8fcd3b2648ac9d4d5ee89d5a56f124d2481c...fc1e36d1b64c4d31d08d34f82ae25e63f9abb68f
>
> Please send comments, suggestions, notes of approval, etc.
>
> Best,
>
> -Mallory
>
> ===
>
> # Human Rights and Policy Considerations
>
> This research group aims to explore the relationship between Internet architecture and human rights for a wide audience. It aims to inform the technical community of how the design of protocols impacts, and can be informed by, policies that serve the public interest and protect human rights. It also aims to inform policy makers and civil society groups of technical constraints that might impact policy choices. The role of the research group is to promote understanding of the issues so those making decisions can do so in an informed manner.
>
> ## Background
>
> The research group takes as its starting point the problem statement that human-rights-enabling characteristics of the Internet might be degraded if they are not properly defined, described and sufficiently taken into account in protocol and standarization development. Not protecting these characteristics could result in (partial) loss of functionality and connectivity.
>
> Moreover it is widely accepted that technical design decisions about the Internet are not value neutral and can have lasting impacts on public policy and individual human rights.
>
> The Internet aims to be the global network of networks that provides unfettered connectivity to all users at all times and for any content. Open, secure and reliable connectivity is essential for rights such as freedom of expression and freedom of association. Since the Internet’s objective of connectivity intersects with human rights, its architectural design considerations converge with the human rights framework.
>
> ## Research question
>
> How are human rights and public interest policy considered in the development of the Internet?
>
> 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, as defined in the Universal Declaration of Human Rights (UDHR) [1] and the International Covenant on Civil and Political Rights (ICCPR) [2].
>
> Furthermore HRPC researches how protocols can influence policy concerns that intersect with human rights, and vice versa. This research group is a discursive resource for the community to support the development process in recognizing these potential public policy impacts as well assist to address those impacts adequately. The Global Data Protection Regulation [3], principles of necessity and proportionality of surveillance [4], are examples of policy developments that have led to rich areas of work for the IETF through the Privacy Enhancements and Assessments research group (PEARG) and more such regulatory actions are expected as the digital age progresses.
>
> HRPC collaborates with other research groups: PEARG and privacy as a human right, Global Access to the Internet for All on second-generation equity rights, and with RASPRG on analysing how discussion of core architectural principles make value judgements.
>
> ## Objectives
>
>   * To expose the relations between protocols and values, with a focus on the human rights framework, such as the policy implications of technology choices and the technical implications of policy choices.
>   * To suggest guidelines to protect the Internet as a human-rights-enabling environment and a global public good in future protocol development.
>   * 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 and the public interest.
> * To create a place for discussions and analysis on the relationship between protocol development, and their human rights and policy implications by, among other mechanisms, serving as a bridge between the human rights community and the protocols-development one.
>
> ## Outputs
>
> The research group plans on using a variety of research methods to create different outputs including, but not limited to:
>
>   * Internet drafts, some of which may be put in IRTF RFC stream. These will concern progress of the project, methodology, and will define any possible protocol considerations.
>   * Research papers concerning both policy and academic topics which can include in-depth analysis, discussions and review of the values embedded in the Internet architecture, for publication elsewhere.
>   * Protocol analysis. Data analysis and visualization of (existing) protocols to research their concrete impact on human rights and the public interest.
>
> HRPC research group does not set policy for the IETF.
>
> ## Membership
>
> Membership is open to any interested parties who intend to remain current with the published documents and mailing list issues.
>
> [1]http://www.un.org/en/documents/udhr
>
> [2]http://www.ohchr.org/EN/ProfessionalInterest/Pages/CCPR.aspx
>
> [3]https://gdpr-info.eu
>
> [4]https://necessaryandproportionate.org/principles
>
> ===
> On 12/22/22 12:30 PM, Mallory Knodel wrote:
>> Dear RG,
>>
>> Hope everyone is well.
>>
>> At the 115 meeting HRPC was reviewed by the IAB [0], notes of which 
>> are forthcoming from the IAB.
>>
>> Partially as a result, though this activity predates the review 
>> itself, Sofia and I have been reviewing the HRPC charter. In 
>> particular we are keen to expand HRPC slightly, though arguably our 
>> area of work will remain the same (more on that later), to explicitly 
>> welcome policy discussions.
>>
>> The recharter text is available in GitHub [1] where you can view a 
>> diff [2]. It is also in a plaintext format with more visual 
>> indications of where the changes have been made [3].
>>
>> My view on the proposed change to include "policy" as a replacement 
>> for "protocol" in the name and charter text have been shaped by both 
>> of the past chairs of HRPC and Colin's feedback, which is that the 
>> human rights framework can apply to virtually any policy discussion 
>> and therefore HRPC has all along according to its charter had a 
>> mandate to talk about these issues. However I do think that the 
>> slight rephrasing in places gives us necessary updates that reflect 
>> the current political moment as well as learning from past lessons 
>> since the group was chartered the first time. Additionally I think 
>> there is value in the group name and its charter text being written 
>> so as to explicitly attract researchers and research that discuss 
>> policy, as a "place to land" in the IETF/IRTF.
>>
>> We welcome any comments on the proposed changes.
>>
>> Happy new year and best wishes to everyone,
>>
>> -Chairs, Mallory & Sofia
>>
>> [0] https://www.iab.org/wiki/index.php/RG_Reviews
>>
>> [1] https://github.com/IRTF-HRPC/IRTF-HRPC/blob/main/hrpccharter.md
>>
>> [2] 
>> https://github.com/IRTF-HRPC/IRTF-HRPC/commit/1a029b31ab3521e8da1490924c94397a99497d19
>>
>> [3] https://pad.riseup.net/p/Qgq2TJuWLbFSY1Jrcxgm
>>
>>
> -- 
> Mallory Knodel
> CTO, Center for Democracy and Technology
> gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc