Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!lll-tis!lll-ati.arpa!narayan
From: narayan@lll-ati.arpa (Narayan Moharram)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: standard interface
Message-ID: <21847@lll-tis.arpa>
Date: Fri, 20-Nov-87 17:39:40 EST
Article-I.D.: lll-tis.21847
Posted: Fri Nov 20 17:39:40 1987
Date-Received: Sun, 22-Nov-87 16:03:39 EST
References: <301@halley.UUCP> <8711140117.AA08165@violet.berkeley.edu> <304@halley.UUCP>
Sender: nobody@lll-tis.arpa
Reply-To: narayan@lll-ati.arpa (Narayan Moharram)
Organization: Lawrence Livermore National Laboratory, Livermore CA
Lines: 24

In article <304@halley.UUCP> bc@halley.UUCP (Bill Crews) writes:
>
>
>Uh, what does that mean?  What else would one do?  You aren't proposing
>contaminating the socket interface with knowledge of the underlying transport,
>are you?  Do you want a TCP interface or a transport-protocol-independent
>interface, like sockets or TLI?
>
>> [...]
>
>>    In Bill Crews message (<301@halley.UUCP>), he mentions a TLI.
>>I would like more information on this interface.
>
>OK.  TLI is a part of Unix System V.3 network services.  I would imagine that
>most V.3 manual sets will contain TLI documentation.  I've been using
>the Unix System V Network Programmer's Guide for the AT&T 3Bs.  Other very
>interesting reading can be found in the Unix System V STREAMS Programmer's
>Guide and the STREAMS Primer.  Now, TLI doesn't imply STREAMS and STREAMS
>doesn't imply TLI.  They are both good ideas, though, and are both implemented
>in V.3.

If you don't have an AT&T lisence (sp?) you can get a identical
interface from XOPEN. They call it XTI, and it is essentially the
same thing.