[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
De-bogon not possible via arin policy.
- Subject: De-bogon not possible via arin policy.
- From: rubensk at gmail.com (Rubens Kuhl)
- Date: Wed, 14 Dec 2011 19:20:17 -0200
- In-reply-to: <CAD6AjGSiJiLj3itb1EARVpNn-xF5hMnrk97pYYjLrw=X_-XfhA@mail.gmail.com>
- References: <CAD6AjGSiJiLj3itb1EARVpNn-xF5hMnrk97pYYjLrw=X_-XfhA@mail.gmail.com>
> 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 ?
You should easily qualify for a /32 or larger IPv6 block.
And it's curious that errors that are likely to be there for decades
are just now trying to be fixed as IPv4 pool is depleted, isn't it ?
Rubens