[168568] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: FW: Updated ARIN allocation information

daemon@ATHENA.MIT.EDU (Tore Anderson)
Thu Jan 30 09:56:19 2014

Date: Thu, 30 Jan 2014 15:55:57 +0100
From: Tore Anderson <tore@fud.no>
To: "Justin M. Streiner" <streiner@cluebyfour.org>, 
 nanog list <nanog@nanog.org>
In-Reply-To: <Pine.LNX.4.64.1401300515020.15990@whammy.cluebyfour.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

* Justin M. Streiner

> In the worst case, this would add another 262,144 routes (/10 fully
> assigned, and all assignments are /28s) to the global IPv4 route view.
> Realistically, the number will be a good bit smaller than that, but only
> time will tell for sure exactly how much smaller.  Wash/rinse/repeat for
> any other RIR that adopts a similar policy.

I wouldn't worry if I were you. I'll wager you $100 that pretty much all
of the people requesting a block from ARIN under this policy (or any
other) is going to go for a /24 (or larger). There is some precedent;
RIPE policy has not mandated a minimum assignment size for IPv4 PI, at
least not in the last decade, yet the NCC has made almost no assignments
smaller than /24.

Tore


home help back first fref pref prev next nref lref last post