Re: Why /64

Jeroen Massar <jeroen@massar.ch> Mon, 28 October 2013 08:35 UTC

Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73FEA11E822A for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:35:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.908
X-Spam-Level:
X-Spam-Status: No, score=-4.908 tagged_above=-999 required=5 tests=[AWL=1.691, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qzDwg7YWPzw4 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:35:19 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [78.47.209.234]) by ietfa.amsl.com (Postfix) with ESMTP id 9E4E011E8141 for <ipv6@ietf.org>; Mon, 28 Oct 2013 01:35:17 -0700 (PDT)
Received: from kami.ch.unfix.org (kami.ch.unfix.org [IPv6:2001:1620:f42:99:7256:81ff:fea5:2925]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 2DF49801C2A2; Mon, 28 Oct 2013 09:35:10 +0100 (CET)
Message-ID: <526E21C5.9080707@massar.ch>
Date: Mon, 28 Oct 2013 09:35:17 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: trejrco@gmail.com, "<ipv6@ietf.org>" <ipv6@ietf.org>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <CAKD1Yr0_anudWNpWRkvMGvD_pvyEscnuqEsPUy4YNm3e9Hue9g@mail.gmail.com> <CAPv4CP9k_J2GCOFhTCBz3U-nQmCWSjc4nceexaWwYZ-nDMpJmw@mail.gmail.com> <526D0F47.5040803@massar.ch> <CALOgxGaoB_u+br5bpyVu-A0w8vD=QjYkrzaPqYrrhtPK=z6BEw@mail.gmail.com>
In-Reply-To: <CALOgxGaoB_u+br5bpyVu-A0w8vD=QjYkrzaPqYrrhtPK=z6BEw@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Oct 2013 08:35:24 -0000

On 2013-10-27 20:04, TJ wrote:
>     >>> IMHO big nonsense. The company (amongst many others!) you work for
>     > uses amongst others cookies to track their people,
>     >>
>     >> Not sure we want to get into that argument here, but
>     >
>     > I _don't_ want to get into it here but I want to briefly support
>     Lorenzo
>     > on privacy.  Privacy through controlling tracking of an IP address is
>     > very different in mechanism and result from higher layer end-to-end
>     > privacy.
> 
> 
> First off, ++1 to Lorenzo on all counts (and Scott, Karl).

You can +1 without facts or any backing details, but the fun thing is,
it is no difference at all: privacy addresses do not make you "private"
in any way or form.


The only thing higher levels gives the adversary is a easier detection
and correlation. But unless you have exactly the same packet signature
and you are hitting the same sites as other people in your /64 or /48
you are unique.

Please note that a IPv6 Privacy Address is for a period of time, not per
application (at least I have not seen an OS do that yet, it could, but
they do not).

As such, when your HTTP browser goes to a site, that IP address is
identified as you; then anything else goes to another site, and voila,
they know that that connection is also related to you. Then your privacy
time window expires, you connect to that second site again, which is not
HTTP, but as you have been there just a bit ago, there is a high chance
that that is still you.

>     It does not matter if you have 1 IPv4 address with 2000 people behind
>     it, or 1 /48 with 2000 people behind it.
> 
>     The algorithms to de-anonimize and differentiate between the real hosts
>     behind them exist.
> 
>     Cookies are one way to do that, complete browser profiles or other
>     differences in the client, be that the tcp stack level another. For
>     other protocols it is all much easier as they are typically already
>     authenticated anyway or have other bits.
> 
> 
> 
> Having said that, FWIW - I partially disagree with Jeron here - it does
> matter.

With what exact part do you disagree and what part does matter?


> A user can have browser extensions, multiple browsers (or
> mutliple VMs with different OSes) and have a fairly good level of
> privacy if so desires - as long as the underlying L3 provisioned does
> not prevent it.  Is may not be exactly mainstream / commonplace, but not
> uncommon enough to ignore (IMHO) either.

Even though that would give you separate addresses and would initially
give that user separate identities that are being tracked, that user is
still coming out of the same /64 or /48.

Thus on the IP level indeed it initially looks like multiple users. But
as various organizations are pretty good at estimating amount of users
in a location, they can easily guess that it is the same person anyway.


I'll state again: if you want privacy use a mixnet, eg Tor.
(and even then you are exposing all your random bits, thus beware what
protocols and tools you use)

Greets,
 Jeroen