Re: [hrpc] HRPC recharter

Eric Rescorla <ekr@rtfm.com> Thu, 13 April 2023 16:26 UTC

Return-Path: <ekr@rtfm.com>
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 8EEB8C14CE45 for <hrpc@ietfa.amsl.com>; Thu, 13 Apr 2023 09:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level:
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 (2048-bit key) header.d=rtfm-com.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 USjD0cC1ToGd for <hrpc@ietfa.amsl.com>; Thu, 13 Apr 2023 09:26:36 -0700 (PDT)
Received: from mail-yb1-xb32.google.com (mail-yb1-xb32.google.com [IPv6:2607:f8b0:4864:20::b32]) (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 C27FEC14CE2B for <hrpc@irtf.org>; Thu, 13 Apr 2023 09:26:36 -0700 (PDT)
Received: by mail-yb1-xb32.google.com with SMTP id q5so18839887ybk.7 for <hrpc@irtf.org>; Thu, 13 Apr 2023 09:26:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20221208.gappssmtp.com; s=20221208; t=1681403195; x=1683995195; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=W6gqm1udzUHEOOPiKbkE9gA7OjA/rwslrPPQpk1m7vs=; b=OsN3M96nyc1JIv7gOnZjWUmjHAPVzqHDxZhZoqFDkWQfu8mecrGGxY0fXJcSu+UnpS 2bzBo/J1N9np6GpZFWAVIoatrmsHHQ4CC+NYjB+Se+U3ZOwLxIzXI3YqkGMGZQ029IJp j8Q/uC7KFkxYEAEGeH8rxXm4C19sse8VhivvFUnSmZ+L47j1M99T6o7OaLzDJxh4kuGj zFZ7XrGJpgUgGwCXM0GJbXZ245ZhubmAVg9A30JozEMgyqwSYsTdmAlG1sZ/3cF3DkDK 245w69X0N96WmcTuQboqXd2kOXiIyd+gCrRLiCdYj1Kd5wk6fz63zD2hpJoO7qS0anT5 MueA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681403195; x=1683995195; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=W6gqm1udzUHEOOPiKbkE9gA7OjA/rwslrPPQpk1m7vs=; b=i1PFtLMiHiiFL6zgVh7fC2vai7a0ysYrcbHat0Ej9yjfReMiVVD6obVEeA9CC+NUTi 5fzQvGY7mmhAMFgO35439wOyxlPn9st5OmWaoS5/VsCVgKKIGg8JQVIPQXlSiT9ZwCeQ gaaPZNaAMrOUMTQ2qZYwBxFPG/tytve62pqJLmOorpvYSRSTckB/fozF11aOA2MIf/Oi C1keYdwqMlpQsbp2Hb6ZgmIDNQKWg95UKMxW3XoGhgpYMRPZLba2tIPSwcITRUww2p24 YLfdJYc4ip4PuhwrK3o4B5FtEEwE8vN7AOW0mW1Do8uWMdTRziq8qE93KTQd2sfc4h+6 YOAw==
X-Gm-Message-State: AAQBX9f7f/1LVN1GP6MY+izakNZSxkUAXA7pihTaqFwRpkI26ohVuw7k zZbWlLCGI5ZrDeQJAu+cy+HRXSlid6c0VjHP7hZ9L+IqpYk2L7VN
X-Google-Smtp-Source: AKy350Z4d8WwlWGuYUS4hUCKxhZW3zuZytPmnilIUlGJ1L+6UfXi0QM867GcwzJXpHfoq+rRsAfZ5OAOs66U3gPO6FI=
X-Received: by 2002:a25:8488:0:b0:b8f:5b11:6d6c with SMTP id v8-20020a258488000000b00b8f5b116d6cmr1477165ybk.1.1681403194662; Thu, 13 Apr 2023 09:26:34 -0700 (PDT)
MIME-Version: 1.0
References: <6ddd480d-76ed-a05e-066d-d740fee61441@cdt.org> <2e18e418-dfde-e23f-9639-1ca0ea6ad7f1@cdt.org> <dfe28959-32d7-fac4-e08e-d2bffa6f7848@lear.ch>
In-Reply-To: <dfe28959-32d7-fac4-e08e-d2bffa6f7848@lear.ch>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 13 Apr 2023 09:25:58 -0700
Message-ID: <CABcZeBOJEvr6K88=g9d7Q630M43ndWCA2=FOr78ZA+YLOdPZJQ@mail.gmail.com>
To: Eliot Lear <lear@lear.ch>
Cc: Mallory Knodel <mknodel@cdt.org>, Hrpc <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="00000000000024786e05f93a30ae"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/-Aaq2CE22CpW8KmxjwkkzbC6VVE>
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 16:26:41 -0000

Eliot,

I think this ties into the issue that Vittorio raised of what kind of
material the group is intended to produce.

If it's merely research results, then, yes, I agree they don't need
consensus. However, if it's to be taking
positions (and I think policy guidance is clearly a position) on behalf of
the group, then I think that clearly
needs consensus.

-Ekr


On Thu, Apr 13, 2023 at 12:04 AM Eliot Lear <lear@lear.ch> wrote:

> 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 listhrpc@irtf.orghttps://www.irtf.org/mailman/listinfo/hrpc
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc
>