IETF Logo Mail Archive

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:13 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 D1175120105 for <hrpc@ietfa.amsl.com>; Wed, 12 Jun 2019 13:13:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 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, T_SPF_PERMERROR=0.01] 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 urrLQE3xocMz for <hrpc@ietfa.amsl.com>; Wed, 12 Jun 2019 13:13:55 -0700 (PDT)
Received: from outbound1f.eu.mailhop.org (outbound1f.eu.mailhop.org [52.28.59.28]) (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 6C8DF120091 for <hrpc@irtf.org>; Wed, 12 Jun 2019 13:13:55 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1560370432; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=mtDPVRwAbDHEl1SBbaCYCO79TX3Hzz0PKuaMINXE8NR3zujt8P80Y2iTwWTuiWtpf1xzvaAUI4FPd mK5uwuGoqDUmVc3Q/lAstIKLkzKaYAmQqw87Xjm5U8ayU3ZPcchmtHJeHWOyuEqFGKXSZHGiIstCCs 9pg8Nr8k4XdCdhh+8Zbb0bEacEHY2BnjOgVH6nuG53ww/73RkIFLAZMUsP7d8i/gfI+aNuaLMHQLly k26kh4MvAd5i6YQT5trrFdPOybpgM82PSILrLdO7HWRx+t1DuS2WiTD4sosDAMKnuAxfX5q12XSxiv FcmFkB6u7UwSWv7/GUto1Yo56Vlpdkg==
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=SAwaDj4m8U4PMVbDb6v9V46mBfXH1j6wxQjpe+AyaeQ=; b=RM9ZpZlDy7/P8kpj8DxQWIQWYqcy2R8cmyqFHhrykXJKdnoHXZvsYozFNVtrputC6Gj9ig5+7zI+e Dx2+mCnA4EMAd04+MIO0xggDoQLW7M+2+O6uW/HptQ4PF8iA14KSHmgXXCZFkT2/goFdkm3ZNetmXI 73tjLw4ao+Po+p/8iZBvT+beD4oKCmX1Bh+DHs0NJStfxbDXfa1GJgJ1u0NgzgmVqwwBXKzxd0AKgj sxS4I3nC2duuL8ebux3+iFb2T17a+bvpQHZYCyGPKmdf3oOotnM0Tzq0wPyQFXHqLVqGHuhwERMSmh JESglGUuo1QJEtKnoiBtP1z1m+E+unQ==
ARC-Authentication-Results: i=1; outbound2.eu.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=SAwaDj4m8U4PMVbDb6v9V46mBfXH1j6wxQjpe+AyaeQ=; b=B6SORDTWeUM8X6XZMnouJKDzCb2mrG8KdvCiHVgqAVoqPiw7x4HIoHvgaEWh6WoWT1TVJwez17NyL IEsIL+atduC+5MAn8pY/Y4WdhfXJXQpAs2ykXpk8AHbIRqqYaB4FQaVciL2QKayEefWl49MM7chIA2 iX/vQcBOo5IbN1F2gKG+3Zj+JayWKt+N497XFlC63yvWIaAfIxtP18RBYoLk2rf9vv2J2YrypVVR3Z UGKoUW0LVVMo1RV11GI1DgI1rX7OGFm5n7rM2+rAWG0IulqLGKbqlXKWJa1fEW9vVV8XlajW9NdKNN ipWjuZzCslzfX0mXfkxWQWtay5/YJ8w==
X-MHO-RoutePath: amN1cnJhbg==
X-MHO-User: 959d93a7-8d4e-11e9-85c6-c97e5c048ed3
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 outbound2.eu.mailhop.org (Halon) with ESMTPA id 959d93a7-8d4e-11e9-85c6-c97e5c048ed3; Wed, 12 Jun 2019 20:13:48 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by geode.istaff.org (Postfix) with ESMTP id 997683BEAA4C; Wed, 12 Jun 2019 16:13:46 -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 qZL1d2Y9e5hT; Wed, 12 Jun 2019 16:13:45 -0400 (EDT)
Received: from [172.20.0.75] (unknown [65.216.233.162]) by geode.istaff.org (Postfix) with ESMTPSA id C6C9E3BEAA2B; Wed, 12 Jun 2019 16:13:45 -0400 (EDT)
From: John Curran <jcurran@istaff.org>
Message-Id: <28845DAD-58D6-4BF8-BF96-AEEE53228E79@istaff.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B694E951-5904-47DC-9FF0-364C6FECFCF6"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 12 Jun 2019 16:13:45 -0400
In-Reply-To: <CAN1qJvA_ouuxgtJGaOY9ZrFU0eoiyEZ-EWz2fhKaBaAEhDrnWw@mail.gmail.com>
Cc: Ted Lemon <mellon@fugue.com>, Niels ten Oever <mail@nielstenoever.net>, hrpc@irtf.org, Amelia Andersdotter <amelia@article19.org>
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> <2347EC29-4F1B-4A67-9C96-632006CD2311@fugue.com> <CAN1qJvA_ouuxgtJGaOY9ZrFU0eoiyEZ-EWz2fhKaBaAEhDrnWw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/RZRAhYCb2GEUyoXEitMn9AsSeYI>
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:13:58 -0000

On 12 Jun 2019, at 3:42 PM, farzaneh badii <farzaneh.badii@gmail.com> wrote:
> 
> So since John has not criticized me yet over the use of the word outrageous I hold back apologizing for using it, seems like he doesn't get offended quickly which I am thankful for. If the community wants me to apologize for the usage of this outrageous word, please let me know so that I send in my apology. 

I think it would be outrageous to seek such an apology, as your remarks were made in good faith and did not intend any harm.  

> Explanation: John's suggestions (including it as is) will have (in my opinion)many negative consequences. 

It might be helpful to elaborate somewhat on the negative consequences that you foresee – I’ll admit that the worst consequence that I've envisioned is that those protocols which intentionally preclude attribution will end up with a sentence in their HR assessment to the effect that anonymity provided by the protocol also means that parties who are harmed (via communications taking place over it) should be aware that it may be challenging to seek legal recourse against the perpetrator. 

This isn’t exactly surprising, and reflects many of the Internet protocols that we use today. 

Thanks,
/John 

p.s. Disclaimer:  my views alone, in individual serving size and not packaged for any resale.

v2.23.0 | Report a Bug | By Email