[167618] in North American Network Operators' Group
Re: turning on comcast v6
daemon@ATHENA.MIT.EDU (Matthew Huff)
Fri Dec 20 17:27:33 2013
From: Matthew Huff <mhuff@ox.com>
To: Mark Andrews <marka@isc.org>
Date: Fri, 20 Dec 2013 17:27:15 -0500
In-Reply-To: <20131220215148.AE92FC1C7D5@rock.dv.isc.org>
Cc: nanog2 <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
You can request a fully working IPv6 implementation, but it's not going to =
stop a purchasing if it doesn't. If you are deciding between two vendors an=
d one is better/cheaper and doesn't have IPv6 and you choose the other, it'=
s likely you will be looking for another job. There is no strong justificat=
ion for deploying IPv6 in a corporate enterprise currently. Corporate world=
is focused on the next quarter, not at a 10 year horizon.
We decided to roll it out for a number of reasons. One, we had time this s=
ummer. Two, we figured it would highlight inherent issues already in our en=
vironment (it did, and we found a few doozies), and finally it was a good i=
ntellectual exercise. We have it running on all over our desktops, and most=
of our servers (some issues with license management software and other leg=
acy software prevents us from deploying it on all servers)
If we had an orderly shutdown of our IPv6 environment, there would be zero =
impact to the business. In fact, due to complexity issues, it would arguabl=
y we would arguably be better off without it. Perhaps in a few years things=
will be different. My bet is that even in 5 years, corporate adoption will=
be very small, maybe as low as 10%.
On Dec 20, 2013, at 4:51 PM, Mark Andrews <marka@isc.org> wrote:
>=20
> In message <CAL9jLaa=3DqKuMLC7djtMru92f3tQcYp3ehR060nRcfKg-ho+bKA@mail.gm=
ail.com>, Christopher Morrow writes:
>>>=20
>>> Not all devices have working IPv6 stacks. OK, they're broken, complain
>>> to the vendor and get them to fix their product or buy a working produc=
t
>>> from a different vendor.
>>>=20
>>=20
>> I don't know that this is a practical option... for say some systems I
>> know that don't do v6 properly or at all, and which have buying cycles
>> on the 10yr horizon, not 2yrs/etc.
>=20
> And I hate to say it but people have been saying for over a decade.
>=20
> * request support IPv6 in the products you are purchasing.
> * test the IPv6 support.
> * report the bugs found so they can be fixed.
>=20
> This situation was foreseen. Too many people just left this for
> later and later is here now and the fixes will come too late for
> some.
>=20
>> BUT... so what? you can do v4/v6 on the same LAN, right? just only use
>> the v4 bits for those devices?
>>=20
>> I don't think 'eh, toss out your crap, buy new crap' is the right
>> message to send. 'you can cohabitate, this isn't virginia' is though.
>>=20
>> -chris
> --=20
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
>=20
