Re: [v6ops] I-D Action: draft-colitti-v6ops-host-addr-availability-01.txt

Philip Homburg <pch-v6ops-3@u-1.phicoh.com> Tue, 28 July 2015 13:44 UTC

Return-Path: <pch-bBB316E3E@u-1.phicoh.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3498B1A907E for <v6ops@ietfa.amsl.com>; Tue, 28 Jul 2015 06:44:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.6
X-Spam-Level:
X-Spam-Status: No, score=-4.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 p-6NhxfbLYIV for <v6ops@ietfa.amsl.com>; Tue, 28 Jul 2015 06:44:45 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id 2E2D41A908B for <v6ops@ietf.org>; Tue, 28 Jul 2015 06:44:36 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #91) id m1ZK5BL-0000CVC; Tue, 28 Jul 2015 15:44:35 +0200
Message-Id: <m1ZK5BL-0000CVC@stereo.hq.phicoh.net>
To: IPv6 Operations <v6ops@ietf.org>
From: Philip Homburg <pch-v6ops-3@u-1.phicoh.com>
Sender: pch-bBB316E3E@u-1.phicoh.com
References: <CAKD1Yr2z6T86gmQMPZwbgFB4mdt7=xWNuei5jaQg=vpG7-zLVg@mail.gmail.com> <m1ZJdjZ-0000CcC@stereo.hq.phicoh.net> <20150727091241.GL84167@Space.Net> <m1ZJfOr-0000CgC@stereo.hq.phicoh.net> <C9C3FBC4-44F3-45D2-B8C4-3725396E5D40@nominum.com> <CAPi140Mx96dBgeaCkrsDD+-J85OZDo5Di+gHTBiaGDzYK2us4w@mail.gmail.com> <20150728115944.GZ84167@Space.Net> <m1ZK3m7-0000CZC@stereo.hq.phicoh.net> <20150728122230.GD84167@Space.Net> <m1ZK4Ih-0000CdC@stereo.hq.phicoh.net> <20150728125004.GF84167@Space.Net>
In-reply-to: Your message of "Tue, 28 Jul 2015 14:50:04 +0200 ." <20150728125004.GF84167@Space.Net>
Date: Tue, 28 Jul 2015 15:44:34 +0200
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/GCcBhcjJH7NDs2zEMEKvckPJH1c>
Subject: Re: [v6ops] I-D Action: draft-colitti-v6ops-host-addr-availability-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 28 Jul 2015 13:44:48 -0000

In your letter dated Tue, 28 Jul 2015 14:50:04 +0200 you wrote:
>On Tue, Jul 28, 2015 at 02:48:07PM +0200, Philip Homburg wrote:
>> If you have more a 100 devices requesting DHCPv6-PD, then maybe it is time to
>> get a /48?
>
>For each single L2 network in a large enterprise?  Is that covered by RIR
>policies?
>
>Please do me the honour to actually *read* what I write.  This is not
>about "home", because home does not have scaling issues of the sort Andrew
>was talking about.

I don't see the problem. You can get a /48 no questions asked. This is 
equivalent to a /16 for IPv4. You can easily reach 10000 devices without nat on
IPv4 out of a /16. Why would it be different for /64s out of a /48?

Of course, the more devices you want in a /48 the more careful you addressing
plan has to be. But certainly for large flat structures it should be easy to
achieve high density.

I don't know if RIR policies allow for one /64 per device from PI. If not, then
maybe somebody should submit a policy proposal.