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

Fernando Gont <fgont@si6networks.com> Fri, 17 March 2017 21:04 UTC

Return-Path: <fgont@si6networks.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 0A6D012956B for <v6ops@ietfa.amsl.com>; Fri, 17 Mar 2017 14:04:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 zLEoyJxLoBfv for <v6ops@ietfa.amsl.com>; Fri, 17 Mar 2017 14:04:45 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F24F712952E for <v6ops@ietf.org>; Fri, 17 Mar 2017 14:04:44 -0700 (PDT)
Received: from [IPv6:2001:1291:200:42e::2] (cl-1071.udi-01.br.sixxs.net [IPv6:2001:1291:200:42e::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 3B91C82B75; Fri, 17 Mar 2017 22:04:38 +0100 (CET)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Gert Doering <gert@space.net>
References: <c8c0f5be-28bb-ba31-16da-7fc7e3fccec0@gmail.com> <20170316082639.GF2367@Space.Net> <29F9E911-E637-456D-A930-3316FFD93C41@jisc.ac.uk> <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>
Cc: v6ops@ietf.org
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <caa13b7e-f2d2-93f5-7f67-28f16a16da0b@si6networks.com>
Date: Fri, 17 Mar 2017 17:52:44 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <212f8258-a025-325e-badc-e7bdcc2bf5f7@gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/PyyOWM_M6Vf1Eu8e-GkDtF4fgm8>
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 21:04:47 -0000

On 03/16/2017 07:43 PM, Brian E Carpenter wrote:
> On 17/03/2017 09:14, Gert Doering wrote:
>> Hi,
>>
>> On Fri, Mar 17, 2017 at 06:31:43AM +1300, Brian E Carpenter wrote:
>>> So, it seems clear to me that while getting a /64 is better than getting
>>> a /128, it's even better to get a /56. Or even one of those 15 trillion /48s.
>>> We should make it clear that /64 is not even second-best. Just better
>>> than /128.
>>
>> "give any *host* that connects a /48" (and dimension pools on WiFi
>> hotspots etc. big enough to actually be able to do this) might actually 
>> be a good way to ensure IPv6 is going to run out faster than expected...
>>
>> IOW, be careful with the maths here.
> 
> 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. :-)

Well... /64 is not enough because somehow we choose to waste a large
part of 128-64. IN principle if one were to use 48 bits for the iid (or
even 56) that would still be big enough for randomizing IID, while still
having 16 or 8 bits for "subnetting"...

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492