[comp.protocols.tcp-ip] Questions on IP & 802.2,3 & use or value of streams.

dougm@violet.ICO.ISC.COM ("Doug McCallum") (09/20/88)

In reply to your message of Fri, 16 Sep 88 15:56:19 EDT
-------

> 1) Anyone using IP over 802.2 LLC or 802.3 MAC layers in commerical or
> academic products? (Commercial folks are interested in having their
> products conform to "standards").

I don't know if it is in very wide use, but there are a number of vendors
that support it as an option.

> 2) What is ATT's streams used for: like Berkeley's sockets, to provide
> access to protocol families? Is there a "native" streams protocol or
> protocol suite? And more concrete: just like TCP/IP is being or will be
> delivered with streams, are there other protocol suits available
> (commerically or otherwise) with a streams interface?, say ISO's?

AT&T STREAMS is a framework in which to implement communications protocols.
There is no native Streams protocol.  That is, with a generic base system
you get no communications protocols, just the tools to implement them.  TLI
is the AT&T equivalent to sockets in the V.3 environment.  There has been
much discussion about TLI vs. sockets in this group in the past so I won't
get into that.

There are a number of protocol suites available.  A number of vendors have
TCP/IP implementations.  There are also ISO and XNS implementations that I
know of plus some others proprietary to various vendors.

bae@unisoft.UUCP (Hwa Jin Bae) (09/27/88)

> 1) Anyone using IP over 802.2 LLC or 802.3 MAC layers in commerical or
> academic products? (Commercial folks are interested in having their
> products conform to "standards").

There are a few such products including one from us.  Usually it is
done by using a 802.2 LLC header with DSAP and SSAP value 170 and 
Control value 3 (unnumbered info.) along with a SNAP header to indicate
ethernet type field since the 802.3 doesn't have a type field, with
Protocol Id equal to 0.

> 2) What is ATT's streams used for: like Berkeley's sockets, to provide
> access to protocol families? Is there a "native" streams protocol or
> protocol suite? And more concrete: just like TCP/IP is being or will be
> delivered with streams, are there other protocol suits available
> (commerically or otherwise) with a streams interface?, say ISO's?

STREAMS provides a general environment to implement a networking protocol
or device drivers.  Several implementations use STREAMS different ways to
implement TCP/IP.  Some are straight ports of 4.3 BSD TCP/IP with additional
code for multiplexing modules at TCP and IP levels.  At LLC level these
implementations usually use another module that understand M_PROTO messages
of various kinds that sort of simulates (implements) 802.2 like services
to be used by upper layer module (IP multiplexor).  Others (like ours)
work different way but in general STREAMS implementations do try to follow 
the "standard" stacks as closely as possible for better or worse.  
There are some interesting issues involved in optimizing flow control 
algorithms with STREAMS based protocol implementations.

/hjb
-- 
I only speak for myself.
Hwa Jin Bae				bae@tis.llnl.gov	(Internet)
UniSoft					bae@unisoft.UniSoft	(smail uucp)
Emeryville, CA				...!uunet!unisoft!bae	(plain uucp)