Re: [hrpc] HRPC recharter

Adrian Gropper <agropper@healthurl.com> Tue, 10 January 2023 17:36 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 D7FC9C09A5CA for <hrpc@ietfa.amsl.com>; Tue, 10 Jan 2023 09:36:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.547
X-Spam-Level:
X-Spam-Status: No, score=-6.547 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.096, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 kw4E49iSjL7O for <hrpc@ietfa.amsl.com>; Tue, 10 Jan 2023 09:36:41 -0800 (PST)
Received: from mail-ej1-f54.google.com (mail-ej1-f54.google.com [209.85.218.54]) (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 14A35C09A5B1 for <hrpc@irtf.org>; Tue, 10 Jan 2023 09:36:41 -0800 (PST)
Received: by mail-ej1-f54.google.com with SMTP id ud5so30644746ejc.4 for <hrpc@irtf.org>; Tue, 10 Jan 2023 09:36:40 -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=S+qj7KFRmbnXs7wx7+meC3wLV9er+3dJ7zLT4piDiew=; b=C4US9F+LHDftd4fWeDF6BDogHOy8m1jpBQkD4CCPchoUi9ISa6lxgUEsqCwR8Tr/oc nHncZ8lpVtJQjUuAAmSM+KssZvUGuyRgPyqAAQk6/DwoZ0I5cnUaxbxit59OVQD/22V4 O+4LIpFMdanbRsJ/fLxqr/xTb4pNE5YB4wTekuTUqDZ+e9mbJqbc+ljpF5BZ0pbLbCVW OuWoUR/qKFdCSUUfCmEUPBivl0l1FQJBBeMOfL1YlVJzKll32UjwwNKAvXKKXZRPS7Xm 3OmT/GdHtU/qyCYDJTY4EtohtkoHuejcZpgLRKVfEaE6vaBQkBLWwf5yI1AQ3JTVamYW 7dtA==
X-Gm-Message-State: AFqh2kpaRQT3AU8wFpWzV5IyDLlWE6yfsNtPGttUxF6DBC0nLKCkYQiW q2y5mpOG2DvrbVk9iiYPp8XOGJZrYm/ykz0WnxcgndY2
X-Google-Smtp-Source: AMrXdXsg+To4pr5V9UQuiwAsTwoOzTOp3ZJ7TMrl8ADvfAePS+YhJEfqBEn1LBAUZQ4De1mGBR5k5NtfvEJs+98CR3o=
X-Received: by 2002:a17:906:b255:b0:812:d496:2c9a with SMTP id ce21-20020a170906b25500b00812d4962c9amr7551307ejb.367.1673372199207; Tue, 10 Jan 2023 09:36:39 -0800 (PST)
MIME-Version: 1.0
References: <6ddd480d-76ed-a05e-066d-d740fee61441@cdt.org> <20230104215936.5exwsmtztk2shnzb@crankycanuck.ca> <63464538-4d40-a946-bcbe-570a6a3b49f9@lear.ch> <bTrwmE0TLN4PwdQNwJzzFmzPZPIjXrO6ld6loBlNBDBrluGDos9kftE0EzKxQMFhzhoE6LJewu0jGGFet5PqoYFj8gJaHRguKWDYFmp0fJ4=@interpeer.io> <134c16a8-8660-def4-d24a-3da1b5ea9953@lear.ch> <pV5jIGoys2OYStStFWHPislouC0adgYAxkJwI2RkCCzC8eriSGSAnuMnwEDt9IjFi0rUcrrA7i1bhvidiPjvx6Y26hd66TdxSfijZ4NfCKo=@interpeer.io> <CAN1qJvAWPxDaNVUj9COhjbysweErNxg3zx4QWXGOgFNA_DAvuw@mail.gmail.com>
In-Reply-To: <CAN1qJvAWPxDaNVUj9COhjbysweErNxg3zx4QWXGOgFNA_DAvuw@mail.gmail.com>
From: Adrian Gropper <agropper@healthurl.com>
Date: Tue, 10 Jan 2023 12:36:25 -0500
Message-ID: <CANYRo8gTfihYVe0Hc=G7Kdi0x_vnX-maeeVCk3n+tRv31x_VQg@mail.gmail.com>
To: farzaneh badii <farzaneh.badii@gmail.com>
Cc: Jens Finkhaeuser <jens@interpeer.io>, Eliot Lear <lear@lear.ch>, "hrpc@irtf.org" <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="00000000000082c60505f1ec53c9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/S3FTeZmmF2e_yUpohUtI_M0i_yY>
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: Tue, 10 Jan 2023 17:36:44 -0000

The greatest contribution HRPC can make is to show how human rights are
different from privacy and security. Talking about human rights in terms of
privacy is confusing because privacy is cultural and human rights are
universal. Talking about human rights in terms of security is confusing
because security is expensive in many ways, including the inconvenience of
high security practices.

If we were to recharter I would opt for a clearer separation between
Privacy, Security, and Human Rights considerations and having all three on
equal footing in IETF standards.

- Adrian

On Tue, Jan 10, 2023 at 12:25 PM farzaneh badii <farzaneh.badii@gmail.com>
wrote:

> Most times, this practice of balancing rights favors the powerful who can
> quash other people's rights and abuse their power. We can start from
> debunking some narratives that, for example security and privacy are always
> conflicting (they are sometimes but sometimes they are not and they are
> quite aligned).
>
> And what do you mean by technical solutions? Technical solutions that
> address the tradeoffs between rights? Am I getting this right? If so, then
> I totally disagree, I think you cannot overcome the trade-off with
> technical solutions. I don't want to misframe this but are backdoors
> technical solutions? I prefer that policymakers actually understand the
> technical limitations and the effect of their policies on the Internet and
> values they want to uphold.
>
> P.S. John's disclaimers are always so apt. A genius lawyer must have
> crafted them.
>
>
> Farzaneh
>
>
> On Tue, Jan 10, 2023 at 3:18 AM Jens Finkhaeuser <jens@interpeer.io>
> wrote:
>
>> Hi,
>>
>> > Nobody disputes that human rights concerns are a problem now. What many
>> > of us have concerns about is how to balance the different and often
>> > conflicting rights and interests at the time of protocol design.
>>
>> I wasn't quite sure how to parse this comment, and wanted to mull it over.
>>
>> So far, the group has focused on considerations documents, which raise
>> the questions that one has to ask when balancing such things as you
>> mention. I can't find it in me to see anything concerning about that. This
>> may reveal conflicts in interests, but that is the entire point of asking
>> questions. It's how you know that more work is needed - or a comment on why
>> something can't be done in the design.
>>
>> I'm not sure what is concerning here.
>>
>> Jens
>> _______________________________________________
>> hrpc mailing list
>> hrpc@irtf.org
>> https://www.irtf.org/mailman/listinfo/hrpc
>>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc
>