[hrpc] My suggestion for the attribution paragraph

farzaneh badii <farzaneh.badii@gmail.com> Tue, 16 March 2021 12:18 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 251D23A0922 for <hrpc@ietfa.amsl.com>; Tue, 16 Mar 2021 05:18:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 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, T_REMOTE_IMAGE=0.01, 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 IXQAfzt_ZAWj for <hrpc@ietfa.amsl.com>; Tue, 16 Mar 2021 05:18:49 -0700 (PDT)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (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 BC1DC3A091E for <hrpc@irtf.org>; Tue, 16 Mar 2021 05:18:48 -0700 (PDT)
Received: by mail-lj1-x22e.google.com with SMTP id f26so20174171ljp.8 for <hrpc@irtf.org>; Tue, 16 Mar 2021 05:18:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hs0GbGBvnk1aMGA5ArNE1dYWHGSJMPLPCorYJlurgoY=; b=Fn4+bKZOUp35KU6LIAYHtsMkPiCVrmimik3DX6wd7PtuS+1CwsbYFo65ju/H00Wtmm sBUtiHUX8wY7LyYxYDsdT+eAdeDjmL6/2dQ/PEpkyoR4q602xKj9vjguXdg0wpFHkLJv 13ke6L/+C+GY5OA7T6RR3Evwhq5onfTUHcdAy8W38QEUPexYlxdtOCfXypdzqx3uxGGq aGoki416ALSTfXoa3TbXIzhfWXxHU5vocnbeVa3RvdlYbHQj/ePLLaVfMG5wO73AzKL6 KrdE19gGCxA4HRMuzm9tCLd3MaFaFDK/CYIPrpE/3UiFdIp3Ua/AwMIVMKGqK8FpaeNo x8sA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hs0GbGBvnk1aMGA5ArNE1dYWHGSJMPLPCorYJlurgoY=; b=j0ZCvBn1sg3o1arITPthOmC1bJp1MoSe3ok2+sZWZHfvsJQbvkXJR999VtDHrlSwTV k8E16TaJ+zuBk9XF8up/kX2uhvHDCE4Mgbh15+0KDNRYmFOJ7fCQ0ckp5hRt+GTIbxi9 0M0xCbJkn1R5j/9fAfvHYd4wf4DZ0MqGNod+OzaSoU2D6dPYTID7/Qlr6YvHahLvO0r5 MmA5zMHWJ0+4R7882wAFwkI/YjJUVj2gAzUG20de/b9jWb2BGP9mgUHlEz09xKsfadUW YPxnhgPzJU7cNEU6YRDumyV0MwvFtdHaeQ+rcfpDGa9lLW6u2hXTS1wwpC7z8lanFFLw Whxw==
X-Gm-Message-State: AOAM533dmqmZVu2t/ngcnIDIDWfAAtZHThvyvHplXXCZ797/3eiGlCEv 5eZns+6i6XpLMjAoz1TMCis/E73REl8gV5kf320=
X-Google-Smtp-Source: ABdhPJznC+vxJo3ObO2zTm2ATe8hhKJdOH5jZsaoidfN7Jrc86ORcBnlW39J5mc9l4iHQspyPqlbSZPPWT6VEjUhtwA=
X-Received: by 2002:a05:651c:119a:: with SMTP id w26mr2449451ljo.104.1615897125593; Tue, 16 Mar 2021 05:18:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:c189:0:0:0:0:0 with HTTP; Tue, 16 Mar 2021 05:18:45 -0700 (PDT)
In-Reply-To: <5f706893-5ccf-a6ad-353e-1f64241e9978@yahoo.com>
References: <CAN1qJvA_ONSNqk_Am6z6SASHO63eObaYMRVMY4cHR6XzPskGqg@mail.gmail.com> <988c1a1b-97a4-bccc-f991-7f51f760c088@cis-india.org> <CAN1qJvC2jPSJuawePyH5DO9xvqWLnUUAzFu8tWBzfkntQBEO6Q@mail.gmail.com> <5f706893-5ccf-a6ad-353e-1f64241e9978@yahoo.com>
From: farzaneh badii <farzaneh.badii@gmail.com>
Date: Tue, 16 Mar 2021 08:18:45 -0400
Message-ID: <CAN1qJvDx50N8JkC5jO=EeR4PKkoCE8Xn0FwtRj0-uQrowkWWWA@mail.gmail.com>
To: Mark Perkins <marknoumea=40yahoo.com@dmarc.ietf.org>
Cc: "hrpc@irtf.org" <hrpc@irtf.org>
Content-Type: multipart/alternative; boundary="0000000000002a253205bda65ebf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/EZ46R6o6ZGQxpjlWbSocHqMW-fI>
Subject: [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: Tue, 16 Mar 2021 12:18:51 -0000

Thank you Mark.
If that is the case, then perhaps we shouldn’t add this paragraph. I had
suggested it and still support that approach.

On Thursday, March 11, 2021, Mark Perkins <marknoumea=40yahoo.com@dmarc.
ietf.org> wrote:

> 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.
>
> MP>> This is exactly my fear, excepting that I disagree that "that ship
> has sailed", and am still not sure that consensus has been reached on this
> issue...
>
> Mark P.
> Le 12/03/2021 à 05:34, farzaneh badii a écrit :
>
> 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
>> >
>>
>
> _______________________________________________
> hrpc mailing listhrpc@irtf.orghttps://www.irtf.org/mailman/listinfo/hrpc
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Garanti
> sans virus. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
> <#m_140600057450132848_m_-6419674917296323565_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>


-- 
Farzaneh