Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!nsl.dec.com!dcrocker
From: dcrocker@nsl.dec.com (Dave Crocker)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: UDP bind question
Message-ID: <9002150009.AA02350@dcrocker.pa.dec.com>
Date: 15 Feb 90 00:09:04 GMT
References: <HWAJIN.90Feb7145434@ganges.wrs.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 13

"the UDP/IP.  The system calls (whether you use bind() or t_bind()) get turned
into STREAMS messages as they pass through the STREAM heads with types that TPI
multiplexor module understands (in case of bind request it would be"

Let me caution you.  Each Streams implementation of TCP/IP appears to be
quite different, in its interface both to sockets() and TLI.  Especially
TLI.  The semantics for sockets() are well-defined, by virtue of having
the BSD code as the reference implementation.  However, the mapping
of TLI syntax and semantics into TCP functionality is subject to
considerable interpretation.  Such flexibility is, always, exercised when
there are multiple implementors.  It is the great fun of open systems.

Dave