[98068] in North American Network Operators' Group
Re: An Internet IPv6 Transition Plan
daemon@ATHENA.MIT.EDU (James R. Cutler)
Tue Jul 24 13:48:23 2007
Date: Tue, 24 Jul 2007 13:15:24 -0400
To: nanog@merit.edu
From: "James R. Cutler" <james.cutler@consultant.com>
In-Reply-To: <87f7bba70707240850n20c5ff1dl7ac24adea08fb832@mail.gmail.co
m>
Errors-To: owner-nanog@merit.edu
--=====================_103634138==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cost of operating v4/v6 combined for some time includes, among other things:
1. Help Desk calls resulting from confused customers wanting
configuration help.
2. Memory for Routing Information for IPv4 plus IPv6.
3. Help Desk calls resulting from errors by confused engineers
trying to work both protocols on too many devices.
4. Cost of documentation and training for Help Desk personnel.
5. Cost of "Linksys WRT54G-IP6" or equivalent because of increased
memory and programming requirements.
6. Cost of software maintenance for network core router software --
didn't we just go through getting rid of DECnet, SNA, IPX/SPX, and
AppleTalk because of this, among other reasons??
7. Marketing cost of being perceived as "obsolete".
8. Opportunity cost due to more complex delivery configurations
slowing down sales.
9. Cost of "IP Naming and Addressing Management" due to multiple
protocol complexity -- didn't we just go through getting rid of
DECnet, SNA, IPX/SPX, and AppleTalk because of this, among other reasons??
Of course, this is just a smattering. Note also that, although
hardware costs for the router core are driven primarily by speed and
port count, memory costs can be substantial.
At 7/24/2007 11:50 AM -0400, Chad Oleary wrote:
<snip/>
However, what I'm trying to understand is why the motivation to
rapidly go from v4 to v6 only? What are the factors I'm missing in
operating v4/v6 combined for some time?
Chad
-
James R. Cutler
james.cutler@consultant.com
--=====================_103634138==.ALT
Content-Type: text/html; charset="us-ascii"
<html>
<body>
<font size=3>Cost of operating v4/v6 combined for some time includes,
among other things:<br><br>
1. Help Desk calls resulting from confused customers wanting
configuration help.<br>
2. Memory for Routing Information for IPv4 plus IPv6.<br>
3. Help Desk calls resulting from errors by confused engineers
trying to work both protocols on too many devices.<br>
4. Cost of documentation and training for Help Desk personnel.<br>
5. Cost of "Linksys WRT54G-IP6" or equivalent because of
increased memory and programming requirements.<br>
6. Cost of software maintenance for network core router software --
didn't we just go through getting rid of DECnet, SNA, IPX/SPX, and
AppleTalk because of this, among other reasons??<br>
7. Marketing cost of being perceived as "obsolete".<br>
8. Opportunity cost due to more complex delivery configurations
slowing down sales.<br>
9. Cost of "IP Naming and Addressing Management" due to
multiple protocol complexity -- didn't we just go through getting rid of
DECnet, SNA, IPX/SPX, and AppleTalk because of this, among other
reasons?? <br><br>
Of course, this is just a smattering. Note also that, although
hardware costs for the router core are driven primarily by speed and port
count, memory costs can be substantial. <br>
<br><br>
At 7/24/2007 11:50 AM -0400, Chad Oleary wrote:<br>
<snip/><br>
However, what I'm trying to understand is why the motivation to<br>
rapidly go from v4 to v6 only? What are the factors I'm missing in<br>
operating v4/v6 combined for some time?<br><br>
Chad<br>
</font><x-sigsep><p></x-sigsep>
<font face="Courier, Courier" size=3>-<br>
James R. Cutler<br>
james.cutler@consultant.com<br>
</font></body>
</html>
--=====================_103634138==.ALT--
