Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ptsfa!ihnp4!occrsh!occrsh.ATT.COM!gorgo.UUCP!authorplaceholder
From: bsteve@gorgo.UUCP
Newsgroups: comp.sys.att
Subject: Re: NPACK protocol
Message-ID: <58300006@gorgo.UUCP>
Date: Mon, 13-Apr-87 17:45:00 EST
Article-I.D.: gorgo.58300006
Posted: Mon Apr 13 17:45:00 1987
Date-Received: Fri, 24-Apr-87 05:18:02 EST
References: <242@pyuxe.UUCP>
Lines: 28
Nf-ID: #R:pyuxe.UUCP:-24200:gorgo.UUCP:58300006:000:766
Nf-From: gorgo.UUCP!bsteve    Apr 13 16:45:00 1987


>  Does RFS run over it?
  YES.

>  Is it writtten to interface to the AT&T Transport provider?
  YES.

>Dose it provied connection/connectionless oriented service?
  YES.

>What levels of the ISO protocol model does it correspond to? 
  Same as STARLAN protocol layers.

>Any word on performance?
  I have used it and it provides reasonably fast remote file-sharing.

>The information that AT&T has provided just isn't enough
>to justify the purchase of this product ($5,000).
  So it goes.

>If it could support RFS and uucp on SYSV 3.0/3.1,
>it might be attractive since the binary sublicensing fees 
>are resonable ($5,000 one time + $10 per copy).
  It supports both RFS and UUCP under SVR3.[01].

  Steve Blasingame
  bsteve@gorgo.att.com
  ihnp4!gorgo!bsteve