[161301] in North American Network Operators' Group
Re: What Should an Engineer Address when 'Selling' IPv6 to Executives?
daemon@ATHENA.MIT.EDU (John Curran)
Thu Mar 7 02:23:08 2013
X-Report-Abuse-To: abuse@dyndns.com (see
http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse
reporting information)
From: John Curran <jcurran@istaff.org>
In-Reply-To: <CAK__Kzu7JnqV6UTdnNE25-yj6iKUzOU=LRUdanQ2M-WUcFSEHg@mail.gmail.com>
Date: Thu, 7 Mar 2013 02:21:55 -0500
To: George Herbert <george.herbert@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Mar 6, 2013, at 3:13 PM, George Herbert <george.herbert@gmail.com> wrote:
> ...
> I'm sorry, but a lot of organizations' response to IPv6 has been "Ok,
> desktops will need an overlay of it for some websites in AP next year,
> so we'll do that. And we need an IPv6 front end visibility for our
> website.
If nothing else, it's worthing giving that last point some priority
(i.e. "And we need an IPv6 front end visibility for our website.")
While the Internet is greater than the web, the more public facing
servers reachable by IPv6, the more functional IPv6 is as an IPv4
substitute for connecting customers to the Internet.
/John
