Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!ucsd!helios.ee.lbl.gov!nosc!cod!neerma
From: neerma@cod.NOSC.MIL (Merle A. Neer)
Newsgroups: comp.protocols.tcp-ip
Subject: TCP IP vendor selection
Message-ID: <1711@cod.NOSC.MIL>
Date: 30 Nov 89 16:59:09 GMT
Reply-To: neerma@cod.nosc.mil.UUCP (Merle A. Neer)
Distribution: comp.protocols.ibm-pc.tcp-ip
Organization: Naval Ocean Systems Center, San Diego
Lines: 54

The Distributed Command and Control project (DC2) at
NOSC is an attempt to bring Naval command and control
systems into the networking arena by frontending them
with PC-ATs.  The microcomputers perform the TCP-IP
function transparently for the Naval systems.  This
project began strictly as an R&D laboratory experiment
but has now progressed to the point where shipboard
installations have begun.  The operational environment,
however, requires 'hardening' of the network frontends
(NIUs).  We have had a difficult time in achieving the
hardening of the NIUs.  The problems stem from the
poor quality of the commercial TCP-IP packages we have
tried.  In April 1988 our contractors were tasked to
evaluate several TCP-IP packages for use in the NIUs.
Their conclusion: none of the packages examined satisfy
the requirements of the NIU.  The problems identified:
1. inability to handle more than 2 or 3 connects per
socket 2. inability to close/reopen a connect 3. poor
and inaccurate documentation 3. violation of the TCP
window management specification 4. bugs in networking
code (usually results in hung or crashed system)
and almost UNIVERSALLY 5. lousy technical support.
The vendors examined during this study: Network
Research FUSION, Exelan, CMC and FTP Software.

We have reached a point of frustration.  Our current
strategy is to: 1. wait for CMC to fix a bug in their
ROM for their ether card (since the rest of their stuff
looks o.k. so far, 2. look at the public domain KA9Q
(advantage: sources), 3. wait for FTP Software to fix
their socket library 4. look at Woolongong (havent tried
them yet) 5. write our own?

Most of these packages work when run with the vendors
own applications (FTP, Telnet, etc.).  Most I believe
work if the PC wants to open one connection, send a 
little data, and that s all.  We program the PCs to be
network servers: must maintain multiple connections,
must recover from opening/closing connections, MUST
implement TCP window mechanism because our clients
often send much data to server, must provide a socket
interface (somewhat of a standard), MUST WORK!

If we could find a vendor with a product as described
we would anticipate buying more than a few packages as
the Navy has a lot of ships with lots of command and
control systems and soon to have lots of networks.
So far, however, we cant get any package out of the lab.

Does anyone want such a customer?

Merle Neer
neerma at nosc.mil
(619)553-3974


Brought to you by Super Global Mega Corp .com