[131496] in North American Network Operators' Group
Re: IPv6 Routing table will be bloated?
daemon@ATHENA.MIT.EDU (Florian Weimer)
Tue Oct 26 11:20:35 2010
To: Jack Bates <jbates@brightok.net>
From: Florian Weimer <fweimer@bfk.de>
Date: Tue, 26 Oct 2010 15:20:27 +0000
In-Reply-To: <4CC6DE55.7000901@brightok.net> (Jack Bates's message of "Tue\,
26 Oct 2010 08\:57\:41 -0500")
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
* Jack Bates:
> So, the best that I can tell (still not through debating with RIR),
> the IPv6 routing table will see lots of bloat. Here's my reasoning so
> far:
>
> 1) RIR (ARIN in this case, don't know other RIR interpretations) only
> does initial assignments to barely cover the minimum. If you need more
> due to routing, you'll need to provide every pop, counts per pop, etc,
> to show how v6 will require more than just the minimums (full routing
> plan and customer counts to justify routing plan).
If you get better routing and reachability from not filtering at the
/32 boundary, network operators will stop filtering at the /32
boundary. So this issue will likely go away pretty soon because you
can use our initial assignment to gain the routing flexibility you
need.
--=20
Florian Weimer <fweimer@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstra=DFe 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
