Re: [tae] The internet architecture
Keith Moore <moore@network-heretics.com> Fri, 05 December 2008 21:29 UTC
Return-Path: <tae-bounces@ietf.org>
X-Original-To: tae-archive@ietf.org
Delivered-To: ietfarch-tae-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 9B9593A6BE2;
Fri, 5 Dec 2008 13:29:44 -0800 (PST)
X-Original-To: tae@core3.amsl.com
Delivered-To: tae@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 24C003A6BE2
for <tae@core3.amsl.com>; Fri, 5 Dec 2008 13:29:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.502
X-Spam-Level:
X-Spam-Status: No, score=-2.502 tagged_above=-999 required=5 tests=[AWL=0.097,
BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id KdvpAdvZzJ3e for <tae@core3.amsl.com>;
Fri, 5 Dec 2008 13:29:42 -0800 (PST)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131])
by core3.amsl.com (Postfix) with ESMTP id 4F0BA3A6BC2
for <tae@ietf.org>; Fri, 5 Dec 2008 13:29:42 -0800 (PST)
Received: from lust.indecency.org (adsl-242-100-137.tys.bellsouth.net
[74.242.100.137]) by m1.imap-partners.net (MOS 3.10.3-GA)
with ESMTP id BFC60878 (AUTH admin@network-heretics.com)
for tae@ietf.org; Fri, 5 Dec 2008 13:29:35 -0800 (PST)
Message-ID: <49399D3D.1090409@network-heretics.com>
Date: Fri, 05 Dec 2008 16:29:33 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
References: <C15AE32B-E564-4C93-86FF-40EF203E673A@mpi-sws.org>
<49382030.5020704@network-heretics.com>
<200812051425.mB5EPKEG032766@cichlid.raleigh.ibm.com>
<493950CE.1070202@network-heretics.com>
<200812051834.mB5IY0Ov008202@cichlid.raleigh.ibm.com>
<49399159.8000205@network-heretics.com>
<200812052103.mB5L3C0j024903@cichlid.raleigh.ibm.com>
In-Reply-To: <200812052103.mB5L3C0j024903@cichlid.raleigh.ibm.com>
Cc: tae@ietf.org, ietf@ietf.org, Bryan Ford <brynosaurus@gmail.com>
Subject: Re: [tae] The internet architecture
X-BeenThere: tae@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Architecture Evolution <tae.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tae>,
<mailto:tae-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tae>
List-Post: <mailto:tae@ietf.org>
List-Help: <mailto:tae-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tae>,
<mailto:tae-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tae-bounces@ietf.org
Errors-To: tae-bounces@ietf.org
Thomas Narten wrote: >> I suppose it follows that people don't actually need those applications >> to work in order to continue doing business... in which case, of course >> they shouldn't upgrade them. > > Keith, this is umbelievably simplisitic logic. This whole discussion is unbelievably simplistic logic. Insults don't make the logic any better. > The applications run today. Important things would > break if they were turned off. But there is no money to pay for an > upgrade (by the customer) because the budget is only so big, and the > current budget was more focussed on beefing up security and trying to > get VoIP running. Or, the vendor doesn't have an upgrade because the > product is EOL, and the customer can't afford to buy a replacement for > it (again for a number of different reasons). Or, the vendor does have > an upgraded product, but it requires running the latest version of the > product, which doesn't run on the OS release you happen to be running > (and can't change for various reasons), and would require new hardware > on top of things because the new product/OS is a memory pig, or was > rewritten in Java, etc., etc. Yep. I've seen it happen many times in various guises. By now it is widely understood that many things need maintenance budgets - e.g. buildings, vehicles, computer and networking hardware. And we actually have a decent sense of how much to budget for those things. But we don't have a widely-understood idea of what it costs to maintain software, particularly networking software. There's both a strong tendency to believe that software is fixed-cost and an increasing tendency to fire in-house programmers and push things like software maintenance to third parties - which is to say, they don't get paid for. But when the Internet keeps changing (for many more reasons than IPv4 address space exhaustion) you can't expect the software to stay static and keep working well. >> Either that, or the people who are making these decisions don't really >> understand what's important to keeping their businesses running... and >> those businesses will fail. > > They may understand very well. But a simple cost/benefit analysis (in > terms of $$ and/or available technical resources) says they can't > afford to upgrade. > > Happens all the time. Why do you think people run old software for > years and years and years? Most likely, because they aren't properly estimating cost and/or benefit, or because they are too focused on short-term costs and ignoring medium- and long-term costs. Keith _______________________________________________ tae mailing list tae@ietf.org https://www.ietf.org/mailman/listinfo/tae
- Re: [tae] The internet architecture Bryan Ford
- Re: [tae] The internet architecture Keith Moore
- Re: [tae] The internet architecture Hallam-Baker, Phillip
- Re: [tae] The internet architecture Keith Moore
- Re: [tae] The internet architecture Hallam-Baker, Phillip
- Re: [tae] The internet architecture Keith Moore
- Re: [tae] The internet architecture John Leslie
- Re: [tae] The internet architecture Joe Touch
- Re: [tae] The internet architecture Keith Moore
- Re: [tae] The internet architecture Thomas Narten
- Re: [tae] The internet architecture Thomas Narten
- Re: [tae] The internet architecture Henning Schulzrinne
- Re: [tae] The internet architecture Dave CROCKER
- Re: [tae] The internet architecture Melinda Shore
- [tae] sockets vs. fds Dave CROCKER
- Re: [tae] The internet architecture John Day
- Re: [tae] sockets vs. fds Melinda Shore
- Re: [tae] The internet architecture John Day
- Re: [tae] The internet architecture John Day
- Re: [tae] The internet architecture Keith Moore
- Re: [tae] The internet architecture Keith Moore
- Re: [tae] The internet architecture Keith Moore
- Re: [tae] The internet architecture Keith Moore
- Re: [tae] The internet architecture Dave CROCKER
- Re: [tae] The internet architecture John Day
- Re: [tae] The internet architecture John Day
- Re: [tae] The internet architecture Thomas Narten
- Re: [tae] The internet architecture Keith Moore
- Re: [tae] The internet architecture Thomas Narten
- Re: [tae] The internet architecture Keith Moore
- Re: [tae] sockets vs. fds Tony Finch
- Re: [tae] The internet architecture David W. Hankins
- Re: [tae] The internet architecture Hallam-Baker, Phillip
- Re: [tae] sockets vs. fds Florian Weimer
- [tae] The Great Naming Debate (was Re: The intern… Bryan Ford
- Re: [tae] The Great Naming Debate (was Re: The in… Keith Moore
- Re: [tae] The Great Naming Debate (was Re: The in… Joe Baptista
- Re: [tae] The Great Naming Debate (was Re: The in… Hallam-Baker, Phillip
- Re: [tae] The Great Naming Debate (was Re: The in… Melinda Shore
- Re: [tae] The Great Naming Debate (was Re: The in… Hallam-Baker, Phillip
- Re: [tae] The Great Naming Debate (was Re: The in… Keith Moore
- Re: [tae] The internet architecture John Leslie