Re: [hrpc] HRPC recharter

Abdussalam Baryun <abdussalambaryun@gmail.com> Fri, 06 January 2023 07:36 UTC

Return-Path: <abdussalambaryun@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 B2125C14CF04 for <hrpc@ietfa.amsl.com>; Thu, 5 Jan 2023 23:36:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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] 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 7B1dt0YIFevO for <hrpc@ietfa.amsl.com>; Thu, 5 Jan 2023 23:36:02 -0800 (PST)
Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (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 DB69AC14F749 for <hrpc@irtf.org>; Thu, 5 Jan 2023 23:36:02 -0800 (PST)
Received: by mail-lj1-x232.google.com with SMTP id g14so691547ljh.10 for <hrpc@irtf.org>; Thu, 05 Jan 2023 23:36:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=+0B1D3vLb4iAvkJ2fKfC1ljy5hcRJdleZbRx1Wv3Wqk=; b=Rps112GFeHkUNmubqbyc9CI8o+YC8iM2q5h5Nh/y3H2dYe2Zz2e75gt0GBoRhlYMCa myVKBh6c8spiCzdD0dOabuU+TVe8sp+BmEIUN5y5u7lFlGYjFSws7hWyBb7xzcnWTK2b l06r5Wo32taGncWdRBK0EZRtPkeZyrHuMtUcv2My8+JMIZYyKWK251DWcqgyGZr09bhG HcDqtP7Vy52fkPJXK31k0lssrsOVqp1Yqxvz2kI4srIWsLfjGA3sdECm62bwD13kwtYL /u/yRV0Y6ktzgCf9SULJKQFq/DniVVe0k7qJXRFgINMfn2oMw7SP7xgsmMyVqMWuxQUJ wwqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=+0B1D3vLb4iAvkJ2fKfC1ljy5hcRJdleZbRx1Wv3Wqk=; b=EVx9M0L3s9TGmxoSpbVwmfcshZ5AVKfPFf2AdXPKTy1nvysJBbC8ZneHv7QDXUHDw8 pv/5oGYS1s6LY3Cip83zt0/F8NlDOwQRsmYrj+SZPgWNxB4FmbJLLLs9wPkBuWPMuFmJ EcHWh7ddFlduBCeROZPzjQ5acz4c5LSReSAWj/zjGgry9MzH+eS51gaE1SXg8BqDnrCJ feHYLu7Xht50CWIcSGBKpvJpDRi63LsSJ6G7D2yt2qJkjUMJwD3wPFaVX1FRJLNTy3PS p/sKMl4bsHKFzvWAU0ZAs9MkSmmWSG+Ep6Zo3eUFiKynmKeLHIkjjZEHr59EpNaS32oO cikw==
X-Gm-Message-State: AFqh2kpJefKe4HNtFHt+VurrdP20EG48h4y9loZeyyykbdTqdPLoyni+ KEoA0XUv4oC89lAEdEWTSKDUZpyDaz8ceeJWPdcX+fKi
X-Google-Smtp-Source: AMrXdXvc5AAMbcUyAU5M1qrI1WqGlZZDJedINvUi0GFDeTKNPQq1CP16CFv2PHeIJTLGB9IJEG3a1ZMWj3K13xN7KTw=
X-Received: by 2002:a05:651c:1713:b0:27a:ec5:2ddb with SMTP id be19-20020a05651c171300b0027a0ec52ddbmr3046568ljb.128.1672990559859; Thu, 05 Jan 2023 23:35:59 -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> <68dab8e6-b17c-4ceb-5267-d4edb62f3eea@cdt.org> <20230106020951.wrv6cgr6eci4lqoo@crankycanuck.ca>
In-Reply-To: <20230106020951.wrv6cgr6eci4lqoo@crankycanuck.ca>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Fri, 06 Jan 2023 09:36:40 +0200
Message-ID: <CADnDZ8_4jZjpmhjed0+mXftKDk95G0JcL2P36tEPrN8BHjYRZA@mail.gmail.com>
To: hrpc@irtf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary="0000000000000879b905f1937878"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/Wb_hgKj4P3kD-7ag-cCv1YMv1Iw>
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: Fri, 06 Jan 2023 07:36:08 -0000

Hi Andrew,

I thank you for your input,

On Fri, Jan 6, 2023 at 4:10 AM Andrew Sullivan <ajs@anvilwalrusden.com>
wrote:

> [....]
>
> On Thu, Jan 05, 2023 at 11:01:07AM -0500, Mallory Knodel wrote:
> >In other words: I don't believe it is widely accepted that HRPC has a
> >misguided view of its own purpose. Others may, but that has
> >unequivocally improved since it was first chartered.
>
> I must say that I very strongly disagree with that "unequivocally
> improved" claim.  I thought the original charter discussion was pretty good
> because of the way it whittled the space down to a set of questions that
> one could imagine answering through research.  I was indeed frustrated over
> time by the way the RG resisted sticking to those questions, but at least
> there was something to hang on to.  I don't think officially giving up on
> such scope limitations is an unequivocal improvement.  (Maybe I'm just
> old-fashioned.  I also believe that, say, musical forms often provide a
> better structure for creativity than a total lack of such structure.)
>

you are right, and you are not old-fashioned. My opinion is focusing on
human rights of IP_Users and them not to be abused by the technology
because of the way of technical_protocol design. I think the RG chair needs
to check the consensus on their proposal of recharter because I think the
chair has a different opinion from the group. This group need experts in
many disciplines that will help but we need a clear scope in each
research_draft or research_task.


> I suppose I will receive a suggestion that I make a PR at the github, but
> if I am honest I don't really understand why the charter text needs to
> change except perhaps to remove bullet 2 under "Objective".
>
>
> I also don't understand, because the first message in this thread from the
chair did not explain the recharter-reasons from IAB.

Best Wishes

AB