Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!ucbcad!ucbvax!ARAMIS.RUTGERS.EDU!hedrick
From: hedrick@ARAMIS.RUTGERS.EDU (Charles Hedrick)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Networks & vendor upgrades/fixes
Message-ID: <8711220444.AA10224@aramis.rutgers.edu>
Date: Sat, 21-Nov-87 23:44:55 EST
Article-I.D.: aramis.8711220444.AA10224
Posted: Sat Nov 21 23:44:55 1987
Date-Received: Tue, 24-Nov-87 04:40:59 EST
References: <8711201833.AA25671@mitre.arpa>
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 14

> Source Code: So that an organization can fix/improve the code
> themselves, or by a third party, and not have to depend on the original
> vendor.  Does your recommendation change if software maintenance is in
> effect?

We have yet to see an organization that fixes things fast enough to
cope with our situation.  When a problem shows up, it shows up in
spades.  Like suddenly we are using the whole bandwidth of a T1 line
sending bogus name requests.  Now and then we'll call an organization
and have them say "oh yes, we know about this.  What is your UUCP
phone number?"  But otherwise, it is "fixed in the next release" or
at best fixed in a few days.  That are situations where we would have
to disable a crucial function during the interim.  So I consider it
crucial to have source for as much as possible.