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

t.petch <ietfc@btconnect.com> Fri, 30 May 2014 13:01 UTC

Return-Path: <ietfc@btconnect.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 20FD71A08DE for <v6ops@ietfa.amsl.com>; Fri, 30 May 2014 06:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] 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 FzEEnI08xtVz for <v6ops@ietfa.amsl.com>; Fri, 30 May 2014 06:01:01 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lp0080.outbound.protection.outlook.com [213.199.154.80]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F7991A08E2 for <v6ops@ietf.org>; Fri, 30 May 2014 06:01:01 -0700 (PDT)
Received: from DBXPRD0510HT003.eurprd05.prod.outlook.com (157.56.252.165) by AMXPR07MB054.eurprd07.prod.outlook.com (10.242.67.143) with Microsoft SMTP Server (TLS) id 15.0.954.9; Fri, 30 May 2014 13:00:54 +0000
Message-ID: <02dc01cf7c06$cc6a4bc0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: Tore Anderson <tore@fud.no>, 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>
Date: Fri, 30 May 2014 13:57:51 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.252.165]
X-ClientProxiedBy: AMXPR07CA006.eurprd07.prod.outlook.com (10.242.64.46) To AMXPR07MB054.eurprd07.prod.outlook.com (10.242.67.143)
X-Microsoft-Antispam: BL:0; ACTION:Default; RISK:Low; SCL:0; SPMLVL:NotSpam; PCL:0; RULEID:
X-Forefront-PRVS: 02272225C5
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(6009001)(428001)(51444003)(13464003)(189002)(199002)(377454003)(51704005)(87286001)(87976001)(74662001)(44736004)(85852003)(4396001)(92726001)(77982001)(74502001)(89996001)(83072002)(92566001)(76482001)(83322001)(50226001)(19580395003)(19580405001)(77156001)(64706001)(81816999)(81686999)(50986999)(76176999)(99396002)(81542001)(102836001)(21056001)(42186004)(81342001)(79102001)(33646001)(47776003)(44716002)(62236002)(20776003)(14496001)(101416001)(15975445006)(84392001)(88136002)(104166001)(46102001)(80022001)(61296002)(62966002)(66066001)(31966008)(23756003)(93916002)(86362001)(50466002)(74416001)(7726001); DIR:OUT; SFP:; SCL:1; SRVR:AMXPR07MB054; H:DBXPRD0510HT003.eurprd05.prod.outlook.com; FPR:; MLV:nov; PTR:InfoNoRecords; MX:1; A:0; LANG:en;
Received-SPF: None (: btconnect.com does not designate permitted sender hosts)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
X-OriginatorOrg: btconnect.com
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/2ulvZWInQSyWc2JMer-vEWUjF1A
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 13:01:04 -0000

----- Original Message -----
From: "Tore Anderson" <tore@fud.no>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
Cc: "V6 Ops List" <v6ops@ietf.org>
Sent: Wednesday, May 28, 2014 11:09 PM

> * 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

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.

So, Brian is spot on, and just as the IETF did little about IPv4
addresses running out until the event loomed large, so I expect history
to repeat itself with the growth of PI in IPv6.

Tom Petch
>
> Tore
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops