nanog mailing list archives
Re: De-bogon not possible via arin policy.
From: Rubens Kuhl <rubensk () gmail com>
Date: Wed, 14 Dec 2011 19:20:17 -0200
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
Current thread:
- De-bogon not possible via arin policy. Cameron Byrne (Dec 14)
- Re: De-bogon not possible via arin policy. Rubens Kuhl (Dec 14)
- Re: De-bogon not possible via arin policy. Andrew D Kirch (Dec 14)
- Re: De-bogon not possible via arin policy. Robert E. Seastrom (Dec 14)
- Re: De-bogon not possible via arin policy. David Conrad (Dec 14)
- Re: De-bogon not possible via arin policy. Jeff Wheeler (Dec 14)
- Re: De-bogon not possible via arin policy. Jimmy Hess (Dec 14)
- Re: De-bogon not possible via arin policy. Joel jaeggli (Dec 14)
- Re: De-bogon not possible via arin policy. David Conrad (Dec 14)
- Re: De-bogon not possible via arin policy. Jimmy Hess (Dec 14)
- Re: De-bogon not possible via arin policy. Jared Mauch (Dec 14)
- Re: De-bogon not possible via arin policy. Matthew Kaufman (Dec 15)
- Re: De-bogon not possible via arin policy. Rubens Kuhl (Dec 14)