IETF Logo Mail Archive

Re: [v6ops] Google Alert - IPv6

Dave O'Reilly <rfc@daveor.com> Thu, 02 November 2017 17:07 UTC

Return-Path: <rfc@daveor.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 80C1813F79E for <v6ops@ietfa.amsl.com>; Thu, 2 Nov 2017 10:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=daveor.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 3z6HUfEPOYvr for <v6ops@ietfa.amsl.com>; Thu, 2 Nov 2017 10:07:16 -0700 (PDT)
Received: from vps.ftrsolutions.com (vps.ftrsolutions.com [5.77.39.21]) (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 37FA913F7B0 for <v6ops@ietf.org>; Thu, 2 Nov 2017 10:07:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=daveor.com; s=default; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date: In-Reply-To:From:Subject:Mime-Version:Content-Type:Sender:Reply-To:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=kGjNHa55kUR9iO/B/Cmmbx7yaP6SV/b+E+BNDkoaIDY=; b=Bxm5pXIgDgPa+Yp6JEK7jBv1my IVRRCYoR/Q2cx/33VMw+EGXiEhZb7wzp6ChHMQiFadGcGpHon6PG7c0l+sjJxEFFjCqLRXbz2vTYK 3Ag8iRehl0tuwQ3kZahHm4XXuHdcf9KdknZfvEGibvB/sxTzCYayGg5UPnYnrDW0s0jc=;
Received: from [83.103.212.135] (port=62276 helo=[172.16.102.121]) by vps.ftrsolutions.com with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.89) (envelope-from <rfc@daveor.com>) id 1eAIxQ-0002nG-Pa; Thu, 02 Nov 2017 17:07:08 +0000
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Dave O'Reilly <rfc@daveor.com>
In-Reply-To: <F0990C2F-0626-4416-AA5D-1AAE41C24510@gmail.com>
Date: Thu, 02 Nov 2017 17:07:09 +0000
Cc: Mark Smith <markzzzsmith@gmail.com>, Tom Herbert <tom@herbertland.com>, Tore Anderson <tore@fud.no>, v6ops list <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F358557D-F8B4-4EE6-B6ED-51F2BDCF0B6C@daveor.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>
To: DY Kim <dykim6@gmail.com>
X-Mailer: Apple Mail (2.3124)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - vps.ftrsolutions.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - daveor.com
X-Get-Message-Sender-Via: vps.ftrsolutions.com: authenticated_id: dave@daveor.com
X-Authenticated-Sender: vps.ftrsolutions.com: dave@daveor.com
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/OeDnvsGIe-B0qKhoUcT2rKuzTWA>
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: Thu, 02 Nov 2017 17:07:25 -0000

All sorts of scenarios could still arise to challenge that assumption. For instance, a person could be forced to enter their credentials under duress. If you need to establish that a person was using a device at a particular time “beyond a reasonable doubt” you really need something like a statement from them that they were the only person to ever use their device and/or a statement that they had it in their possession at a particular time (i.e. wasn’t lost or stolen). All pretty standard stuff from a law enforcement point of view. 

That is all, of course, presuming you can associate an IP address with a specific device (you may have seen the recently published Internet Draft on crime attribution in cases involving large-scale IP address sharing :-))

daveor

> On 1 Nov 2017, at 01:47, 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.
>

v2.23.0 | Report a Bug | By Email