Re: [v6ops] WGLC: draft-ietf-v6ops-unique-ipv6-prefix-per-host-02 - multiple prefixes per device

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 17 March 2017 12:05 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE7121286CA for <v6ops@ietfa.amsl.com>; Fri, 17 Mar 2017 05:05:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.332
X-Spam-Level:
X-Spam-Status: No, score=-0.332 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PUux5tPgxnEk for <v6ops@ietfa.amsl.com>; Fri, 17 Mar 2017 05:05:46 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33FD41286B1 for <v6ops@ietf.org>; Fri, 17 Mar 2017 05:05:46 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v2HC5iMQ040778 for <v6ops@ietf.org>; Fri, 17 Mar 2017 13:05:44 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 40A62202E74 for <v6ops@ietf.org>; Fri, 17 Mar 2017 13:05:44 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 37B7D202E60 for <v6ops@ietf.org>; Fri, 17 Mar 2017 13:05:44 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v2HC5hUQ011876 for <v6ops@ietf.org>; Fri, 17 Mar 2017 13:05:44 +0100
To: v6ops@ietf.org
References: <27AE6A05-C742-44BF-98E8-BFCEC72316F2@employees.org> <EF0F4950-F238-4001-BA74-D9440524BEFA@gmail.com> <634a6a12-4d82-da33-6d1d-baae2e5b2891@gmail.com> <13DA8077-91C1-4B3F-9D67-3727F546D202@employees.org> <13194a4f-aeda-63b0-0293-6bc738b068f2@gmail.com> <4D60B43B-24F9-4701-800E-13CF32CD4769@employees.org> <8fc7f3e7-7155-f184-c028-a9f6da7e97db@gmail.com> <20170316201413.GQ2367@Space.Net> <212f8258-a025-325e-badc-e7bdcc2bf5f7@gmail.com> <20170316232633.77ADD66F1D4A@rock.dv.isc.org> <20170317101306.GT2367@Space.Net>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <294476e5-0b53-c29d-0ddc-ca83ae84b5d7@gmail.com>
Date: Fri, 17 Mar 2017 13:05:35 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170317101306.GT2367@Space.Net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/rjMga9eaWwG6XFyKWK8fWd3stKc>
Subject: Re: [v6ops] WGLC: draft-ietf-v6ops-unique-ipv6-prefix-per-host-02 - multiple prefixes per device
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Mar 2017 12:05:48 -0000

Le 17/03/2017 à 11:13, Gert Doering a écrit :
> Hi,
>
> On Fri, Mar 17, 2017 at 10:26:33AM +1100, Mark Andrews wrote:
>>>
>>> Yes, one always needs cautious allocation policies. But still...
>>> /64 is not enough in the general case, with today's link-layer
>>> media and today's IPv6 stacks. (We can have the argument about
>>> tomorrow some other time. :-)
>>
>> And PD allows for a node to do multiple PD requests.  Each router
>> doesn't need a pool of prefixes to answer PD requests from.  It can
>> do a upstream request to full fill the downstream request on
>> demand.
>
> Technically, it could.  Administratively, I'm going to believe that
> when I see it - like, in a big enterprise network, individual /64s
> being routed randomly across the place because a wifi hotspot needed
>  another prefix to hand out.
>
>> A coffee shop is a site or part of a site.  That site should have
>> a /48 with 65536 /64 subnets to further allocate.  Hosts draw from
>>  that pool.  Yes, that does mean that there are lots of intra site
>>  routing entries for /64's rather than for shorter prefix lengths.
>>  That however shouldn't matter because it is not a excessive number
>>  for even the most inexpensive router to handle and they are
>> summaried as a /48 in the global routing table.  Even with a few
>> of /48 pools from different ISPs it still isn't excessive.
>
> A coffee shop has a /48 today (or a /56, given that the RIR policies
>  where changed based on extrapolations that a /48 for each SoHo
> customer connection might not be sustainable).
>
> If we suggest that hosts should "get a /48", and there a a number of
> customers in that coffee shop, then a /48-per-site is not going to be
> enough.
>
> But seriously: how many visitors of said coffee shop would need more
> than a /64?

Many visitors use smartphone-smartwatch combinations.

> Yes, I've heard about the laptop with the VMs running,

Smartphones run VMs too, not only laptops.

> in multiple hierarchical virtual networks, and such.  How many of
> those laptops exist?  100, 1000?  This is totally niche.

Even for a 100-sized niche, one needs to plan for 100 times multiple /64 
prefixes per unit.

Even for a 100-sized niche, one can't plan to use a single /64 per unit.

> Normal users want their browsing, e-mail and corporate VPN to work.

New ways dont do any browsing, email or corporate VPN.  They do 
purpose-specific messaging and project management apps.  Often they 
neeed simultaneity between multiple independent such apps - easier with VMs.

Alex

>
> Gert Doering -- NetMaster
>
>
>
> _______________________________________________ v6ops mailing list
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>