[161238] in North American Network Operators' Group
Re: What Should an Engineer Address when 'Selling' IPv6 to Executives?
daemon@ATHENA.MIT.EDU (Owen DeLong)
Tue Mar 5 20:47:34 2013
From: Owen DeLong <owen@delong.com>
In-Reply-To: <CAHDzDLDVdTNF1yspki+SezS+rEjXL3Ajh_oTZXHD3YMDGye4qA@mail.gmail.com>
Date: Tue, 5 Mar 2013 17:41:36 -0800
To: "Mukom Akong T." <mukom.tamon@gmail.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I think it's also important to cover the following topics somewhere in =
the process:
1. This will affect the entire organization, not just the IT =
department and
will definitely impact all of apps, sysadmin, devops, =
operations, and
networking teams within the IT department.
2. Training will be required for virtually all levels of the =
organization. End users
won't need more than a ~2 hour introduction to what to look for =
during and
after the upcoming changes. The IT department will need =
substantial training,
covering a wide variety of topics (application changes =
(development, configuration,
testing, management), systems administration changes, networking =
changes, etc.)
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.
It's also worth pointing out the ways you can save by starting sooner =
rather than later.
Owen
On Mar 5, 2013, at 9:55 AM, Mukom Akong T. <mukom.tamon@gmail.com> =
wrote:
> Dear experts,
>=20
> I've found myself thinking about what ground an engineer needs to =
cover in
> order to convince the executives to approve and commit to an IPv6
> Deployment project.
>=20
> I think such a presentation (15 slides max in 45 minutes) should cover =
the
> following aspects:
>=20
> a) Set the strategic context: how your organisation derives value from =
IP
> networks and the Internet.
>=20
> b) Overview of the problem: IPv4 exhaustion
>=20
> c) Implications of IPv4 Exhaustion to your organization=92s business =
model.
>=20
> d) Introduction of IPv6 as a solution to IPv4 exhaustion.
>=20
> e) Understanding the risks involved.
>=20
> f) How much will deploying IPv6 will cost.
>=20
> g) Call to action.
>=20
> I've detailed my thinking into each of these items at <How to =91Sell=92=
IPv6
> to Executive Management =96 Guidance for
> =
Engineers<http://techxcellence.net/2013/03/05/v6-business-case-for-enginee=
rs/>
>>=20
>=20
> My question and this is where I'd appreciate some input:
>=20
> a) To all you engineers out there who have convinced managers - what =
else
> did you have to address?
>=20
> b) To you who are managers, what else do you need your engineers to =
address
> in order for you to be convinced?
>=20
> Regards.
>=20
> As always, all opinions expressed are mine and do not necessarily =
represent
> the views of my employers, past or present.
>=20
> --=20
>=20
> Mukom Akong T.
>=20
> http://about.me/perfexcellence | twitter: @perfexcellent
> =
--------------------------------------------------------------------------=
----------------------------------------------------------------
> =93When you work, you are the FLUTE through whose lungs the whispering =
of the
> hours turns to MUSIC" - Kahlil Gibran
> =
--------------------------------------------------------------------------=
-----------------------------------------------------------------
> --=20
>=20
> Mukom Akong T.
>=20
> http://about.me/perfexcellence | twitter: @perfexcellent
> =
--------------------------------------------------------------------------=
----------------------------------------------------------------
> =93When you work, you are the FLUTE through whose lungs the whispering =
of the
> hours turns to MUSIC" - Kahlil Gibran
> =
--------------------------------------------------------------------------=
-----------------------------------------------------------------
