[161241] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: What Should an Engineer Address when 'Selling' IPv6 to Executives?

daemon@ATHENA.MIT.EDU (Vincent C Jones)
Tue Mar 5 21:57:55 2013

Date: Tue, 05 Mar 2013 21:56:03 -0500
From: Vincent C Jones <v.jones@networkingunlimited.com>
In-reply-to: <006572C7-3081-4A73-A7C0-79B6A1DD6326@delong.com>
To: Owen DeLong <owen@delong.com>
Cc: NANOG list <nanog@nanog.org>
Reply-To: v.jones@networkingunlimited.com
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Tue, 2013-03-05 at 17:41 -0800, Owen DeLong wrote:
> 3.	We've actually been through this before. In some cases more than once.
> 	e.g.:
> 		Novell -> TCP/IP
> 		Windows Networking -> TCP/IP
> 		Appletalk -> TCP/IP
> 		NCP -> TCP/IP
> 
> 	In some ways, this change is less profound than many of those.

Lest we forget one of the more profound ones whose memory could be the
source of much resistance. Assuming this industry had any memory... 
                  TCP/IP -> MAP/TOP/GOSIP -> TCP/IP
Complete with government mandates, dual stacking, and RFP inclusion.
Been there, done that, been burnt... 

Vincent Jones



home help back first fref pref prev next nref lref last post