[161296] in North American Network Operators' Group
Re: What Should an Engineer Address when 'Selling' IPv6 to Executives?
daemon@ATHENA.MIT.EDU (Jared Mauch)
Wed Mar 6 23:37:13 2013
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <95F2D89E-AF5C-431B-86F5-859EBB53B8AA@arbor.net>
Date: Wed, 6 Mar 2013 23:36:50 -0500
To: "Dobbins, Roland" <rdobbins@arbor.net>
Cc: NANOG General Mail List <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Mar 6, 2013, at 11:31 PM, "Dobbins, Roland" <rdobbins@arbor.net> =
wrote:
>=20
> On Mar 7, 2013, at 10:10 AM, Jerry Klonaper wrote:
>=20
>> It wasn't due to the lack of selling to executives, as this thread =
contends can be done, but due to the lack of any business case that =
could be found.
>=20
> Is the deployment in such a state that rollout can be resumed if/when =
it's deemed a priority?
>=20
> Another possible approach might be to utilize IPv6 for BYOD wireless - =
it's sort of the ultimate in device segregation.
The big problem I have (and with our own IT group) is that their network =
doesn't provide IPv6 yet we have offered it as a commercial service for =
a decade or more. This limits the ability to troubleshoot and dog-food =
the IPv6 network when using their resources. This means we stand up our =
own resources because they are unable to meet our needs. This is =
natural in many businesses, you work around what is broken or missing to =
get things done.
I would pitch it as follows: We need to at least have IPv6 access to =
troubleshoot/understand customers that have dual-stack technology. I =
found banks that would return NXDOMAIN instead of NOERROR when you asked =
for their domain name. This caused many problems until they corrected =
it. I actually got in contact with someone there by calling their whois =
contact. Was amazed that worked, but was a happy surprise.
- Jared=
