IETF Logo Mail Archive

Re: [hrpc] HRPC recharter

Jens Finkhaeuser <jens@interpeer.io> Tue, 10 January 2023 08:18 UTC

Return-Path: <jens@interpeer.io>
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 12496C152561 for <hrpc@ietfa.amsl.com>; Tue, 10 Jan 2023 00:18:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-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 (1024-bit key) header.d=interpeer.io
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 uWBqxxA8EsGE for <hrpc@ietfa.amsl.com>; Tue, 10 Jan 2023 00:18:37 -0800 (PST)
Received: from mail-4022.proton.ch (mail-4022.proton.ch [185.70.40.22]) (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 32BE0C1522D7 for <hrpc@irtf.org>; Tue, 10 Jan 2023 00:18:35 -0800 (PST)
Date: Tue, 10 Jan 2023 08:18:27 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interpeer.io; s=protonmail; t=1673338712; x=1673597912; bh=I+x7EExad3kbROQrWLbPEKBPybXgP5ssz5zXgE5A1BA=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=KRc/sOptKNkTHLmBDj51ElLQQJsD/BI+pCmsskCMD0g1VL0H2iC8F0JAjlxqyAzxl 29lcSmkv2r7UD2yw5c80I0YrWw+mVzjhkFZ8TG/+Vjz9iU/ChHkO81zuwkMG8TNppf SGaDfDDIvNGqHOZeGrHxwpQtltVQkFOPxnaM/wUs=
To: Eliot Lear <lear@lear.ch>
From: Jens Finkhaeuser <jens@interpeer.io>
Cc: "hrpc@irtf.org" <hrpc@irtf.org>
Message-ID: <pV5jIGoys2OYStStFWHPislouC0adgYAxkJwI2RkCCzC8eriSGSAnuMnwEDt9IjFi0rUcrrA7i1bhvidiPjvx6Y26hd66TdxSfijZ4NfCKo=@interpeer.io>
In-Reply-To: <134c16a8-8660-def4-d24a-3da1b5ea9953@lear.ch>
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>
Feedback-ID: 18725731:user:proton
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="------7231d4e954eb97279a6f8eeac2da68cbaf671ba50b821c971ade66f4075dc21d"; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/kaDUnWis_4GzV1GjOg6Rgt0KGA4>
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 08:18:42 -0000

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

v2.23.0 | Report a Bug | By Email