Re: [v6ops] PI [ULA draft revision #2 Regarding isolated networks]

Tore Anderson <tore@fud.no> Fri, 30 May 2014 17:23 UTC

Return-Path: <tore@fud.no>
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 35AEF1A6F8C for <v6ops@ietfa.amsl.com>; Fri, 30 May 2014 10:23:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.951
X-Spam-Level:
X-Spam-Status: No, score=-1.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, RP_MATCHES_RCVD=-0.651] 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 zt_HtUU5Lbgr for <v6ops@ietfa.amsl.com>; Fri, 30 May 2014 10:22:58 -0700 (PDT)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E0171A09CC for <v6ops@ietf.org>; Fri, 30 May 2014 10:22:58 -0700 (PDT)
Received: from [2a02:fe0:c410:3310::3] (port=46616 helo=wrath.fud.no) by greed.fud.no with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <tore@fud.no>) id 1WqQW3-0001xM-I6; Fri, 30 May 2014 19:22:51 +0200
Message-ID: <5388BE5C.8010809@fud.no>
Date: Fri, 30 May 2014 19:22:36 +0200
From: Tore Anderson <tore@fud.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: "t.petch" <ietfc@btconnect.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D8B6B9A@nkgeml506-mbx.china.huawei.com> <m261ks7xww.wl%randy@psg.com> <53840070.90801@gmail.com> <m2y4xn7wep.wl%randy@psg.com> <53840723.8010606@gmail.com> <CAKD1Yr1O_poMR200sjU=ttRvGaeQRkC1ZfXC0Ok4uQxdq3K=NQ@mail.gmail.com> <m2mwe37tbn.wl%randy@psg.com> <CAKD1Yr2t3-vxuG=iDi4biBNFpJwuzuHgfpB74i_uydWWRV7qZg@mail.gmail.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D8B6E02@nkgeml506-mbx.china.huawei.com> <m2fvjv7q4h.wl%randy@psg.com> <m1WpDcc-0000BMC@stereo.hq.phicoh.net> <43BB867C-7BCA-45F6-8ADC-A49B34D6C0DC@nominum.com> <5384937A.90409@foobar.org> <m2iooq4oqi.wl%randy@psg.com> <5385762E.5020901@dougbarton.us> <5385AA97.1050207@fud.no> <53864DCB.5070202@gmail.com> <53865EA2.9000502@fud.no> <02dc01cf7c06$cc6a4bc0$4001a8c0@gateway.2wire.net>
In-Reply-To: <02dc01cf7c06$cc6a4bc0$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/kNG7LED1AD4HAPgcOetdMW_8C6E
Cc: V6 Ops List <v6ops@ietf.org>
Subject: Re: [v6ops] PI [ULA draft revision #2 Regarding isolated networks]
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: <http://www.ietf.org/mail-archive/web/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, 30 May 2014 17:23:01 -0000

* t.petch

> The damage done by PI in IPv4 was understood before the RIRs
> started handing out addresses in large numbers, so while PI exists,
> it has always been hard to get.
> 
> The fear with IPv6 is that just because one constraint on PI has
> been removed, those handing out addresses will not realise that there
> is another show-stopping constraint in the number of entries a FIB
> can cope with, 1M being the best estimate (as before, on the RRG
> list) with the foreseeable improvements to current technology.
> 
> And I think that every SME who has lost business with the
> unreliability of their ISP will want multi-homing and will think that
> with IPv6 and PI the constraints have gone, and the number of such
> SMEs can only approach 10M over time.

I'm only familiar with the RIPE region's policies, but PI certainly
wasn't «hard to get» for an SME here that wanted to multi-home (until
the point where we stopped completely issuing new blocks of it, that
is). It only had to do the following:

1) Pick a sponsoring LIR out of the ~10k available to choose from, and
2) Fill out the appropriate request form, and
3) Be prepared to pay a yearly fee of €50 (+ the LIRs profit margin).

The procedure was the same for IPv4 PI as it still is for IPv6 PI.

(The only real difference between IPv4 and IPv6 PI was the difficulty in
getting a large IPv4 assignment. While in IPv6 you get an enormous /48
with no questions asked, in IPv4 you only get a measly /24 and would
have to provide additional documentation if you wanted more. However
this difference is moot in a discussion of FIB sizes, as the scarce
resource is the routing table entries themselves, and the prefix length
of each individual entry is AFAIK irrelevant.)

Tore