Path: utzoo!attcan!uunet!husc6!mailrus!uwmcsd1!ig!agate!ucbvax!MAILGW.CC.UMICH.EDU!rees
From: rees@MAILGW.CC.UMICH.EDU (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: Domain tcp VS. bsd tcp
Message-ID: <8808162024.AA00241@mailgw.cc.umich.edu>
Date: 16 Aug 88 18:10:35 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: rees@caen.engin.umich.edu (Jim Rees)
Organization: The Internet
Lines: 30


         Just a quick question: what are the differences between what
    Apollo calls domain/ix (or bsd) tcp/ip, and domain tcp. We've read and
    reread the documentation we have and it still isn't clear.  The only
    thing I can figure is the domain tcp was invented/written before the
    Unix stuff was fully implemented, and was used primarily to bridge
    between ringnets. When bsd tcp was implemented, the older product
    became obsolete.  Is this speculation true, somewhat true, or complete
    garbage?

First, there was domain tcp.  It didn't use sockets, in fact it didn't
use a stream (ios) interface at all.  It was not based on Berkeley code.

Over the years it acquired first a stream interface, then a socket
interface.  Once that was done, it became possible to port the Berkeley
user commands (telnet, ftp, etc).  Both the original set of user
commands and the Berkeley set co-existed for a while, but the protocol
engine has always been shared between the "domain" and "bsd" tcps.  Some
other user space things, like host tables, also had separate
implementations.

The separate implementations were done partly for licensing reasons. It
didn't seem proper to make people buy a Unix license in order to run
tcp.  Now you get a license "free" with every node, so that's not an
issue any more.

At sr10, the "domain" user commands and host tables go away, and all you
have is the "bsd" stuff.  Also, tcp is bundled in with the base product,
not sold separately.
-------