Re: [hrpc] Protocol/Architecture consideration of Attribution & right of legal remedy (was: Re: I-D Action: draft-irtf-hrpc-guidelines-03.txt)

John Curran <jcurran@istaff.org> Wed, 12 June 2019 20:00 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 5DE66120114 for <hrpc@ietfa.amsl.com>; Wed, 12 Jun 2019 13:00:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=outbound.mailhop.org
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 lmKRXnsjLQXs for <hrpc@ietfa.amsl.com>; Wed, 12 Jun 2019 13:00:41 -0700 (PDT)
Received: from outbound2r.ore.mailhop.org (outbound2r.ore.mailhop.org [54.200.129.228]) (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 0D246120179 for <hrpc@irtf.org>; Wed, 12 Jun 2019 12:59:37 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1560369577; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=e1rBbWScQNUfFoBnKs6oVyRNn05FUQkZm/zC5rGaD7BNFO2nXyxc4Ce/xYLplhau5Rr3S1UItKbqL mQuV52HMKc6nYDg+rEY5FoWtnHn05WkSjy82wTWcwbjOVEjStq2Az3XB4LhmG3VFMUDB8+7VVnxEge 6l7LNQFY55h7i/n2/tkk2m4yAPDHZAesHCJHQeslaU6x+LMZQxZ4eF/V2lbjnxRaMH9CuWDgvQBoL6 DSMgo3DWcuFy1qVsdMgZAxQFiifhle/47depkjCpgq1GeI+N9SHKpx5kQbwGN8UTKmPUHWgMheqcJ7 VMDclZIc/dHgO+jvEbkUXNimXYtNiaw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=references:to:cc:in-reply-to:date:subject:mime-version:content-type: message-id:from:dkim-signature:from; bh=o486k4iy8aZkQB1eoLTlO/v7eVP8nAPVO+YN2/0iqrs=; b=cnMMw9zhuJuGjOMRqqngYhmhb0Y7QOW6wK8Yhj1JRVoz5AMfno/Vg9jee7vg7T3FhKep8VqhqODe0 y90liAOtRsr3+hCowFP/HZG7I2SzeDq5MIQM87cT60PnP3EjsiB1yMwp8w44sNq/fpyr0RGf5bKAHW X5ScqVlp77srLwZ4PYt13AeIU7QcrjzMgKvEIlUzAQfDKX+oxi3mIdunEhsDG9bYQWSRgDADcD4w1j zYd+B5i8nxAJ9/VG2c66MPJH9g7E5RKTwrHMtcXqo0SebQz48IAT5s5+p6CE3PmHkcOwH7Om/hcG0q b/bSqw1e7yjDNdIpkp7hi3lpFt3teQg==
ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=pass smtp.mailfrom=istaff.org smtp.remote-ip=96.241.220.148; dmarc=none header.from=istaff.org; arc=none header.oldest-pass=0;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=references:to:cc:in-reply-to:date:subject:mime-version:content-type: message-id:from:from; bh=o486k4iy8aZkQB1eoLTlO/v7eVP8nAPVO+YN2/0iqrs=; b=PIyQgdnTDbeYQpqPv1i794/6tnd5SAMyCkcpb0oTAYdCQnFTeM0Xx3LhNaFIWD19tL1JiIldmBpW1 x/QMycEsZO3RHQyXee+XYFCNZz5ug8ox3+BaCE733dlxuA9HCZXeOXq+gsFmHwyo7N4+WEn8smd6fT 6M69R4CJ8XLfy3603SGxRNkpWODpdggAhdUwKUmfeC4Kxf6TXfMp/7w0e1U04IgozO+PxDRr3x+UhF 1B4hY7YA1txC+2UtG1OgiqeVmGVGdLw1H/uqj0AX5CEwLMEx5VrhEHX40PhGS7Vj7tvrGPUiOJnLQT xvlFdw/k08Jxd1xHml/jnzjKO7ACHfg==
X-MHO-RoutePath: amN1cnJhbg==
X-MHO-User: 980cdb24-8d4c-11e9-b39b-9d2c53d3dedb
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 96.241.220.148
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from geode.istaff.org (unknown [96.241.220.148]) by outbound4.ore.mailhop.org (Halon) with ESMTPA id 980cdb24-8d4c-11e9-b39b-9d2c53d3dedb; Wed, 12 Jun 2019 19:59:35 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by geode.istaff.org (Postfix) with ESMTP id A4CC03BEA745; Wed, 12 Jun 2019 15:59:31 -0400 (EDT)
X-Virus-Scanned: amavisd-new at istaff.org
Received: from geode.istaff.org ([127.0.0.1]) by localhost (geode.istaff.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1bsNHBz6AxaM; Wed, 12 Jun 2019 15:59:30 -0400 (EDT)
Received: from [172.20.0.75] (unknown [65.216.233.162]) by geode.istaff.org (Postfix) with ESMTPSA id CE98B3BEA72C; Wed, 12 Jun 2019 15:59:29 -0400 (EDT)
From: John Curran <jcurran@istaff.org>
Message-Id: <75BFC93D-8C5A-45C3-A68B-B3BBEF65390F@istaff.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_91C349A4-8840-41D0-BCB7-C03B385C1D8B"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 12 Jun 2019 15:59:28 -0400
In-Reply-To: <CAN1qJvD+m+ecOWj8rY3v59u=qnxBH4zU8Z3G74R4tU38h6Eccg@mail.gmail.com>
Cc: Amelia Andersdotter <amelia@article19.org>, hrpc@irtf.org, Niels ten Oever <mail@nielstenoever.net>
To: farzaneh badii <farzaneh.badii@gmail.com>
References: <155989623088.20255.12181969220178709616@ietfa.amsl.com> <C550D5BC-8062-4C58-8CEC-B82B2798C1D9@istaff.org> <71b7350e-cb75-aba1-1717-50d1069531b1@nielstenoever.net> <B8D9823F-2D42-42DF-AE8A-6E67532DA4D1@istaff.org> <d66b60ab-3aaa-d45d-3f47-d2c00f89119d@article19.org> <1ECD44BA-4BB1-47FD-87B5-E35A3B6DDCB6@istaff.org> <CAN1qJvA5BdbSJNkGADChmtmjHzww0Q5RcvXwwOC4rO7YT7DiVw@mail.gmail.com> <992B79C0-5B80-4710-B8CF-D87BC80FA2C3@istaff.org> <CAN1qJvD+m+ecOWj8rY3v59u=qnxBH4zU8Z3G74R4tU38h6Eccg@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/lOjU1VFw4ANnfDghz0XT1-dQcKU>
Subject: Re: [hrpc] Protocol/Architecture consideration of Attribution & right of legal remedy (was: Re: I-D Action: draft-irtf-hrpc-guidelines-03.txt)
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "mail@nielstenoever.net" <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: Wed, 12 Jun 2019 20:00:46 -0000

On 12 Jun 2019, at 2:49 PM, farzaneh badii <farzaneh.badii@gmail.com> wrote:
> 
> Thanks John. That now makes better sense to me. We can discuss whether it should be documented and how it should be documented.

Agreed. 

> But we need to consider many more aspects of it. 
> We need to understand what  "security" and "legal remedy"  means in IP. What is "harm"? Harm is a very controversial term which can be interpreted in various ways.

Even if we had perfect and globally recognized political norms for harms from communications, we couldn’t ignore the potential need for attribution to support legal remedy. 

For example, protection of whistleblowers is widely recognized as an important element necessary to underpin the right of freedom of expression (and access to information), yet it often results in loss of personal privacy and/or security for the individuals involve – most would agree that using communication technology to disclosure an officials embezzlement of public funds is reasonable and yet disclosing their spouse's serious medical condition is not appropriate.  The communication protocols are agnostic on content, and so we need to be intellectually honest and document if a protocol’s attributes preclude support for legal remedy.   It doesn’t mean that such a protocol is “bad” but simply means that there’s a conscious tradeoff that’s been made on prioritization of functionality in favor of certain human rights (in that case freedom of expression over legal remedy.) 

> I suggest we have more discussion about the nuances before arguing about the inclusion of your text. 

I actually don’t feel particularly strongly about the inclusion or omission of the “attribution” attribute text, but would prefer not having the final document characterized as guidelines for assessment of “select" human rights – the offered text is simply the best I’ve come up with in order "round out" the overall effort. 

Best wishes,
/John

p.s.  Disclaimer: my views alone, and produced under the influence of excessive caffeine - no warranty assumed or implied.