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

farzaneh badii <farzaneh.badii@gmail.com> Wed, 12 June 2019 19:42 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 BCC24120158 for <hrpc@ietfa.amsl.com>; Wed, 12 Jun 2019 12:42:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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=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 dy7RTfs7O1WR for <hrpc@ietfa.amsl.com>; Wed, 12 Jun 2019 12:42:53 -0700 (PDT)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (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 87F46120159 for <hrpc@irtf.org>; Wed, 12 Jun 2019 12:42:39 -0700 (PDT)
Received: by mail-qt1-x830.google.com with SMTP id h21so19798461qtn.13 for <hrpc@irtf.org>; Wed, 12 Jun 2019 12:42:39 -0700 (PDT)
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=zML6VnmWx0qF6Vdh/WFTLc5z0tGMThtx1OPqQDVz3h8=; b=jNmonJ4bRaIvvoL0dh3juqC74wIQi+NQCnYVODCg5bZ/BQ4HB5RJgVUY8NWnRmKQhj 6ZamL7BK0ENN2ro4QCBYkvsQ7gpPtSkyeEvaPOXqoC6gXDh91lbxxvJ+n8fnfJ8L6pqp KIsqGAYb1fOtYhcraMq0jhWqe0F35GVrKuocMLHv1aagGC6JY5Yj8ZSiDPTsmM7kNtZk XPwDYIKLft6bfX4LBLPtbd5xFAg2DT1ySHHuN5CBCO78E8PkvT3cKOcDT3XFBW8fh5Qf JmUnM85LCAIQ2MRNcWwbiGLTJwSqDO7TgTZ8Q/wjUY45Abx0cSY4pG5KTC7tUE7a4En8 1U3A==
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=zML6VnmWx0qF6Vdh/WFTLc5z0tGMThtx1OPqQDVz3h8=; b=CeVThrYq40tNdGQNPIHiM0jBMusX6LnvEdEaIR/I6ZI2BGi0Nv7bt1wcelRt12VbE2 U6MBNpfnvdIQEeqfmawV0t3HqpezDtvZSNfzve5/xXRTJqVURaqggcRaBdMBWbPWeuT8 epUJhS82w8fjZoDxq12lA0i07/fvZEzZ+VSvExSvvRuQaZf3A7Jmr2g140XHg1IRtg4X juOY9dPvk68pT46LI91iIiRLg6jsFp66uYajJtC+bQt9SwMv5BoFb8mZ5LCv+mKzSf/J EylHW9cGAE3IAxtKXUWVMHhNS+HSkmovRpeQ+O6a5Wrg6K2lYk0UK7zdpMtTctFnO1fx ouwQ==
X-Gm-Message-State: APjAAAXqA5fiqKn9LVEaRb6fIBb9IB95HlQZg1qp2F7zLT18zpIkFfgF c84Nsl7XOLmhU4c1BCTs4Gv0hTg37rxUAj3S6H0=
X-Google-Smtp-Source: APXvYqwVApwsYEsPYcBB5gh9nvQ8jj53d5NlgJc2JlFJDNN4p1SXKESmdWHjEawv6/G3cTuHZL5HQchiYn/bo0pHn7w=
X-Received: by 2002:a0c:b659:: with SMTP id q25mr249576qvf.29.1560368558495; Wed, 12 Jun 2019 12:42:38 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <2347EC29-4F1B-4A67-9C96-632006CD2311@fugue.com>
From: farzaneh badii <farzaneh.badii@gmail.com>
Date: Wed, 12 Jun 2019 15:42:12 -0400
Message-ID: <CAN1qJvA_ouuxgtJGaOY9ZrFU0eoiyEZ-EWz2fhKaBaAEhDrnWw@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: John Curran <jcurran@istaff.org>, Niels ten Oever <mail@nielstenoever.net>, hrpc@irtf.org, Amelia Andersdotter <amelia@article19.org>
Content-Type: multipart/alternative; boundary="000000000000a5e071058b259db7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/qc2b8BDS1ZFblFv6mP_QJsGdx6w>
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 19:42:57 -0000

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.

Explanation: John's suggestions (including it as is) will have (in my
opinion)many negative consequences.  it is not clear what we mean by
"harm".is it a cybersecurity issue? Or is it physical harm on others?   it
is not clear what is meant by "attribution". Is it about identification of
a person? A network?   what do we mean by legal remedy and access to legal
remedy? The document John points to about attribution (the BCP) has been
criticized before.
https://tools.ietf.org/html/draft-andersdotter-intarea-update-to-rfc6302-00 so
there are controversies surrounding this issue, and we have not discussed
whether what John is arguing is a human right issue that we should consider
in HRPC. And usage of the term "public safety" (which is not in John's
suggested text but in RFC 6302) is ambiguous. By public safety, do we mean
law enforcement queries? what sort of queries? fighting with cybercrime? or
street crime? consumer protection?

 This is actually an interesting case to look at and see how RFC 6302 been
implemented and how it has helped "public safety" queries. Maybe it will
lead us to revisit RFC 6302 :)






Farzaneh


On Wed, Jun 12, 2019 at 2:06 PM Ted Lemon <mellon@fugue.com> wrote:

> On Jun 12, 2019, at 1:48 PM, farzaneh badii <farzaneh.badii@gmail.com>
> wrote:
>
> Frankly, John, what you are suggesting is outrageous.
>
>
> I’m having trouble seeing what John has said that’s outrageous.   Rather
> than simply saying it’s outrageous and hoping that we will see what you
> mean, could you please tell us what you think he has said that is
> outrageous, and what about it is outrageous?   I say “think he has said”
> because it’s also possible that there is a misunderstanding here, and
> that’s why I’m not seeing it.
>
>
>