Karl O. Pinc wrote:
On 06/18/2009 01:50:17 PM, Pete Vickers wrote:
On 18. juni. 2009, at 19.45, Karl O. Pinc wrote:
What's the best way to solve this problem?
stop trying to bodge it, and get some PI space.
I'd love but, how can I justify to ARIN a large enough address
block that it won't be dropped by BGP administrators?
The only reason we'd need the addresses is to muti-home.
ARIN says you can get a /22 for multihoming if you can justify their 25%
/ 50% usage as spelled out in their numbering policy.
https://www.arin.net/policy/nrpm.html#four322
If you can't justify that, then get a /24 of PA space from a provider
that *will* allow you to reannounce that /24 via an additional transit
and *will* provide you with an LOA that you can provide to that
additional transit operator.
The number of networks that filter prefixes smaller than /22 don't
appear to be that numerous IMHO, but if they do, your /24 will still be
reachable as they'll see the larger /19 or whatever from your provider
that it's carved out of.
I am under the impression this is not reason enough
for ARIN, that they are in a rationing mood when it comes
to handing out IPv4 address blocks.
As well they should be. IP resources are scarce and people are wasteful
and greedy.
Most offices don't need BGP multihoming, or any sort of inbound
multihoming at all-- just outbound which is easily done without the
assistance of the ISPs themselves or ARIN by using NAT and
upstream-failover features commonly found in most routers.
Most world-accessible servers that are important enough to need inbound
multihoming should be sitting in a datacenter which has significantly
more professionally-managed multihoming than small offices.
And before the flaming starts, remember that I said "most."
Cheers,
Tico
Karl <k...@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein