[147562] in North American Network Operators' Group

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

De-bogon not possible via arin policy.

daemon@ATHENA.MIT.EDU (Cameron Byrne)
Wed Dec 14 16:16:45 2011

Date: Wed, 14 Dec 2011 13:15:48 -0800
From: Cameron Byrne <cb.list6@gmail.com>
To: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

Fyi, I just was rejected from arin for an ipv4 allocation. I demonstrated I
own ~100k ipv4 addresses today.

My customers use over 10 million bogon / squat space ip addresses today,
and I have good attested data on that.

But all I can qualify for is a /18, and then in 3 months maybe a /17. This
is called slow start ? For an established business?

Just fyi, de-bogoning , or private rfc 1918 is not really an option even
with strong and consistent demonstrate load.

Any suggestions on how to navigate this policy ?

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