Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!bellcore!faline!ulysses!sfmag!mjp
From: mjp@sfmag.UUCP (M.J.Purdome)
Newsgroups: comp.sys.att
Subject: Re: RFS for TCP/IP
Message-ID: <1177@sfmag.UUCP>
Date: Sun, 15-Nov-87 21:17:45 EST
Article-I.D.: sfmag.1177
Posted: Sun Nov 15 21:17:45 1987
Date-Received: Tue, 17-Nov-87 02:12:37 EST
References: <521@udiego.UUCP>
Organization: AT&T Information Systems, Summit, NJ
Lines: 28

> i was talking to the phone support people and asked the $64,000
> question: 'When is RFS for TCP going to be written?'
> 
> The answer was that it was being tested inhouse. The libraries are
> scheduld to be tested the week of Nov. 16th.
> 
> 
> Hopefully, AT&T won't sit on this too long!
> 
> -- 
> David Stokes                   "USD where the future is tomorrow
> Academic Computing Department   and today is slightly behind schedule"
> University of San Diego
> (619) 260-4810 or {sdcsvax, sdsu, ucsdhub}!udiego!stokes


Actually, RFS is media- and protocol-independent.  RFS 1.1 runs over TCP/IP
just fine...

Keep in mind that the TCP/IP MUST be the STREAMS-based TCP/IP recently 
announced by AT&T (Version 2.1, I think).  The character-based version 
of TCP/IP won't work.
-- 

    Mark Purdome      AT&T UNIX System Development Laboratory
                      190 River Road A-130, Summit, NJ  07901
                      {ihnp4,allegra}!attunix!mjp
    disclaimer: these statements do not represent AT&T policies or opinions