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

Owen DeLong <owen@delong.com> Fri, 30 May 2014 14:45 UTC

Return-Path: <owen@delong.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 E61A11A0942 for <v6ops@ietfa.amsl.com>; Fri, 30 May 2014 07:45:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.642
X-Spam-Level:
X-Spam-Status: No, score=-1.642 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no
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 fzTZbGujt6o4 for <v6ops@ietfa.amsl.com>; Fri, 30 May 2014 07:45:26 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 3C9361A0933 for <v6ops@ietf.org>; Fri, 30 May 2014 07:45:26 -0700 (PDT)
Received: from [IPv6:2620::930:0:225:ff:fe44:af17] ([IPv6:2620:0:930:0:225:ff:fe44:af17]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.2) with ESMTP id s4UEejiN026854 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 30 May 2014 07:40:45 -0700
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com s4UEejiN026854
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1401460846; bh=Rfnk0n1fSVv2G87yGP/WLZ5IFxI=; h=Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=jA7cSFfmfrGQzlDo4DsORgF59ranI4MQ2vXCpGyY+NveApUn3HnldQ32CVN28FPOM Ce1McIX8Ez4uYM7B6tVRycXfnxFt3c9OJ9jBvKLnhT80yRNutIfpXBS7gRyU8ealN+ BV3L2FmgN4NrNfMu0wuO0rKz9/7pbH8cEyLEHOw8=
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Content-Type: text/plain; charset="windows-1252"
From: Owen DeLong <owen@delong.com>
X-Priority: 3
In-Reply-To: <02dc01cf7c06$cc6a4bc0$4001a8c0@gateway.2wire.net>
Date: Fri, 30 May 2014 07:44:06 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3350A387-4F86-4445-A72E-075913E40618@delong.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>
To: "t.petch" <ietfc@btconnect.com>
X-Mailer: Apple Mail (2.1874)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [IPv6:2620:0:930::200:2]); Fri, 30 May 2014 07:40:46 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/2yv_nlWpolrJzKYKoW9CDd7E56A
Cc: V6 Ops List <v6ops@ietf.org>, Tore Anderson <tore@fud.no>
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 14:45:27 -0000

> 
> Tore
> 
> 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.

Yes, we need to change the fundamental way we deal with routing and come up
with a more scalable solution than the current everyone knows every prefix
model.

However, at any likely growth rate, if we actually start working on the problem
instead of simply inflicting limitations and calling it handled, then we have
time to address the issue in IPv6. Hopefully the RRG will wake up and start
addressing this issue. For now, it is out of scope for v6ops as I understand
the WG charter.

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

All the more reason this issue needs to get addressed instead of ignored.

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

He’s somewhat right about the problem. He’s absolutely wrong in believing that
the current limitations are a solution.

Owen