Re: Why /64

Lorenzo Colitti <lorenzo@google.com> Sun, 27 October 2013 18:06 UTC

Return-Path: <lorenzo@google.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 B240311E81B1 for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 11:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[AWL=0.080, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 JD6SBvShZERy for <ipv6@ietfa.amsl.com>; Sun, 27 Oct 2013 11:06:39 -0700 (PDT)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 16CBC11E80E7 for <ipv6@ietf.org>; Sun, 27 Oct 2013 11:06:37 -0700 (PDT)
Received: by mail-ie0-f169.google.com with SMTP id ar20so10093826iec.28 for <ipv6@ietf.org>; Sun, 27 Oct 2013 11:06:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Psx1ek1TUuIJdQCkcbh1XlgMAtZtoBvC4WxJWxSq9kw=; b=MGXQX6ja9AOMc98ajYUUyozunMwHnxq44FudUcK0kklbhMiujxfrH5WvlVxoYCWBxs kQxYmgf/Ngh3dIjqTkFO8Mt5mi526us+aP2A9LwloekUP2bCin8zpz+909imsYa9P/C+ CQe1yOm9Kl5Q60kgokdrl30Tt/3oafXHH3M+7+e0VaZYRaDy/JsgPrBa3xb7aJk4ioOr f5qNss2KZXzaAUVwG1FM8HI58W4n9RUcmBVD5bGTruwHwhi45/JwtgFA+EDKDVoxXyDg FFntSRG5OT7wVbQULS7FTKuP3l2L1RpYeOO60t7Wshhe1v8ZRHWr07d17rjAqImaJJKO Z7GQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Psx1ek1TUuIJdQCkcbh1XlgMAtZtoBvC4WxJWxSq9kw=; b=M3xaIbFV/uvHP4poHQ07kmTZl8W8MIIfHgcOjgT87pPvZmB+203TYdFk/4GAlzxD32 /V8ACdlMOj3PWdZ6pAPb3tavjlkL6DtEgzgoG94e3fVwZBn5i+1fq+RbkWzwdW7Zb/tN L3lGru8Fae3/jDyg0IMz2DMuqLzfGi8+oHvXDKtGZqC+53Yf6x6yTwUGCjv9AiiMYFYq Cc6kFIGOhjs7Av2bIbOy7zfdviTU9cq5E8+/ns2dlVVDF2Wk8Reu+Hr3FQVx+9YF3Ld5 gSK1mWB9B2OgF/b8MHDJJ1fe189xh57yG9FXx6CWYmdFhOA5Qa73B6SCc9ueWteMTYQT S/kw==
X-Gm-Message-State: ALoCoQmd20Tz2oXllgcaCidHUGweqFj+tYe9PqsnQJ5B4jBxamFurdRvAcpi2RNoGGh5SwMjfNRX8I2ZpCJzQN0LeH7wgsCVbl5n99OguUPkSNo1hLkdE5eFVqsIgVI9sJ4lNSjQGjH83ahLTIGO1/ab2voiBj2x9LA8qowZvS68yn/uR/4nNTrj+A0LrdmuRABD2EzYqoQN
X-Received: by 10.50.22.101 with SMTP id c5mr5893523igf.17.1382897196428; Sun, 27 Oct 2013 11:06:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.106 with HTTP; Sun, 27 Oct 2013 11:06:16 -0700 (PDT)
In-Reply-To: <526D3AE2.2020300@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> <526CE821.1000900@massar.ch> <CAKD1Yr138KfSo_g5mr-5r4-H8Fxrk0GUnDLy0nLHZr1z6PC_cg@mail.gmail.com> <526D3AE2.2020300@massar.ch>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 28 Oct 2013 03:06:16 +0900
Message-ID: <CAKD1Yr1DnHrkXmYhGc-mSg4W94=-=DLizm0iR18hPCa=yw3Pdw@mail.gmail.com>
Subject: Re: Why /64
To: Jeroen Massar <jeroen@massar.ch>
Content-Type: multipart/alternative; boundary="047d7b10c9cb27a5df04e9bcd857"
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>
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: Sun, 27 Oct 2013 18:06:42 -0000

On Mon, Oct 28, 2013 at 1:10 AM, Jeroen Massar <jeroen@massar.ch> wrote:

> The point that I am trying to make, but the one you do not want to hear,
> is that "IPv6 privacy" does not exist


Perhaps, but let's not argue that on this thread, which is about subnet
sizes.


> >     Amongst others: http://www.ipsidixit.net/2010/03/24/239/ one of many
> >     articles on this for free.fr <http://free.fr> (the "largest IPv6
> >     native deployment").
> >
> >
> > Since forever Free.fr has been handing out /60 to all its customers
>
> Hence why the above linked article exists and many other similar ones.
>

The article exists because the writer wanted to put a firewall between the
ISP router and the other machines. You can do that with DHCPv6 PD but not
with native routing (just like you can't do that in IPv4 without NAT). It
doesn't support the assertion that free.fr assigns single IPv6 addresses to
their users.

For free.fr docs on this:

http://ripe58.ripe.net/content/presentations/ipv6-free.pdf (addressing
plan, mentions /60 per user)
http://aide.ma-freebox.fr/ipv6.html (look at the screenshots, they even
allow you to statically route some of your /64s to nexthops you specify)


> IPv6 (this whole thread :) is not limited to a single /128 either, but
> this is how it is being deployed in the wide by various ISPs (cheap
> hosters are a primary example, but there are also consumer ISPs, eg
> Liberty Global mentioned above) who do.
>

Where did you get the information that unitymedia only provide a single
/128? http://www.unitymediakabelbwforum.de/viewtopic.php?f=53&t=23981 and
http://www.youtube.com/watch?v=K0hT1PpfxxQ suggests the CPE gets a /57.


> Note that I am pointing out documentation that is available. That these
> authoritative sources are out of date not much I can do about.
>

Of course you can't do anything about out-of-date documentation, but please
do a little more research before making confident statements based on said
out-of-date documentation. People might believe you, and they'd be wrong.

Specifically, I think the "quite a few [ISPs] give exactly 1 IPv6 address
to their users" statement is not true in the case of mainstream residential
ISPs - I think they all provide at least a /64, and more usually at least a
/60.