[137092] in North American Network Operators' Group
Re: IPv6 - a noobs prespective
daemon@ATHENA.MIT.EDU (Jack Bates)
Wed Feb 9 13:22:53 2011
Date: Wed, 09 Feb 2011 12:22:38 -0600
From: Jack Bates <jbates@brightok.net>
To: William Herrin <bill@herrin.us>
In-Reply-To: <AANLkTimNwxkB0xZ-OKP44DXKvfLHedwV8K3pEX4yawQx@mail.gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 2/9/2011 12:03 PM, William Herrin wrote:
> The thing that terrifies me about deploying IPv6 is that apps
> compatible with both are programmed to attempt IPv6 before IPv4. This
> means my first not-quite-correct IPv6 deployments are going to break
> my apps that are used to not having and therefore not trying IPv6. But
> that's not the worst part... as the folks my customers interact with
> over the next couple of years make their first not-quite-correct IPv6
> deployments, my access to them is going to break again. And again. And
> again. And I won't have the foggiest idea who's next until I get the
> call that such-and-such isn't working right.
What scares me most is that every time I upgrade a router to support
needed hardware or some badly needed IPv6 feature, something else
breaks. Sometimes it's just the router crashes on a specific IPv6
command entered at CLI (C) or as nasty as NSR constantly crashing the
slave (J); the fixes generally requiring me to upgrade again to the
latest cutting edge releases which everyone hates (where I'm sure I'll
find MORE bugs).
The worst is when you're the first to find the bug(which I'm not even
sure how it's possible given how simplistic my configs are, isis
multitopology, iBGP, NSR, a few acls and route-maps/policies), it takes
3-6 months or so to track it down, and then it's put only in the next
upcoming release (not out yet) and backported to the last release.
Jack (hates all routers equally, doesn't matter who makes it)
