Re: [v6ops] Google Alert - IPv6

Fred Baker <fredbaker.ietf@gmail.com> Wed, 01 November 2017 01:59 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 8706A13F418 for <v6ops@ietfa.amsl.com>; Tue, 31 Oct 2017 18:59:33 -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 iq-ZRQ43UJdd for <v6ops@ietfa.amsl.com>; Tue, 31 Oct 2017 18:59:31 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 9477013ADF6 for <v6ops@ietf.org>; Tue, 31 Oct 2017 18:59:31 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id r196so2257657wmf.2 for <v6ops@ietf.org>; Tue, 31 Oct 2017 18:59:31 -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=hCrBsjYxXmR4vjnY4m3AxpxYwVaIZxU7rSmPQSaXdMs=; b=n4a0g1kI2R2VlDRK/GBt7kk24t/oayP6gCDQTfZ63k2qucnS8Wsm9+UR/ecSQBI2MQ U6850a5Lnf/UTiIXuGkjPOKwzjixXs4QIMGIzQKsF9iR5+Unm61pwxW7rQljSEyZXAXO tuHGWO+pdvSh199L0/GXZfD/kzt8LmX/HYPM/IxrMLMKUC3Q8QxBlC0jwbp4Ln/WsQv4 itASJ7h2Brmzq197W5LYYx94wr5ufKVfEFnP9cwFIUNakd4cS7XmCd+7eWURvew0IGxs A2aodvO1qIpBOjMYsWaZBkbbkwlEK+DVgWGK6jDmZKy4M4MXIORQmejrh0JCTmSl6YSD WWnw==
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=hCrBsjYxXmR4vjnY4m3AxpxYwVaIZxU7rSmPQSaXdMs=; b=YIw52rQr76nguDODX+jsMl1D9/4rdRE92tXTtZ38lLe0d06WYWVMzm1NPnvGJJHjBQ xFov4bf3Eecvx3Xwe3skaW3i6Pg35hA/CAHJXdHNJ09v/1pq0ourSDEdzivMGXrOiRc5 EeBaOwRQ7VmSH/xsif+gB1fI7mYmhYci+KM0C8/aXwT8XJ59HhqRFUFa7MVJFbBT19m4 i96mmZshDXZnJ+/lzMrj8cTm4T8J3M+xtnIxxqcEmd0nacw1C8UsDHxnHOEJ6OY/XXEJ 0BkKwI3vF8Xr6KD8tUunhGEPECAg6UVsJZLVRGQuQZdvuOmZwQz8O6U4oWiiNMU96iX6 H9cQ==
X-Gm-Message-State: AMCzsaXwtrJOnqBxfV5Q/QV32bjx9z4aGzINWH8b+SfKvTGXHRgINnY2 k1O/bCAUFrJ2mO7pSkBu28Y=
X-Google-Smtp-Source: ABhQp+Rl6z90AiF/+67Zr5gU2nIkih8TOkOLWb3v18kruIPLm5d28ANFmC7dKLq/NTs4d6hkimynsQ==
X-Received: by 10.28.8.145 with SMTP id 139mr3541202wmi.115.1509501570150; Tue, 31 Oct 2017 18:59:30 -0700 (PDT)
Received: from 207.66.20.149.in-addr.arpa (207.66.20.149.in-addr.arpa. [149.20.66.207]) by smtp.gmail.com with ESMTPSA id p28sm12114135wmf.2.2017.10.31.18.59.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Oct 2017 18:59:29 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <A9FAF661-C5DB-4EE2-8175-56FF50792B27@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_BE6FF904-365D-4D5C-82FA-16F425D8AB92"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Date: Wed, 01 Nov 2017 05:59:19 +0400
In-Reply-To: <F0990C2F-0626-4416-AA5D-1AAE41C24510@gmail.com>
Cc: Mark Smith <markzzzsmith@gmail.com>, v6ops list <v6ops@ietf.org>, Tore Anderson <tore@fud.no>, Dave O'Reilly <rfc@daveor.com>
To: DY Kim <dykim6@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> <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> <CAO42Z2yXH0sPJYXJ6Nrq0B=UaDK4mC1R2Tds1tFQeBhuVh5meg@mail.gmail.com> <F0990C2F-0626-4416-AA5D-1AAE41C24510@gmail.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/iEM34VdV17V5lmUZeK8JAyGkisA>
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: Wed, 01 Nov 2017 01:59:33 -0000

I think that misses the point. If you identify yourself to the phone, it knows that you are holding it. You might then pass it to someone else, who uses it. The phone doesn't know who is holding it, only that you unlocked it.

But that's not the point. The point is that someone *else* observing your phone's traffic or location data makes the assumption that the phone is with or being used by you. You didn't present your fingerprint to them; they are observing after the fact and making inferences.

Now, as an investigative tool, that makes sense - in a high percentage of cases, the person using your phone is you. So they can use that as a working assumption in the conduct of an investigation. But the working assumption doesn't prove anything, it only gives hints that have to be further verified to turn into proof.

> On Nov 1, 2017, at 5:47 AM, DY Kim <dykim6@gmail.com> wrote:
> 
> When unlocking your smart phone, you might use the ‘finger touch’ identification, in which case the device use might identify the individual.
> 
> When a password or swipe pattern is used, the association might be weaker since those could be stolen.
> 
> ---
> DY
> 
>> On 1 Nov 2017, at 10:42, Mark Smith <markzzzsmith@gmail.com> wrote:
>> 
>> There really needs to be something else that supports or proves use of a device other than an assumption that an IP address is tightly coupled to a device's owner, and therefore all actions associated with an IP address are those of the device's owner.
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops