Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!cbosgd!ucbvax!SUN.COM!nowicki
From: nowicki@SUN.COM (Bill Nowicki)
Newsgroups: mod.protocols.tcp-ip
Subject: Re: Do we need another protocol?
Message-ID: <8609292004.AA01618@rose.sun.com>
Date: Mon, 29-Sep-86 16:04:11 EDT
Article-I.D.: rose.8609292004.AA01618
Posted: Mon Sep 29 16:04:11 1986
Date-Received: Wed, 1-Oct-86 05:28:51 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 21
Approved: tcp-ip@sri-nic.arpa


	There is a growing trend in the Army to network Intel 310s
	running Xenix on a fat Ethernet under OpenNet.  When asked why
	OpenNet instead of TCP/IP, the answer most often heard is
	because OpenNet provides inter-machine file and record-level
	access at the application level.

Of course I am biased, but you might want to consider the Sun Network
File System (NFS) protocol.  NFS has the advantage of being 
available on many different machines and operating systems:
MS-DOS, many Unix versions, VMS etc. It is licensed by more than 60
vendors, and based on the IP protocol.  Specifications are public
domain, with fully-supported implementations avilable from several
sources. "Open" Net is quite a misnomer if it is only available from
one vendor.

I know, we should circulate an RFC form of the NFS spec; we are 
working on it.
	
	Bill Nowicki
	Sun Microsystems