Re: Why /64

Jeroen Massar <jeroen@massar.ch> Mon, 28 October 2013 08:46 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 7E5B911E823F for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 019Pejus7eIe for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:46:07 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id C63D211E8237 for <ipv6@ietf.org>; Mon, 28 Oct 2013 01:46:04 -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 06BE8801C2A2; Mon, 28 Oct 2013 09:45:56 +0100 (CET)
Message-ID: <526E244B.1030103@massar.ch>
Date: Mon, 28 Oct 2013 09:46:03 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Wuyts Carl <Carl.Wuyts@technicolor.com>, Octavio Alvarez <alvarezp@alvarezp.ods.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> <526D3706.5070409@alvarezp.ods.org> <526E1F5A.2070901@massar.ch> <3135C2851EB6764BACEF35D8B495596806FAC25D4E@MOPESMBX01.eu.thmulti.com>
In-Reply-To: <3135C2851EB6764BACEF35D8B495596806FAC25D4E@MOPESMBX01.eu.thmulti.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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: Mon, 28 Oct 2013 08:46:09 -0000

On 2013-10-28 09:28, Wuyts Carl wrote:
> +1 for the /64 on the link and /48 for enterprise, 
> 
> but "at least" a /56 for home (with /60 too tiny) ??
> Can you elaborate on why you would need more than 4 bits subnets @ home?

Because I am one of the examples where I have, at home, already have
more than 16 VLANs at home.

But I might be special, I can only assume several other people here have
similar large home networks. I have so many VLANs as I like things in
separate networks, many do not even get Internet connectivity but they
are globally addressable. Note that things go very quickly when you have
things like IPv6 connected lightbulbs; though these are in a VLAN per
room so that I can send a multicast message to that VLAN and turn them
all on/off etc in one go.

The original point of the /48 was that nobody should have to bother
thinking about bits as there is enough space.

Clearly some ISPs see some scaling issues inside their network and thus
think that /56's solve that. Hence why ARIN at first then changed that
limit.

One routing slot though is still one routing slot, not more, thus if it
is a /56 or a /48 should not matter.

I am quite fine with a /56 for home users, it definitely works for me
and thus should for really everybody else in a home network.

But enterprises/companies should per default get a /48 per site so that
it is always the same and they can at least number-plan wise renumber
easily.

Hence the /64 link (autoconfig is great), /56 for enter home and /48 for
companies.

Greets,
 Jeroen


PS: one problem with the 'you get a /48' etc is that some ISPs steal the
first /64 for the uplink, some others do not. Hence why if one is doing
a network plan skip the first /64 as it will save some pain if you ever
switch. (Though it would just mean changing one VLAN to other bits).