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 11:06 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 463EA120150 for <hrpc@ietfa.amsl.com>; Wed, 12 Jun 2019 04:06:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 gbG4rGgaRr71 for <hrpc@ietfa.amsl.com>; Wed, 12 Jun 2019 04:06:04 -0700 (PDT)
Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 1A075120124 for <hrpc@irtf.org>; Wed, 12 Jun 2019 04:06:03 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1560337563; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=B5DcFUM9BYe0D4Frm9jP4mXpW5VfsmCHPfal77nLFKZJwQzOJJWB693zGxUPJPJKsY3+jmDlNBo69 mhuDLrePZAlQcOWGc11wYcitoGpDFoQ3lveccfT2VNqkk7ZEGHHVZmoPahVX1yoSYXgXbwB7WELDNX AdNAZYkA7TonM8jF4uT7MXG+b+vfyhPh8cvS9eTXKKOHPOn5mZz/OsDFW8EM9MeQX8L8zm0poxxSd9 uqtqKrfV4lCj9TN5pDWgMP7oQ+K1ag8jco/MEPtCwarqR3wRqfsl9jTLxlLf3d56/GLFNNvRYoU2IJ K+XX1TM0HDvELPTWHPc/bx13mv1PoVg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=to:references:message-id:content-transfer-encoding:cc:date:in-reply-to:from: subject:mime-version:content-type:dkim-signature:from; bh=DscFfi0hNUHV+WKemL4DfllKv24zVzq+Q7eJN1C8BR4=; b=rN8QxQBsenwEWcTTOUgfjuQAy97VRfgAFqnYjmuNwWffwpEypoFx21Ufndsv3jPv3QCrpvoxU+MxY XSllVmhnlo6gx5Q3MX4eW4/v0gb4anzkO75usnf0U5V2z5EoFCUUUv3M43ecD4ZFDdVFNbTnBz2GvG YZZRtOGX5ca21+/2dnNTgfCJkFw3w41N9nI3ynGFb+/zoj5tIWJjIQwRXG8vlQMjya6RasiTT6XCtu ogCW8nAr1oMFxFoOHoAx2hjCapO57veNIXBofzAtN6yhzZyxxDPQX/zbDUrOygOMTlon1Epw4xIcFX rKmcPOgIQKDOsaMNnCeBPlRcWEmM0QQ==
ARC-Authentication-Results: i=1; outbound3.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=to:references:message-id:content-transfer-encoding:cc:date:in-reply-to:from: subject:mime-version:content-type:from; bh=DscFfi0hNUHV+WKemL4DfllKv24zVzq+Q7eJN1C8BR4=; b=Bx0eW9oTUZJvn4rmy9YWfSdpSCmHZMIw+EQrzm+UiaUmx8V35mTtkG9EGN5xzon+rU6KrCYYZQZcM bl9EphF3rrgrbt0amwxeNnWe3PdtJrk76Bhd083WIH+LYoYo1CCCnsqXF8DJzAUJUZzZDBJhp1l6Ie AxoJFM42T9DYS89+RIGWe3wXql0EsNOQ900fCtJUldvokU5EYVjKpzCZxugrSnozXj2QbA9h/IKOAt j14xltr8EBbcxn/jaThmsQS1DtbONsVxIu8Dc7l9sNR5I4aGdFQoSCIkmc7HJLDqU/tTCuAEPqcnQM BA0PI5dAj2GV9lnULvDPhu+4e8oqDFg==
X-MHO-RoutePath: amN1cnJhbg==
X-MHO-User: 0db3196d-8d02-11e9-ba65-db796b3fb7af
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 outbound3.ore.mailhop.org (Halon) with ESMTPA id 0db3196d-8d02-11e9-ba65-db796b3fb7af; Wed, 12 Jun 2019 11:06:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by geode.istaff.org (Postfix) with ESMTP id D741E3BE4977; Wed, 12 Jun 2019 07:05:56 -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 P_HlMo2bj42B; Wed, 12 Jun 2019 07:05:55 -0400 (EDT)
Received: from [172.20.0.75] (unknown [65.216.233.162]) by geode.istaff.org (Postfix) with ESMTPSA id A7E363BE4969; Wed, 12 Jun 2019 07:05:55 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: John Curran <jcurran@istaff.org>
In-Reply-To: <d66b60ab-3aaa-d45d-3f47-d2c00f89119d@article19.org>
Date: Wed, 12 Jun 2019 07:05:54 -0400
Cc: Niels ten Oever <mail@nielstenoever.net>, hrpc@irtf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1ECD44BA-4BB1-47FD-87B5-E35A3B6DDCB6@istaff.org>
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>
To: Amelia Andersdotter <amelia@article19.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/oK2XPCGjdvm7MMjr3cyCzREkuaA>
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 11:06:06 -0000

On 12 Jun 2019, at 6:13 AM, Amelia Andersdotter <amelia@article19.org> wrote:
> ...
> Normally, human rights are obligations on governments and duties on
> companies to respect individuals.

You use the term “normally”, where perhaps you meant “typically”?  All human rights are normal, but I concur that the typical considerations regarding human rights implementation involve preventing otherwise impacting government or business activity. 

> The attribution problem, however,
> seems to me to arise when governments or companies find that individuals
> have not respected their rights, or when individuals have not respected
> other individuals.

Correct. 

> Because the attribution problem in this sense occurs
> in a "reverse setting" (individual -> individual or individual ->
> government/company settings rather than government/company -> individual
> settings), I'd be cautious to include it in RFC8280.

I don’t following how the atypical nature of the "legal remedy” human right makes it any less important than other human rights or warrants its exclusion from aspects that need to be considered by protocol/architecture designers.  In fact, the less obvious relationship between attribution and ability to support the legal remedy human right would argue that it’s likely more important that it be included, less it be readily overlooked by designers when striving to strike an appropriate balance in these areas. 

Thanks! 
/John

p.s. Disclaimer:  my views alone - this message composed of 100% recycled electrons.