Re: Why /64

TJ <trejrco@gmail.com> Sun, 27 October 2013 19:04 UTC

Return-Path: <trejrco@gmail.com>
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 2D72011E81BE for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 12:04:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 YxxEFSeev0ky for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 12:04:29 -0700 (PDT)
Received: from mail-ve0-x233.google.com (mail-ve0-x233.google.com [IPv6:2607:f8b0:400c:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 294F111E81B1 for <ipv6@ietf.org>; Sun, 27 Oct 2013 12:04:26 -0700 (PDT)
Received: by mail-ve0-f179.google.com with SMTP id cz12so4315310veb.24 for <ipv6@ietf.org>; Sun, 27 Oct 2013 12:04:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=R0VgW1IEU/ib8vqLiNGirZ8LBtbcP4axTMarCysPPIQ=; b=fA73B18ndBNdqBK0NOGOatJdevl4lnJQFMrw0oNkEVrSLIvzsqu2DejeGUrr3EB6KV AQ/Xm+fMD4hJSljm6FKb39WGMw714fr8p+G9FHnjyrgUlM4CrKWaDH5pQxPZpFKUPsQs 8tk91CwtR85jyqRBFOMbHC9Dlvn8nmME1AT2LpjcHg9HoDIvSHtTHuay4FislNQcPWtX qaWNErdpR4Qd90vMQog6dw1zsw8RQw6F68SXNz+HuctSufeZivxL9Qegwtmsz4fg66mR iRqexhIkkR+Fn3U8JWJ7cvOCAMCidBttfrlGqv95QH3yOknvwzMurEg53PS5J8YC5fve UmcA==
X-Received: by 10.52.164.102 with SMTP id yp6mr9326376vdb.14.1382900665017; Sun, 27 Oct 2013 12:04:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.173.6 with HTTP; Sun, 27 Oct 2013 12:04:04 -0700 (PDT)
In-Reply-To: <526D0F47.5040803@massar.ch>
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>
From: TJ <trejrco@gmail.com>
Date: Sun, 27 Oct 2013 15:04:04 -0400
Message-ID: <CALOgxGaoB_u+br5bpyVu-A0w8vD=QjYkrzaPqYrrhtPK=z6BEw@mail.gmail.com>
Subject: Re: Why /64
To: "<ipv6@ietf.org>" <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c2c1eae5efe304e9bda6b0"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: trejrco@gmail.com
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: Sun, 27 Oct 2013 19:04:31 -0000

>
> >>> 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).



> 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.  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.


/TJ