Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-guidelines-10
John Curran <jcurran@istaff.org> Mon, 31 January 2022 17:48 UTC
Return-Path: <jcurran@istaff.org>
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 B17323A1097 for <hrpc@ietfa.amsl.com>; Mon, 31 Jan 2022 09:48:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DMV63pZj_HuG for <hrpc@ietfa.amsl.com>; Mon, 31 Jan 2022 09:48:40 -0800 (PST)
Received: from st43p00im-zteg10071901.me.com (st43p00im-zteg10071901.me.com [17.58.63.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19A753A109C for <hrpc@irtf.org>; Mon, 31 Jan 2022 09:48:39 -0800 (PST)
Received: from smtpclient.apple (c-69-255-21-229.hsd1.va.comcast.net [69.255.21.229]) by st43p00im-zteg10071901.me.com (Postfix) with ESMTPSA id BBDCF840D90; Mon, 31 Jan 2022 17:48:37 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: John Curran <jcurran@istaff.org>
In-Reply-To: <c0bcf907-8af4-48c8-f199-7b9d9c2d535d@cis-india.org>
Date: Mon, 31 Jan 2022 12:48:36 -0500
Cc: farzaneh badii <farzaneh.badii@gmail.com>, Colin Perkins <csp@csperkins.org>, Eric Rescorla <ekr@rtfm.com>, Mallory Knodel <mknodel@cdt.org>, "hrpc@irtf.org" <hrpc@irtf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B777A06-1919-4878-A0A0-0F714DC1763A@istaff.org>
References: <6486E6F5-4CE6-4A5F-B91F-9C23ABD00A78@csperkins.org> <55B7FD6E-EF9D-4E90-B6F7-34E2BE24897F@istaff.org> <CABcZeBMS9sGTdgf6ckwG9iN3n=dR=Yb=bXtdKi+mnH-LQVYbQg@mail.gmail.com> <85F738E7-0D3D-490D-B166-FF2C0D975CFD@istaff.org> <CAN1qJvBm0gLqsCS+tC=oEXHCkfU6VDcd+MQgZDvGj0+f-983PQ@mail.gmail.com> <CBB1AF63-652A-4DAD-878A-6658827DD45C@istaff.org> <CAN1qJvC19_9enkQ1ZqCKt5aGVDje3qKhNG6c-v3ErKmRsmc8Yw@mail.gmail.com> <295B9E3F-A89A-4AC8-81E6-C39682903662@istaff.org> <c0bcf907-8af4-48c8-f199-7b9d9c2d535d@cis-india.org>
To: Gurshabad Grover <gurshabad@cis-india.org>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.425, 18.0.816 definitions=2022-01-31_07:2022-01-31, 2022-01-31 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1030 mlxscore=0 mlxlogscore=997 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2009150000 definitions=main-2201310116
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/QKjoZQw9kpruH3UCrIhZcxlSeAk>
Subject: Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-guidelines-10
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
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, 31 Jan 2022 17:48:45 -0000
Gurshabad - I am fine with whatever outcome the working group decides - I provided some possible example text solely to be responsive to the comment received in the review and it was truly optional in nature. Thanks, /John Disclaimer: my views alone - Note: made with 100% recycled electrons. > On 31 Jan 2022, at 12:44 PM, Gurshabad Grover <gurshabad@cis-india.org> wrote: > > Colin, John, Farzaneh, Mallory, Eric: thank you for sharing your thoughts on right to remedy/attribution section. > > As Niels said, the text of the section was arrived at after much discussion, in the hope that it presents group consensus. I think it successfully conveys the trade-offs being discussed on this thread. It also conveys explicitly to the reader that building in attribution mechanisms in a protocol is "most likely not consistent with human rights." > > Since it tends towards advocating _against_ attribution, adding an example is perhaps not as useful as it is for other sections (and may be more contentious than the current text itself). After re-reading all the emails on the topic, I am of the opinion that we should leave the text as it is. > > -Gurshabad > > On 1/27/22 03:00, John Curran wrote: >> On 25 Jan 2022, at 8:43 AM, farzaneh badii <farzaneh.badii@gmail.com <mailto:farzaneh.badii@gmail.com>> wrote: >>> >>> < I am unclear what research you believe is required; the present difficulties of real-world prosecution due to lack of attribution are quite well-known - > >>> >>> But should we solve them here? In this research group? By just inserting opinions in the document? This has been the fundamental problem we have had at HRPC. This group was supposed to be a “research group”. That’s what RG means! Copy and pasting from other sources without even coming up with scope and method and just expressing opinion and which will end up in the document is not research. >> Farsaneh - >> I did not see the guidelines document as an effort to “solve” >> anything with regard to the Internet, but rather to serve as a tool >> to provide protocol developers with guidance that will aid in their >> understanding of how their protocol decisions can potentially >> influence the exercise of human rights on the Internet. >> One of the human rights impacted by protocol design is access to >> remedy, and out of completeness I would expect that we’d want to >> include mention of how some protocol attributes (i.e. lack of >> attribution and/or anonymity) impacts access to remedy. This impact >> is already clearly documented (e.g. review the section of the >> "Global Commission on the Stability of Cyberspace" report that I >> cited earlier, or simply attempt yourself to obtain legal remedy >> against a harm committed anonymously over the Internet) but I do >> understand that including such a statement in the guidance to >> protocol developers may be controversial since “access to remedy” is >> not a particularly popular topic in most academic discussions of >> human rights. Thanks, >> /John >> Disclaimer: my views alone - free to use/reuse/discard as you see fit. >> _______________________________________________ >> hrpc mailing list >> hrpc@irtf.org >> https://www.irtf.org/mailman/listinfo/hrpc
- [hrpc] IRTF Chair review of draft-irtf-hrpc-guide… Colin Perkins
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… John Curran
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… Eric Rescorla
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… John Curran
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… Eric Rescorla
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… farzaneh badii
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… John Curran
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… John Curran
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… Eric Rescorla
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… John Curran
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… Eric Rescorla
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… John Curran
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… Vittorio Bertola
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… Niels ten Oever
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… Mallory Knodel
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… Eric Rescorla
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… Gurshabad Grover
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… Niels ten Oever
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… farzaneh badii
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… John Curran
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… Gurshabad Grover
- Re: [hrpc] IRTF Chair review of draft-irtf-hrpc-g… John Curran