IPV6 in enterprise best practices/white papaers

Sun Jan 27 23:36:17 UTC 2013

In message <CAPYK2_xonYrKqRLMJBVD26JsCEX5jDBjYQU3h_2sBbFVg3uBVw at mail.gmail.com>, Harald Koch writes:
> On 26 January 2013 17:38, Mark Andrews <marka at isc.org> wrote:
> > As for "breaking" your LAN, if the applications take 60 seconds to
> > fallback to the other address they were already broken.  Go complain
> > to your application vendor.  Some vendors have already fixed this
> > problem with their applications.
> 
> The question was about *enterprise* deployment, which raises two issues:
> 
> 1) most vendors are waiting for customer IPv6 demand before
> implementing support (or fixing bugs) - chicken and egg problem.

This is not a IPv6 bug.  The bug is present in IPv4 only networks.
It is a bug in the applications multi-homing support.  Adding IPv6
just makes every destination multi-homed.  Just think about how
much money has already been spent to work around this bug.

> 2) I don't know many enterprises running production software less than
> a year (or more) old.
> 
> In the meantime, the network engineers struggling with this stuff need
> workarounds (like the tuning parameters you and others have
> mentioned).
> 
> -- 
> Harald
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org