Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03

Jeroen Massar <jeroen@massar.ch> Sat, 08 June 2013 03:05 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 DCBD011E80A6; Fri, 7 Jun 2013 20:05:21 -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 UVhmxXKwgdIj; Fri, 7 Jun 2013 20:05:20 -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 751CD11E80A3; Fri, 7 Jun 2013 20:05:19 -0700 (PDT)
Received: from kami.ch.unfix.org (unknown [IPv6:2001:559:8000:c9: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 88DA1801C2BA; Sat, 8 Jun 2013 05:05:04 +0200 (CEST)
Message-ID: <51B29F5F.70400@massar.ch>
Date: Fri, 07 Jun 2013 20:05:03 -0700
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Owen DeLong <owen@delong.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
References: <05DB0BDC-9B6D-4852-B878-5320ABC14D67@steffann.nl> <8D23D4052ABE7A4490E77B1A012B6307751C5A63@mbx-01.win.nominum.com> <CAKD1Yr1tSy9XZ5A8Zc-doBTfWiPX1TkqGuJeqty9=mhwwHPRKA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751C6F61@mbx-01.win.nominum.com> <9B71CE05-E12D-4FE9-8222-6FBFD7938F0C@delong.com> <8D23D4052ABE7A4490E77B1A012B6307751C850C@mbx-01.win.nominum.com> <CAKD1Yr0Y2_-k0sj=RsSicubJT6dUq7FJDvBoCv5h_DUTjY9ZOw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751C86DF@mbx-01.win.nominum.com> <CAKD1Yr0EQwqEzPe_FK+XnN+mOGaVU2NWW2Sr5toGZhKiMwkW2A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751C90F7@mbx-01.win.nominum.com> <CAKD1Yr3frpGOYDoDBfvZR+XocgQZzYeK-_G=3sbtASb3ZfuRSQ@mail.gmail.com> <932B5FC1-FDAB-458B-9117-56E543CC911E@delong.com>
In-Reply-To: <932B5FC1-FDAB-458B-9117-56E543CC911E@delong.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "<draft-jiang-v6ops-semantic-prefix@tools.ietf.org>" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org 6man-wg" <ipv6@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, Lorenzo Colitti <lorenzo@google.com>
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: Sat, 08 Jun 2013 03:05:22 -0000

On 2013-06-07 19:17, Owen DeLong wrote:
>> 
>> 2. Comcast only appears to have a /29 and a /28 (2001:558::/29,
>> 2601::/28). That's only 1.5M /48s, and they have about 10x that
>> many customers. They likely can't use /48 plus semantic prefixes,
>> because if ARIN doesn't accept "semantic prefixes" as using space
>> efficiently (and word from ARIN on this thread seems, well,
>> negative on the matter), then they won't be able to get more space
>> from ARIN. That means that there is a fundamental tension between
>> using semantic prefixes and giving more address space to
>> customers.
>> 
> 
> It also means that Comcast has a dramatically undersized allocation
> and will most likely be depriving their customers.

Comcast is mostly an end-user ISP isn't it? Because in ARIN land ISPs
are supposed to calculate with /56s and suddenly there is a lot of space
for doling out /56 to end-users and /48s and larger for their corporate
clients. And then it is good that they are skipping out on the 6rd
deployment. Funny to see that even good network engineers did not grasp
the concept of 'request a /48 for every customer', and multiply that
with the HD ratio and voila request that address space and be over with
it, but that they had to return for a second prefix though...

Also https://www.arin.net/policy/nrpm.html
---------------------
2.8. Utilization (IPv6)

In IPv6, "utilization" is only measured in terms of the bits to the left
of the /56 boundary. In other words, utilization refers to the
assignment of /56s to end sites, and not the number of addresses
assigned within individual /56s at those end sites.
------------------

Although in 2.15 in that document it is recommended to do /48.

Though this is not reflected in the current policy, it likely comes from
2005-8 (https://www.arin.net/policy/proposals/2005_8.html)

8<-------
The following guidelines may be useful (but they are only guidelines):

- /64 when it is known that one and only one subnet is needed

- /56 for small sites, those expected to need only a few subnets over
the next 5 years.

- /48 for larger sites
---------->8

Greets,
 Jeroen