[144700] in North American Network Operators' Group
RE: wet-behind-the-ears whippersnapper seeking advice on building a
daemon@ATHENA.MIT.EDU (Nathan Eisenberg)
Fri Sep 16 18:14:56 2011
From: Nathan Eisenberg <nathan@atlasnetworks.us>
To: "nanog@nanog.org" <nanog@nanog.org>
Date: Fri, 16 Sep 2011 22:14:12 +0000
In-Reply-To: <Pine.LNX.4.64.1109161723560.17783@whammy.cluebyfour.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> When I still worked in the ISP world, the startup I worked for started of=
f with
> PA space, and then grew into PI space, and handed the PA space back to
> their upstreams as it was vacated. I had no problems getting subsequent =
PI
> blocks because our documentation was in order.
The documentation isn't the pain. The renumbering is, *especially* if you'=
re running a service provider network:
'Dear dedicated server customer, we're taking away your IPs, please don't b=
e angry with us even though it will cost you untold hours of work to hunt d=
own all the tiny implications of renumbering. Never mind the lost business=
it might cause if you miss something.'
'Dear internet access user who happens to run a bunch of IPSEC tunnels: Hav=
e fun fixing all your tunnels! Don't worry, we'll figure out an off-hours =
time that works for everyone, and that makes all the pain go away, right? =
You won't harbor any resentment, right?'
(Wow, that comes off more bitter than I expected...)
Oh well... Since new IPv4 allocations are fast approaching the same scarcit=
y as unobtanium, I guess it's too late to worry about it now. Anyways, app=
arently IPv6 fixes all of this, or something.
Nathan
