Re: [hrpc] HRPC recharter

Adrian Gropper <agropper@healthurl.com> Thu, 05 January 2023 23:29 UTC

Return-Path: <agropper@gmail.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 0B320C151551 for <hrpc@ietfa.amsl.com>; Thu, 5 Jan 2023 15:29:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.396
X-Spam-Level:
X-Spam-Status: No, score=-6.396 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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
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 XqqoDLYo8fDM for <hrpc@ietfa.amsl.com>; Thu, 5 Jan 2023 15:29:52 -0800 (PST)
Received: from mail-yw1-f175.google.com (mail-yw1-f175.google.com [209.85.128.175]) (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 3C260C151550 for <hrpc@irtf.org>; Thu, 5 Jan 2023 15:29:52 -0800 (PST)
Received: by mail-yw1-f175.google.com with SMTP id 00721157ae682-4a2f8ad29d5so960537b3.8 for <hrpc@irtf.org>; Thu, 05 Jan 2023 15:29:52 -0800 (PST)
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=oUTDNk9r6+ES/EFlKpCGYMMTUuCLKEmUmFFf5mx2cmc=; b=ivU2izGHhl0BU+Ka1V5zuEcaBHAfWa/K0YaDtl95cMwQDDBZm/HbOGDa9Dzl0BU2tt 07GM1W3QSnR3QHqIVboC7DT5K/9HXvrcvmvzWzssUIG4I+inNEptc9ZHmv/48uKuVDuz FLOaDPLat4QJl1Qsy7fz8cEyCbrlyXinlcKgaBibcrCIjhD8Ib+3bE60E9dcUsOOHio3 DsoSKLKSsuYq/zhKqyfT5lb/R+djgsKgcxtmlcYuzzVY2gjZeqCs2EGIKAr5IULq7vG2 Hlm64raxuJS9OLCNhBzsczj1DL7GxP9QLP7/CS/Ckrvi+kfjwVQpZJmf2zLxDyBQJku1 lNSg==
X-Gm-Message-State: AFqh2kq/rwg2+6t9b+xryCzMnaUnoHus+MXqsRCkV1dd6DbcPBH17A8K vKhyCJLPTUdAg5MogYJZiqOUC4Y3NONMffygqEA=
X-Google-Smtp-Source: AMrXdXtyy5XTcSOlaw6cOofCr33obU7A8sLCOqvgmhcL5JMPaDvLl5FRs48I+k2RA+/+YgV3u4V5yCAI0BYbmob/RwU=
X-Received: by 2002:a0d:d913:0:b0:48a:1474:d152 with SMTP id b19-20020a0dd913000000b0048a1474d152mr3112978ywe.174.1672961391163; Thu, 05 Jan 2023 15:29:51 -0800 (PST)
MIME-Version: 1.0
References: <6ddd480d-76ed-a05e-066d-d740fee61441@cdt.org> <CABcZeBO-kN+KmNcGuiAxv5ZidvuZW5A5yjB2mP_ZJCiF1qNLyg@mail.gmail.com> <f727a6c8-7f1e-0db8-46d0-36248b921b79@cdt.org> <CABcZeBPuGUXcAo6z+uSCn=99ct7ALxOP8aQHYX+ncViLitMciw@mail.gmail.com> <ff338456-b2b5-0eec-f18f-be81ef1afe99@cdt.org> <CABcZeBO_9tjxDTurFr-uaN6OAPR1=Qo7aJNNHMprLPBUyrsAEg@mail.gmail.com> <5e1edb5c-f1a4-390a-4111-fbcdd58531f3@cs.tcd.ie>
In-Reply-To: <5e1edb5c-f1a4-390a-4111-fbcdd58531f3@cs.tcd.ie>
From: Adrian Gropper <agropper@healthurl.com>
Date: Thu, 05 Jan 2023 18:29:39 -0500
Message-ID: <CANYRo8hVM13da4oeGMmd=v6US71a3APXwvPUaDH7wS6O9uXqFw@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Eric Rescorla <ekr@rtfm.com>, Hrpc <hrpc@irtf.org>, Mallory Knodel <mknodel@cdt.org>
Content-Type: multipart/alternative; boundary="000000000000717cfe05f18cadb1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/nOGRZePsjFvb4iVuWSh4bXum46g>
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, 05 Jan 2023 23:29:56 -0000

Speaking as a privacy expert (I’m CTO of Patient Privacy Rights and on the
Electronic Privacy Information Center advisory board) and a contributor to
many protocol workgroups, human rights are much easier to apply to protocol
design. Some examples:

- Privacy is cultural with vast differences across the world. Trying to
design for privacy in a global context tends to the lowest common
denominator.“Privacy by Design” has been a failure in my opinion.

- Privacy is what gave us “Notice and Consent” in the form of privacy
policies and shrink-wrap contracts. Human rights, by contrast, are
inalienable. As my colleague in PPR says: “You can’t consent away your
human rights.”

- Privacy is not accepted as a public good. The justification for
commercial surveillance (a phrasing that is currently preferred by experts
in the regulatory context) is often the ability to trade privacy for
services delivered over the Internet. The ability to pay for privacy would
not be as relevant in design for digital public goods as a framing.

What attracted me to HRPC is the relevance and clear of your work on forced
association. In the context of a charter discussion, I have no perspective
across IETF protocol groups other than GNAP, but I hope we continue to
focus on protocols for digital public goods rather than policies.

- Adrian

On Thu, Jan 5, 2023 at 12:00 PM Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
> Hiya,
>
> On 05/01/2023 15:09, Eric Rescorla wrote:
> > 2. I think Privacy is much better understood than "Human Rights"
>
> Interesting. I'd agree if the set of people we're talking
> about were IETFers from a security background, but I think
> the opposite would be the case for HRPC folks whose
> background is work on human rights. And I'm not sure what'd
> be the case for e.g. IETFers from a routing background.
>
> For me, bridging those gaps ought be one of the benefits of
> HRPC existing.
>
> Cheers,
> S.
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc
>