Re: [v6ops] Google Alert - IPv6

Ole Troan <otroan@employees.org> Mon, 30 October 2017 16:29 UTC

Return-Path: <otroan@employees.org>
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 E6EBC800A for <v6ops@ietfa.amsl.com>; Mon, 30 Oct 2017 09:29:53 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 IGIIw2HURES6 for <v6ops@ietfa.amsl.com>; Mon, 30 Oct 2017 09:29:51 -0700 (PDT)
Received: from accordion.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 534175438 for <v6ops@ietf.org>; Mon, 30 Oct 2017 09:19:42 -0700 (PDT)
Received: from [192.168.10.119] (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by accordion.employees.org (Postfix) with ESMTPSA id D9A842D5105; Mon, 30 Oct 2017 16:19:40 +0000 (UTC)
Content-Type: text/plain; charset="cp932"
Mime-Version: 1.0 (1.0)
From: Ole Troan <otroan@employees.org>
X-Mailer: iPhone Mail (15A372)
In-Reply-To: <CALx6S34=RVeM6+QaDtBwpKgk9E8eqfgcjx8=10Tja6DifVRotg@mail.gmail.com>
Date: Mon, 30 Oct 2017 17:19:38 +0100
Cc: Dave O'Reilly <rfc@daveor.com>, "v6ops@ietf.org" <v6ops@ietf.org>, Tore Anderson <tore@fud.no>
Content-Transfer-Encoding: quoted-printable
Message-Id: <810E7331-6473-472A-9DD0-21F99A37D863@employees.org>
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> <CE4906A4-E0CC-4C3F-A1F8-D2B5BED294D7@employees.org> <EDC5E9C7-F193-40CE-B21C-8E1D91E9E7E3@daveor.com> <C71D6C23-2720-403F-B655-D8156898A137@employees.org> <CALx6S37E9TN9SyMQfk3CSx9vWzjBM3bmuhvsyN0tFXGYFz9Mjw@mail.gmail.com> <ADFA3F7C-74A6-43D4-9BC8-C6F942B28BE6@employees.org> <CALx6S34=RVeM6+QaDtBwpKgk9E8eqfgcjx8=10Tja6DifVRotg@mail.gmail.com>
To: Tom Herbert <tom@herbertland.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/AyULt8GvGhQdxwffMFEWJOhHOBk>
Subject: Re: [v6ops] 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 16:29:54 -0000

Tom,

> On 30 Oct 2017, at 16:40, Tom Herbert <tom@herbertland.com> wrote:
> 
>> On Mon, Oct 30, 2017 at 7:53 AM, Ole Troan <otroan@employees.org> wrote:
>> Tom,
>> 
>>>> 
>>>> I think that's fine.
>>>> As long as you make it clear that:
>>>> - the IP address _never_ identifies an individual.
>>> 
>>> Ole,
>>> 
>>> I don't think this is something that can be part of the definition of
>>> an IP address, it's more of a desirable property of how IP addresses
>>> are assigned and used. For instance, a smartphone is given an IP
>>> address and technically identifies the host. But given that there is a
>>> likely one to one correspondence between personal device (and its
>>> address) to an individual user, the IP address of the device
>>> effectively identifies the individual or at least can be used with a
>>> little more information to do so. In this case, the IP address seems
>>> to be Personally Identifiable Information.
>> 
>> 
>> I am in no way trying to define an IP address.
>> 
>> My one and only point was that in this document one should not give the indication that an IP address by itself identifies an individual. Which revision -00 did.
>> 
>> (Sure, if the IP address leads to a single-user device with strong user authentication, there is a reasonable chance that it identifies an individual or an individual that knows who has been using it (e.g. their kids). Unless it is already owned by the NSA or a similar organisation.) Where did you interpret that as if I was trying to "define" an IP address?
> 
> It was the "_never_" part of your sentence :-). That seems to imply an
> invariant property of IPv6 addresses that could then be part of its
> definition.

Ah, I was purely talking about the draft, and therefore IPv4 addresses and I tried to include the “by itself”. :/)

Cheers 
Ole