Newsgroups: comp.protocols.tcp-ip
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!barryf
From: barryf@aix01.aix.rpi.edu (Barry B. Floyd)
Subject: Re: Public domain NFS
Message-ID: <v65fsrg@rpi.edu>
Nntp-Posting-Host: aix01srv.aix.rpi.edu
References: <9103191437.AA18198@ftp.com> <1161@cthulhuControl.COM> <40519@cup.portal.com>
Date: 25 Mar 91 15:45:17 GMT
Lines: 30

FelineGrace@cup.portal.com (Dana B Bourgeois) writes:

>Just got my hands on RFC 1094 (NFS) and it didn't seem to say anything
>about licensing.  Off-hand (not being a lawyer) I didn't see anything
>that would stop me from taking the RFC and creating my own brand of NFS
>for Computer 'X'.  Is there something that keeps me from writing my own
>NFS?  Distributing it or selling it?  If so what and why?

>Thanks in advance
>Dana Bourgeois @ cup.portal.com
>"Be EXCELLENT to each other!"  Bob and Ted's Great Adventure.
 
I am no expert on these matters, either. It is my understanding that
"nfs" is based on RPC nad NDR (?) BOTH are public domain. If you can
take RFC 1094, RPC and NDR and mix them together to get a working
"nfs", you got yourself a commercial product or shareware (as you see fit).
 
Obviously your implementation may differ significantly in detail to Sun,
B&W, FTP Software's incarnations. They all should perform the same functions
though, in accordence with RFC 1094.
 
my 2 cents worth...
 
barry

-- 
+--------------------------------------------------------------------+ 
| Barry B. Floyd                   \\\       barry_floyd@mts.rpi.edu |
| Manager Information Systems - HR    \\\          usere9w9@rpitsmts |
+-Rensselaer Polytechnic Institute--------------------troy, ny 12180-+
