Re: [hrpc] My suggestion for the attribution paragraph

farzaneh badii <farzaneh.badii@gmail.com> Thu, 11 March 2021 18:34 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 DFF713A0C99 for <hrpc@ietfa.amsl.com>; Thu, 11 Mar 2021 10:34:40 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7kDQVSmeH6ic for <hrpc@ietfa.amsl.com>; Thu, 11 Mar 2021 10:34:39 -0800 (PST)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A48043A0C94 for <hrpc@irtf.org>; Thu, 11 Mar 2021 10:34:38 -0800 (PST)
Received: by mail-lf1-x131.google.com with SMTP id n16so41443702lfb.4 for <hrpc@irtf.org>; Thu, 11 Mar 2021 10:34:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sdHYUHZTVrIiylhx0+dCWAbsIGXRZYQ5yT7NvW4ZonA=; b=nw+b31t5+yF5m7F1ISc8E+6MmoWTTZJJYU3ZwaDWzEgTOKk4MZGtEhzTHAONpUKjcq K5YqSUvjo0ljYCyf6h2t2NJn24xxL6b4D/I3wJOT3pV4BmFEMiuJm9I6+lNuYhBmeLoI LWWYMZQLVqKxXNiv07v6+rWlpuJ8Fe7HWKsAL/4zDIfLQKXGjqCBugBEjhbzDfFdoU2m pB3DZdTlqB2j+EjBc2CGrB7Ol5KgA1JlaJ6rmio+oMqdC2l/2scRJXXn9j4RpbLZRpPz 421iILyMd7fTvtfEdVVcum28wvKipXC01jI3CoFdEfW9feRKXE8flVuc08UWumzOjsi9 LO1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sdHYUHZTVrIiylhx0+dCWAbsIGXRZYQ5yT7NvW4ZonA=; b=p6NA87w23Aj7dRmeQkj3yl/8U/y5BjrVBTdy85p4lDm8+qgUqddaDH1CdhSxiPAoe6 YnjP7kZtyPQplKuo7bS3QDvb4eh2iMa7GuptbcF6F6zu819eldr/S+gSNchx5e+X0EDF Oj0v9eHKZLBxdPG5tP4xjETA71tcmLnGQojAWjBytyK33+msuxBXwGGLl4tiLTyiymhq CtDoiQsrshpKieGFD8zsVvlrTYMMs2n+AU+faKNyNn3q4S9pWqnEQ7rbU+B4M3R3ya5a JHxa7t1oM+cqtCbWOsE049pjxeeUH5rBWJfDGg4qDIOWWZ2B+0BLFoh5d6Ezc68y/mH3 Rc6w==
X-Gm-Message-State: AOAM5300xl40DvaNjwH4CsERIFTGdp1XJpYs38ttM/gkyLmudOgIItYO HkEc32pKvkaawL7t90j1rYrzUvAtUKe3Jg1+zzs=
X-Google-Smtp-Source: ABdhPJwvGbadF3fP5buK1WJ4KYDMEs4dRs6lEsoBj6w3Y4gIC8vedi+OHC58FGkmqR06qncbfjGoSjMks3WF3ScjR0M=
X-Received: by 2002:ac2:5e26:: with SMTP id o6mr3055368lfg.355.1615487675718; Thu, 11 Mar 2021 10:34:35 -0800 (PST)
MIME-Version: 1.0
References: <CAN1qJvA_ONSNqk_Am6z6SASHO63eObaYMRVMY4cHR6XzPskGqg@mail.gmail.com> <988c1a1b-97a4-bccc-f991-7f51f760c088@cis-india.org>
In-Reply-To: <988c1a1b-97a4-bccc-f991-7f51f760c088@cis-india.org>
From: farzaneh badii <farzaneh.badii@gmail.com>
Date: Thu, 11 Mar 2021 13:34:09 -0500
Message-ID: <CAN1qJvC2jPSJuawePyH5DO9xvqWLnUUAzFu8tWBzfkntQBEO6Q@mail.gmail.com>
To: Gurshabad Grover <gurshabad@cis-india.org>
Cc: Hrpc <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="0000000000000ce1a305bd47091b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/uxVqrFVcauRbSmY7Wo8x1CuMHWI>
Subject: Re: [hrpc] My suggestion for the attribution paragraph
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: Thu, 11 Mar 2021 18:34:41 -0000

Thank you Gurshabad,

Yes this is fine, though I would have removed "may.. be" from the following
sentence and replace it with "is".
attribution on an individual level [may] *is not [*be] consistent with
those particular human rights.  and would have removed individual from "i.e.
mechanisms in protocols or architectures
that are designed to make communications or artifacts attributable to a certain
computer* or individual)*"

I can't think of a text that captures Mallory's suggestion right now but I
am not insistent on further changes to be applied. So don't want to hold
you back.
All good and thank you for your hard and excellent work.


An annoying P.S.: just for the record I hope this paragraph does not
encourage protocol developers to design protocols that can attribute
certain action to an individual or lead to identification of people. I hope
it doesn't legitimize attribution using protocols, with no accountability
or checks and balances. Attribution features can be abused. I still don't
think attribution should have been included at all, but that ship has
sailed. So, I compromise.



Farzaneh


On Thu, Mar 11, 2021 at 1:00 PM Gurshabad Grover <gurshabad@cis-india.org>
wrote:

> Thanks, Farzaneh.
>
> I was referring to these suggestions (which came through well to my mail
> at least), which I mostly incorporated. I realised from your chat
> messages during hrpc today that you were highlighting the importance of
> removing the reference to 'law enforcement agencies'. Taking that and
> the recent suggestions into account, would this text be fine?
>
> """
> Question(s): Can your protocol facilitate a negatively impacted party's
> right to the appropriate remedy without disproportionately impacting
> other parties' human rights, especially their right to privacy?
>
> Explanation: Attribution (i.e. mechanisms in protocols or architectures
> that are designed to make communications or artifacts attributable to a
> certain computer or individual) may help victims of crimes in seeking
> appropriate remedy.  However, attribution mechanisms may impede the
> exercise of the right to privacy.  The Special Rapporteur for Freedom of
> Expression has also argued that anonymity is an inherent part of freedom
> of expression. [Kaye] Considering the adverse impact of attribution on
> the right to privacy and freedom of expression, enabling attribution on
> an individual level may not be consistent with those particular human
> rights.
> """
>
> On a finer point: I do not think that it is appropriate to remove 'the
> right to remedy' from the 'Impacts' section, because it is precisely
> what this section about (regardless of the final position it takes).
>
> -Gurshabad
>
>
> On 3/11/21 11:19 PM, farzaneh badii wrote:
> > Seems like the suggestion I made did not come through because I
> > strike-through
> > Screen Shot 2021-03-11 at 12.44.34 PM.png
> >  that didn't appear on the mailing list archive so I took a screenshot
> > of the changes I suggested which is attached.
> >
> > I will rewrite it here.
> > Farzaneh
> >
> > _______________________________________________
> > hrpc mailing list
> > hrpc@irtf.org
> > https://www.irtf.org/mailman/listinfo/hrpc
> >
>