Re: [hrpc] HRPC recharter

farzaneh badii <farzaneh.badii@gmail.com> Mon, 09 January 2023 11:33 UTC

Return-Path: <farzaneh.badii@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 9875CC1D25BE for <hrpc@ietfa.amsl.com>; Mon, 9 Jan 2023 03:33:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 oJYLhBbTRGHh for <hrpc@ietfa.amsl.com>; Mon, 9 Jan 2023 03:33:38 -0800 (PST)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (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 CA264C151711 for <hrpc@irtf.org>; Mon, 9 Jan 2023 03:33:38 -0800 (PST)
Received: by mail-pj1-x1036.google.com with SMTP id b9-20020a17090a7ac900b00226ef160dcaso7349275pjl.2 for <hrpc@irtf.org>; Mon, 09 Jan 2023 03:33:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.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=rSRZ9gCL3G/ERm7I4D4wWlvkvoYP0ofaGzctqOiEWz8=; b=g8jjWi/CUNbI/33+7lT3QY+lY5aYx5mDMCEnW5qwMmmE97KyLqu/230FGBlknOn9Q9 0ciWq9Pl8UFp/6N1ggkqOSM/KGpU5HGDnMq9euwevD6PyrY81/UiA/uLl7/0Cwd30a0Z J/ztENO/k7JSW5RN73qqI74H0gN5dC0kzG+ILPiahe031YrACAh7LKYPPaVH5z60EZ3Y EVYq6826hPImkDMBy1QsCkbzEmHTnuBxxdBN8i7tR7SxP8/O3G5RjJROFriAaPXpTSwP hr/w9/WGfxfddws0rC8RBg7dro0KzytlLjTisYV6e8zYX3KlyQz6xyN+Bk3N995zYxou bILw==
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=rSRZ9gCL3G/ERm7I4D4wWlvkvoYP0ofaGzctqOiEWz8=; b=yauP0XnGWoWpvat1Be+gMx4+dKuiBtNtDQR42mt/dZnFSfunXH0xeoZHKsuknCyu34 c0JfirYpYivi1VIoWbFHcN8TZ5Dz22uqpa/kj6lHCY4vwUicNeYz8w7VfjV3R4j7YghE uWfsNppGxNUylMuT2OHErkpMg0oMzSIjimQhi7bmtPnyACfHR3ifsi+L10bR2I2DqaP7 7zQLrBpcDCgIejihl0JHl2J11AC7etUDUnkvZQolG6tVrLsDUa8pVDUG+Q2fZgJohwMx 1P6rXHX+fg9wblBnimFYHEizN0cW0iSG0Q/VYbIE9Z59b9tCBYdBIE6TtnKSwzGibICs tsjA==
X-Gm-Message-State: AFqh2kpNxbgXCiE2t6UruXqJpwtWmgyAmv+hWO30vKk//23NsPTqzn9C xJV3qkngTPNJ7osZKne433be04Ljkc1ZlHtqxU/bzxnH60M=
X-Google-Smtp-Source: AMrXdXvFIF0CBHVBvN0z6zMcenPLC+UNs69cgdfAhWHiwdQCjIbjJHIA7s522tzlLkOOEsbdMQdcIG5EdFuFF75r4W0=
X-Received: by 2002:a17:902:9e05:b0:193:39bf:5a27 with SMTP id d5-20020a1709029e0500b0019339bf5a27mr69742plq.86.1673264018093; Mon, 09 Jan 2023 03:33:38 -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> <87FD35DB-1857-4F20-B3F4-D38A8E80C99F@istaff.org>
In-Reply-To: <87FD35DB-1857-4F20-B3F4-D38A8E80C99F@istaff.org>
From: farzaneh badii <farzaneh.badii@gmail.com>
Date: Mon, 09 Jan 2023 06:33:26 -0500
Message-ID: <CAN1qJvA34VmQkiUsHb7UCMU+qktcC8h5fE=8dC6UjoRm-W4oTg@mail.gmail.com>
To: John Curran <jcurran@istaff.org>
Cc: Eliot Lear <lear@lear.ch>, "hrpc@irtf.org" <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="00000000000069fbe805f1d3231e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/4SEpdpD307QrmkqvBVhqC8HBlkk>
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, 09 Jan 2023 11:33:42 -0000

I don’t understand why we want to change this group P name into “policy”.
The more I think about it the less I am convinced. Policy-making and policy
recommendations don’t happen at IRTF. For example, IETF came up with RDAP.
It was at ICANN that we discussed the policy issues surrounding its
implementation. Are we going to do research on implementation of protocols
in this group? Policies that should be in place to implement the protocols?
Or are we assessing protocol implementation and mitigating the adverse
effects?

Somebody mentioned here that “policy” is the tool of the state. True. But
then policy is also used in private settings, by tech companies and IG
organizations. Are we not considering those?

On Sat, Jan 7, 2023 at 8:59 AM John Curran <jcurran@istaff.org> wrote:

>
> > On Jan 6, 2023, at 4:33 AM, Eliot Lear <lear@lear.ch> wrote:
> > ...
> > 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 am fine with the revised charter.
>
> (I had hoped that the update would include more focus on protocol research
> topics that would allow us to deliver on these conflicting rights, but it
> appears to take a different approach and presume that such matters are
> unsolvable – and instead work on building “evidence and guidance for policy
> makers on the necessary design tradeoffs that should be made.”   This is a
> tad unfortunate, since we know that policy makers will not engage in the
> hard technical protocol research necessary into solving these problems, and
> this “research group” resigning itself to documenting recommended guidance
> on tradeoffs rather than working on exploring technical solutions for
> protocols nearly assures that some human rights will never be satisfied on
> the Internet.)
>
> /John
>
> p.s. Disclaimer: my views alone - even ChatGPT is likely to produce better…
>
>
>
>
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc
>
-- 
Farzaneh