Re: [hrpc] HRPC recharter

Eric Rescorla <ekr@rtfm.com> Mon, 26 December 2022 18:50 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 90E1EC1524C7 for <hrpc@ietfa.amsl.com>; Mon, 26 Dec 2022 10:50:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.893
X-Spam-Level:
X-Spam-Status: No, score=-6.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_HI=-5, 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.20210112.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 G43zMxEBqv8L for <hrpc@ietfa.amsl.com>; Mon, 26 Dec 2022 10:50:09 -0800 (PST)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (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 35F23C1522B6 for <hrpc@irtf.org>; Mon, 26 Dec 2022 10:50:09 -0800 (PST)
Received: by mail-pg1-x52a.google.com with SMTP id r18so7559364pgr.12 for <hrpc@irtf.org>; Mon, 26 Dec 2022 10:50:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=A2APsFlkW23WKqudhm5rMHIgS5Ans25Bt5AbxjKDHOI=; b=s/bgS86hJa4EDmjD0XUKPQo2T2W01Yq/Fcj1xVYPQopVJbIRRA0/exaXttoNlo0tfI o85LhzCYfvC4PMo4EC8VZdEWeSbHmczQXfBmb5dr5fhDyqWNXhXWaif2QuPmMojo4Rgp uSKwj+ylZ4Po9d+X/wRbk9EHFknHFiEBfMwViedarKuXjNlvylgxIuN3QQiKWhV4Zo/C QxNvw9QRYeFYNrOh5PUa843r+Sgy64z08+bl7v+slUytmL+1A1qJ7PF8lzy+ZdQPuEPy 8942AXmczPvxsAsD0KZa6KXOcZ8blbIQvmttNX8YjvfHYHbGXE1iV5YEIvl2BAQroaOy Omqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=A2APsFlkW23WKqudhm5rMHIgS5Ans25Bt5AbxjKDHOI=; b=VaD6uljEhbkea26Jxlgcn95c80kSDXerqUfhbcJ8uKqgQ0EvIk6c0su700XGGLbltR c01RExVQTHB05PyM95txNgsDvV4qFwZ2n2td2hwQ+EgyyosZUWVFSlQfFSB5wOg8yIsA DxfPa7+IwrjqmEEN3g1o2x9KtlYoH4T3iIQQZWjK3pEF+ct09IR9g4oUQV1woqNqq4/3 MVXSyV0H1if8K89pJjaTuNjKOB/d0SMQ6fKyQnOCg5ducyq5QZKpmBA7RxR54jeNEzzD iXz3QHzya9jMZnQKM+JsWaDg8aJ5agt8qXCuVL2pqk293KHAOI4pmm5/881ZN9O9zsrS gcZA==
X-Gm-Message-State: AFqh2kpDJQY4y9oC5TXwY6KtEFksOqonKbXRMG6a4KjMFevuLjmRO+nU L2ll4QTTYcaP1m8nCNuDJOgTnXa01yhPaoIt/pGFd03JzoTA7nUg
X-Google-Smtp-Source: AMrXdXvVOHdYW+4jFh2SHgAdzvU5SrbX26E8ohdB71b+wpfo1S2QoOvTBXBP/Bx0nR+ZWTmhStO6aJSr0J4CK8dLs44=
X-Received: by 2002:a63:fa13:0:b0:46b:27b0:c245 with SMTP id y19-20020a63fa13000000b0046b27b0c245mr831831pgh.611.1672080608307; Mon, 26 Dec 2022 10:50:08 -0800 (PST)
MIME-Version: 1.0
References: <6ddd480d-76ed-a05e-066d-d740fee61441@cdt.org>
In-Reply-To: <6ddd480d-76ed-a05e-066d-d740fee61441@cdt.org>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 26 Dec 2022 10:49:32 -0800
Message-ID: <CABcZeBO-kN+KmNcGuiAxv5ZidvuZW5A5yjB2mP_ZJCiF1qNLyg@mail.gmail.com>
To: Mallory Knodel <mknodel@cdt.org>
Cc: Hrpc <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="000000000000b1c76d05f0bf9a86"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/xME421Y4lRIlooyzacEcQ-XdjM8>
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: Mon, 26 Dec 2022 18:50:13 -0000

Mallory,

Thanks for sending this revision. WRT to the specific revisions you
propose, I tend to think that the change to "policy" is a good one,
but ISTM that rechartering is an opportunity to take a deeper look at
what HRPC should do. The current charter seems to contemplate a sort
of mix of functions and I think it would be useful to ask which of
those are working well.

As an outsider, when HRPC was first started, it seemed to have a real
BCP-72ish vibe in which there would be:

- Some common set of expectations for a what it would mean for a
  document to be analyzed from a human rights perspective (presumably
  documented in RFC 8280)

- Some process for external review for those factors (presumably done
  by HRPC)

So, for instance, the current charter has this bullet:

  * To propose guidelines to protect the Internet as a
    human-rights-enabling environment in future protocol development,
    in a manner similar to the work done for Privacy Considerations in
    RFC 6973.

And of course there is the the "Considerations" name of the RG
itself.

Whatever the intentions at the time, I think it's pretty clear that
this has not been the outcome: there haven't been that many of these
reviews and I don't think there's really broad consensus on how to
think about human rights in protocol design (see my separate review of
the 8280 revision [0]). More generally, at least from my perspective,
the work of HRPC has not had much impact on IETF operational practice
in terms of protocol design (even less so than there is around Privacy
Considerations).

I see that the proposed charter revises this bullet somewhat to remove
the comparison to 6973, but I think it would be good to be clearer in
the charter that the intent for the HRPC is not to be some
human-rights flavored version of secdir or opsdir. In particular, if
guidelines for how to design protocols so that they protect human
rights are to have any normative force, they need to come out of the
IETF, not the IRTF. And if the intent is to provide something
informative, then I think what's needed is something much more like an
analysis of problems and a catalog of techniques than guidelines. This
is, for instance, what PEARG does.


The two other objectives have a more public awareness type flavor:

 * To expose the relations between protocols and values, with a focus
   on the human rights framework.
 * To increase the awareness in both the policy 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.

I don't track the work in these areas as closely, so I'm less able
to say whether that work is going well or not. For what it's worth,
I don't typically refer to the artifacts of this group as the main
sources for the human rights impacts of protocols, but perhaps
others have a different experience.

In any case, I think rather than just spinning a new charter, it
would be helpful to take a bigger picture look at what this RG
should be trying to accomplish.

-Ekr


[0] https://mailarchive.ietf.org/arch/msg/hrpc/I2mP4Wehcj3UTSGqh4uwH6QoA4Y/

On Thu, Dec 22, 2022 at 9:30 AM Mallory Knodel <mknodel@cdt.org> 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
>