Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!cit-vax!ucla-cs!zen!ucbvax!ulysses!hector!ekrell
From: ekrell@hector.UUCP (Eduardo Krell)
Newsgroups: comp.sys.att
Subject: Re: RFS for TCP/IP
Message-ID: <3168@ulysses.homer.nj.att.com>
Date: Mon, 16-Nov-87 10:23:29 EST
Article-I.D.: ulysses.3168
Posted: Mon Nov 16 10:23:29 1987
Date-Received: Wed, 18-Nov-87 02:20:44 EST
References: <521@udiego.UUCP>
Sender: daemon@ulysses.homer.nj.att.com
Reply-To: ekrell@hector (Eduardo Krell)
Organization: AT&T Bell Labs, Murray Hill
Lines: 21
Keywords: Comming Soooooooon!!

In article <521@udiego.UUCP> stokes@udiego.UUCP writes:
>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.

It seems you're asking the wrong question: RFS doesn't need to be
changed to run over TCP/IP or any other transport protocol. RFS is
both protocol- and network- independent.  If you have a TCP/IP
kernel driver that speaks TLI (the streams-based AT&T Transport
Level Interface), you can run RFS on top of it. Period.

Now, if your question is when is AT&T going to provide a TCP/IP
driver and user-level programs (ie, the BSD networking programs)
for the 3B2's running under SVR3, then the answer is (I think)
that it's already available from Wollongong (an outside vendor).
    
    Eduardo Krell                   AT&T Bell Laboratories, Murray Hill

    {ihnp4,seismo,ucbvax}!ulysses!ekrell