[ppml] proposed updates to 2006-4

Scott Leibrand sleibrand at internap.com
Fri Mar 31 14:13:59 EST 2006

On 03/31/06 at 6:49pm -0000, Andrew Dul <andrew.dul at quark.net> wrote:

> >  -------Original Message-------
> >  From: Houle, Joseph D (Joe), CMO <jdhoule at att.com>
> >
> >     This "reserve" concept is a little orthogonal to ARINs standard Mode
> >  of Operating, isn't it?
> Yes & no...the IPv4 practice used to be if you were assigned a /19 ARIN reserved a /18 for about 1-2 years.  (I don't know if that is current practice.)  If you came back to ARIN within the reserve window you then were assigned the larger block which would be aggregatable.

AFAICT this is still ARIN practice.  Our last two ARIN IPv4 allocations
were aggregatable.

To address the concern expressed earlier on this thread that larger
reservations use up more space, I would maintain that one advantage to
having a large reserved block for future growth is that if down the road
needs change ARIN can start allocating from the unused "holes" created by
the sparse allocation.  But if they don't need to, then you reduce the
chance of an org having to deaggregate because they were given different
non-aggregatable blocks at different points in their growth curve.


More information about the ARIN-PPML mailing list