Re: Why /64

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 28 October 2013 11:18 UTC

Return-Path: <alexandru.petrescu@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 5366F11E816D for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 04:18:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.294
X-Spam-Level:
X-Spam-Status: No, score=-10.294 tagged_above=-999 required=5 tests=[AWL=-0.045, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
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 9ZebybwktxaY for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 04:18:33 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id 7548D11E81E3 for <ipv6@ietf.org>; Mon, 28 Oct 2013 04:18:30 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r9SBIRTU016868 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ipv6@ietf.org>; Mon, 28 Oct 2013 12:18:27 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9SBIR63025610 for <ipv6@ietf.org>; Mon, 28 Oct 2013 12:18:27 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r9SBIQXv006665 for <ipv6@ietf.org>; Mon, 28 Oct 2013 12:18:27 +0100
Message-ID: <526E4803.8020808@gmail.com>
Date: Mon, 28 Oct 2013 12:18:27 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: 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> <526D3706.5070409@alvarezp.ods.org> <526E1F5A.2070901@massar.ch> <3135C2851EB6764BACEF35D8B495596806FAC25D4E@MOPESMBX01.eu.thmulti.com> <1E6580AB-7010-4E45-8903-6126E82A9772@steffann.nl>
In-Reply-To: <1E6580AB-7010-4E45-8903-6126E82A9772@steffann.nl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
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 11:18:38 -0000

Le 28/10/2013 10:22, Sander Steffann a écrit :
> Hi Carl,
>
>> +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?
>
> Today 4 bits can be enough for simple cases with i.e. a home
> network, a guest network and maybe a home-office network. But IPv6 is
> meant to last for some time, and in the (near) future it is not that
> difficult to see networks for lighting and sensors (i.e. 6lowPAN)
> being added to that.

I agree.

And I would add another aspect.  One could hardly imagine that a single
subnet (any subnet) could hold together 2^64 nodes.  That is a matter of
link-layer technology.  I think not even the largest single subnet
switch/vlan-based office networks or datacenter would approach that number.

(a single IEEE subnet is one where link-scope link-layer multicast works
across, and IP datagrams are not decremented their Hop Limit when
transmitted through).

Alex

> And I'm not being very creative right now ;-)  Besides: home users
> often don't understand the different between a wireless router and an
> access point, so they tend to daisy-chain them. In IPv4 this would
> cause multiple layers of NAT, in IPv6 you need more subnets.
>
> PS: Look at DT's plans, they are giving multiple /56s to each home.
> One for best-effort internet access, one for voice, one for
> streaming audio/video, etc. See
> https://ripe67.ripe.net/presentations/131-ripe2-2.pdf. I'm not
> saying this is the way everybody should deploy IPv6, but it is an
> example of using IPv6 address space in a different way.
>
> Cheers, Sander
>
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>