Message: 7
Date: Thu, 31 Jan 2013 10:00:22 +1100
From: Mark Andrews <marka@isc.org>
To: Michael Thomas <mike@mtcc.com>
Cc: NANOG list <nanog@nanog.org>
Subject: Re: "Programmers can't get IPv6 thus that is why they do not
have IPv6 in their applications"....
Message-ID: <20130130230022.E74BD2E9390C@drugs.dv.isc.org>As a product of having a motorola sb6121 and a netgear wndr3700 both
of which I bought at frys I have ipv6 in my house with dhcp pd curtesy of
commcast
. If it was any simpler somebody else would have had to install it.Except that Apple Airport Extreme users must have one of the newer
hardwareversions, that is my experience as well.
And, even before Comcast and new AEBS, Hurricane Electric removed all
otherexcuses for claiming "no IPv6".
"Remove excuses" != "Create incentive". There are an infinite number of
things I can do to "remove excuses". Unless they're in my face (read:
causing
me headaches), they do not "create incentive". My using my or my
company's
software which doesn't work in my own environment (= work, home, phone,
etc)
"creates incentive". Lecturing me about how I can get a HE tunnel and
that if
I don't i'm ugly and my mother dresses me funny, otoh, just "creates
vexation
".
MikeJust having IPv6 doesn't create incentives to make their code work
with IPv6. People just trundle along using IPv4. Turning off IPv4
creates incentives. Reducing IPv4's capabilities creates incentives.
Being told this needs to work and be tested with IPv6 creates
incentives.
[jjmb] turning off IPv4 is not realistic at this time and there are other
ways to encourage the use and adoption of IPv6. Enabling by default,
requesting upgrades for existing products that introduce support for IPv6.
Enabling IPv6 alone is a significant statement especially when your
business relies on the same. The absence of IPv6 or broken IPv6 when your
business relies on it are no longer options.