North American Network Operators Group
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Historical
Re: IP failover/migration question.
- From: infowolfe
- Date: Tue Jun 27 14:05:30 2006
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=B/IR1XGnuMPoXLOs+0m5Jwf8JfGmtRL5ne7KkR+Xy4Ux+xrbwsECaylr1z0EJFEZ23qNRgSaisZ9PikRlUB6aKm/S5YTgto+DjoMhrZBt5d0OLH0nY69CQDbIwsjbLNTi5Kna8cvQj5aJFYyeluilcJbgZvNWbrSWODPkEksJvM=
On 6/27/06, Owen DeLong <owen@delong.com> wrote:
> Uptime might not matter for small hosts that do mom and pop websites
> or so-called "beta" blog-toys, but every time Level3 takes a dump,
> it's my wallet that feels the pain. It's actually a rather frustrating
> situation for people who aren't big enough to justify a /19 and an
> AS#, but require geographically dispersed locations answering on the
> same IP(s).
I'm not sure why you think you need to be that big to get portable IP
space. Policy 2002-3 allows for the issuance of a /22 to any organization
which can show a need and the ability to utilize at least 50% of a /22
with multihoming. An ASN can be obtained pretty easily if you intend
to multihome. About the only thing that might stand in the way of
a small organization is the up front cost, but, even that is less than
$2000.
It's entirely possible that I was mistaken with regards to /19 vs /22,
but a /22 is still way more ips than I really need, I mean hell, I'm
not really using my /24 currently. I don't nearly have 256 machines,
and I certainly (without honepotting almost all of it) justify 1,024
ips.
In fact, in my network infrastructure currently, I've got one
loadbalancer that sits in front of 6 machines that don't have public
ips, so there goes any thought of justification ;-) and yet, when I'm
at 4 load balancers, I'll want them in geographically dispersed
locations, with a variety of upstream providers so that I don't have
to deal with the issues surrounding single-homed networking.
|
