Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!bellcore!ulysses!ucbvax!CSNET-RELAY.ARPA!BOLTHOUSE%MCCORE%ti-eg.CSNET
From: BOLTHOUSE%MCCORE%ti-eg.CSNET@CSNET-RELAY.ARPA (Anyone who tangos has a l
Newsgroups: mod.computers.vax
Subject: TCP/IP implementations for VAX/VMS 4.2 and later
Message-ID: <8605310306.AA04475@ucbvax.Berkeley.EDU>
Date: Fri, 30-May-86 23:07:04 EDT
Article-I.D.: ucbvax.8605310306.AA04475
Posted: Fri May 30 23:07:04 1986
Date-Received: Sat, 31-May-86 15:54:09 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 28
Approved: info-vax@sri-kl.arpa


I am interested in any and all information you may have regarding TCP/IP
implementations for VAX/VMS 4.2 and beyond.  Such info might include war
stories, technical support experiences, security concerns, relative
performance estimates, relative capability comparisons, coexistence with
DECnet, flames, etc.  Currently, I am aware of the following vendors:

Wollongong
Network Research Corp.
Excelan
Interlan

Ethernet would be the preferred medium; however, it is always possible a
leased line or (gads) an asynchronous line might be used at some point
or another.  Please reply directly to me; I will summarize my findings
to the net.

David L. Bolthouse

net:         bolthouse%mccore@ti-eg.csnet
ma bell:     (214) 952-2059
us snail:    ms 8006
             po box 801
             mckinney, tx 75069

standard disclaimer:  anyone who thinks i represent the views of my employer
                      should be sentenced to a week spent in a small room
                      with a lawyer...