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

Tore Anderson <tore@fud.no> Wed, 28 May 2014 22:09 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 DD21A1A06C2 for <v6ops@ietfa.amsl.com>; Wed, 28 May 2014 15:09:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 OESRiqGN8eF8 for <v6ops@ietfa.amsl.com>; Wed, 28 May 2014 15:09:43 -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 543601A06A9 for <v6ops@ietf.org>; Wed, 28 May 2014 15:09:43 -0700 (PDT)
Received: from [2a02:fe0:c410:3310::3] (port=35768 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 1Wpm2U-0005D5-9o; Thu, 29 May 2014 00:09:38 +0200
Message-ID: <53865EA2.9000502@fud.no>
Date: Thu, 29 May 2014 00:09:38 +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: 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>
In-Reply-To: <53864DCB.5070202@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/Z4JhzugnueY-6pwiRUGrrRBd8r0
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: Wed, 28 May 2014 22:09:45 -0000

* Brian E Carpenter

> Tore,
> 
>> We have a few customers in the same situation. So we obtained a PI
>> prefix for them, 
> 
> The important words there are "a few". As long as the numbers are
> reasonable, this scales. When the numbers cease to be reasonable,
> it doesn't scale. The estimate I made some years ago, based on
> a little research into statistics in a few countries, was that
> there must be about 10 million small or medium enterprises in the
> world. We don't know how to route 10M prefixes in BGP-4. So
> somewhere between "PI for a few customers" and "PI for every
> enterprise", we have to stop.

For sure, it is a very small minority of my customers who have this
requirement. The vast majority are perfectly happy to be assigned
prefixes out of my PA block. This goes for IPv4 too, BTW.

I seriously doubt that a significant fraction of those 10M enterprises
asking for a PI prefix (or multihoming at all) is a realistic scenario.
So I'm not too worried about IPv6 PI to be honest, we survived IPv4 PI
so far and I think we'll survive IPv6 PI also, even if adding a few
"new" PI holders who in IPv4 multihomed using PA assignments from their
upstreams + NAT44 + RFC1918. Especially if homenet comes up with an even
more attractive solution than PI for that specific use case soon.

Tore