[161236] in North American Network Operators' Group
Re: What Should an Engineer Address when 'Selling' IPv6 to Executives?
daemon@ATHENA.MIT.EDU (Mike.)
Tue Mar 5 15:57:43 2013
In-Reply-To: <CAHDzDLDVdTNF1yspki+SezS+rEjXL3Ajh_oTZXHD3YMDGye4qA@mail.gmail.com>
Date: Tue, 05 Mar 2013 15:34:44 -0500
From: "Mike." <the.lists@mgm51.com>
To: "NANOG list" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 3/5/2013 at 9:55 PM Mukom Akong T. wrote:
|Dear experts,
|
|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.
|
|I think such a presentation (15 slides max in 45 minutes) should cover
the
|following aspects:
|
|a) Set the strategic context: how your organisation derives value from
IP
|networks and the Internet.
|
|b) Overview of the problem: IPv4 exhaustion
|
|c) Implications of IPv4 Exhaustion to your organization=E2=80=99s
business model.
|
|d) Introduction of IPv6 as a solution to IPv4 exhaustion.
|
|e) Understanding the risks involved.
|
|f) How much will deploying IPv6 will cost.
|
|g) Call to action.
|
|[snip]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Instead of
f) How much will deploying IPv6 will cost.
I would lean towards
f) Cost/benefit of deploying IPv6.
If you only talk about how much it will cost, then you've created a
major uphill battle for yourself. Also talk of how IPv6 will benefit
the business.
