Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!caip!nike!ucbcad!ucbvax!VTVAX3.BITNET!JARRELLRA
From: JARRELLRA@VTVAX3.BITNET (Ronald A. Jarrell)
Newsgroups: mod.protocols.tcp-ip
Subject: nsfnet
Message-ID: <8609040559.AA16708@ucbvax.Berkeley.EDU>
Date: Thu, 4-Sep-86 02:01:55 EDT
Article-I.D.: ucbvax.8609040559.AA16708
Posted: Thu Sep  4 02:01:55 1986
Date-Received: Thu, 4-Sep-86 05:20:02 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 17
Approved: tcp-ip@sri-nic.arpa



We plan on hooking to nsfnet in the near future, probably through a sattelite
link and an imp.  We were going to be running Wollongong's WIN on the Vaxes,
but I've been told we are going to have a horrible time with it, that it
wouldn't work with out a lot of kluding.. Anyone have suggestions as to a
good, full-function, tcpip package to use in this situation?  It would
need ddn protocol support, and be able to talk to unix flavor systems.

Please also mention whether or not it would require new hardware, or if
we could share the deuna we currently have for decnet and lat.


Also, while I'm thinking of it, anyone have PD or non-PD code for domain
support for a VMS system?

-Ron