Re: [v6ops] [SUSPECTED SPAM] Google Alert - IPv6

Fred Baker <fredbaker.ietf@gmail.com> Mon, 30 October 2017 02:41 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2298013FD60 for <v6ops@ietfa.amsl.com>; Sun, 29 Oct 2017 19:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, 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 Kw9mNSU6I-UD for <v6ops@ietfa.amsl.com>; Sun, 29 Oct 2017 19:41:28 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 03CE113FD67 for <v6ops@ietf.org>; Sun, 29 Oct 2017 19:41:28 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id r196so13438228wmf.2 for <v6ops@ietf.org>; Sun, 29 Oct 2017 19:41:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Oz7MaTkkdeGB1hfWBU7NQgiFfMAatO2jN7f38wZbVk0=; b=OwkY6/Y8ed8EKC3J9WyJytWVUKuvXmPADc14GYlhO9ytKOmjnSX2SGCY13zv5zoouq vign9oAz2i8qvqpdM3Id1PX8PZcwgQcwr3IwlFlayGZJnyfCN9CRzbTMZpp9IHQCfNEP SlhXWjNJqsvMuBcWZaUxRz7q7BJcrmtupcaSQsH0d0miRST9fxQyx71bdImlBRSjqwnS v4Byk2cFkQFYFpl2jDNLIJ8ez8XS0cMe+XGts/Q9p1V6eTYXqi/9+3IdLLVHIbhrcbzP NrSCc7DOIhVfdwBr0Qki3Uwv3Bt2rdsNX4Z+1LaJMMSVHNgVIdx/6z1dSyWqmRtD3Rwe gsPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Oz7MaTkkdeGB1hfWBU7NQgiFfMAatO2jN7f38wZbVk0=; b=ewGfWrejTYy/cUV+63OSzDGftKzDaqJCyXTEbVykHWEOFe6/9NIGhJrddFyWiPO0Ir h+/F+FOvwVNc+ThC4LIjE4W07sjjo5K36vq6WpYCcDveSTH7A4nVyNnq6quECRNH88YV ZTLTlXLumlxmZekz0kiB510kQ9MNqHStZTi3ljwK2ghzKJT5swDrZ3iPyqwlCEfvFRgi YJHmtmXBXtTieZeXOJeQYY3AwfQ+m4/kJz9q7Ir1vKBfDXTJ1/agx4h1dq2HL/yHtcF2 96F5NqHQXh5kgxxOZWHdwXksxFTMOgpuws0f91Gw9xPsIrLLN9BR51+cjlGjEaaK2nVq 8ZYw==
X-Gm-Message-State: AMCzsaXFwKi+iirDc34j/ta+aMnoJYiDgbVghe9XnhBt58/3gsjFCjzq 52uhTKDVSeBDVuDjSFmCUZ3oYGkc
X-Google-Smtp-Source: ABhQp+RR7HD1pKuwXjm/JN35jBg2u+lZB4U24hrQVotjpOGtr4An1rwSupoY9TgtufuyHzTwcbU4Tw==
X-Received: by 10.28.145.196 with SMTP id t187mr1127244wmd.119.1509331286505; Sun, 29 Oct 2017 19:41:26 -0700 (PDT)
Received: from 208.66.20.149.in-addr.arpa (208.66.20.149.in-addr.arpa. [149.20.66.208]) by smtp.gmail.com with ESMTPSA id p200sm3839227wmd.9.2017.10.29.19.41.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 29 Oct 2017 19:41:25 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <1A0AE76A-FA3C-4BDE-B8D9-C8D2E060A8A8@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E5BB2ED1-C738-4829-845C-2CD32843AC30"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Date: Mon, 30 Oct 2017 06:41:17 +0400
In-Reply-To: <CAO42Z2yW1SGhmcYQNgJk35_ua7nu9LRGLv0_ChC=EavwfydnQA@mail.gmail.com>
Cc: Dave O'Reilly <rfc@daveor.com>, Tore Anderson <tore@fud.no>, "v6ops@ietf.org" <v6ops@ietf.org>
To: Mark Smith <markzzzsmith@gmail.com>
References: <f403045ef57ac52962055bd88b84@google.com> <20395E98-DA55-447F-BEFE-CB581A88BB78@gmail.com> <alpine.DEB.2.20.1710190655260.31961@uplift.swm.pp.se> <20171019083506.6627a166@echo.ms.redpill-linpro.com> <alpine.DEB.2.20.1710190856530.31961@uplift.swm.pp.se> <787AE7BB302AE849A7480A190F8B93300A056EB5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CAHw9_iLWAMexrfXwsdB8duGa5ueJMofqVRqNck6DeOzA=KChqA@mail.gmail.com> <C4E37677-A2FB-49F8-B362-C29B28DFD570@daveor.com> <D618D79F.8AA1A%lee@asgard.org> <22C655A9-AE02-4885-98B5-7515C49E7F2B@employees.org> <B20ECDCB-1EFD-4265-BE13-5AE1E92335AE@gmail.com> <95274753-7241-47DE-B463-0341248FAE38@employees.org> <5FA44821-D6C2-4A9C-A1A5-59BECB65B4F4@gmail.com> <D4975FFD-0A2A-49C7-BF91-9EE18429E197@daveor.com> <CAO42Z2yW1SGhmcYQNgJk35_ua7nu9LRGLv0_ChC=EavwfydnQA@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/5xt9NcZMi6j4pA9yEFGa0UmUScE>
Subject: Re: [v6ops] [SUSPECTED SPAM] Google Alert - IPv6
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 02:41:30 -0000


> On Oct 29, 2017, at 11:48 PM, Mark Smith <markzzzsmith@gmail.com> wrote:
> 
> Geoff Huston's article on
> 
> Metadata Retention and the Internet
> 
> https://telsoc.org/ajtde/2015-04-v3-n1/a4
> 
> might be of interest.
> 
> "The Metadata Retention measures being considered in Australia make some sweeping assumptions about the semantics of IP addresses and their association with individual subscribers to the Internet. But are these assumptions warranted?"

In that context, the European Data Retention Directive (which has now been struck down by the European Privacy Court) and the activities by the "Five Eyes" in that regard, notably the US NSA, have been very much about metadata. I asked a Dutch agency representative once what their reason for lawful intercept in general and metadata capture specifically was, and he indicated "mapping criminal networks". They wanted to determine who spoke with whom, with a view to identifying members of a community, presumably an evil community.

I note that the European Privacy Court has (apparently) specified that an IP address is "Individually Identifiable Information", the kind of thing that might be discussed in https://tools.ietf.org/html/rfc7721. I have asked repeatedly what privacy folks think might be an IID below the application layer, and that is the one thing they have come up with. On the point, I would argue that data of that type is not *identification*, but it might be possible to correlate it with other information due to operational practice. To my mind, stomping out correlations is a game of whack-a-mole; someone that desperately wants to find a correlation will probably find something that mostly works for their purposes, even if they have to discard spurious correlations to do so. In my view, that's what we see here: we might be able to correlate an IP address with a computer or subscriber, but we can't stop people in a business or family from using each other's computers. It is at best an investigative tool, not proof of something in particular.