Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!ut-sally!husc6!rutgers!ucla-cs!zen!ucbvax!MONK.PROTEON.COM!jas From: jas@MONK.PROTEON.COM (John A. Shriver) Newsgroups: comp.protocols.tcp-ip Subject: Streams TCP/IP Message-ID: <8707271643.AA23231@monk.proteon.com> Date: Mon, 27-Jul-87 12:43:24 EDT Article-I.D.: monk.8707271643.AA23231 Posted: Mon Jul 27 12:43:24 1987 Date-Received: Tue, 28-Jul-87 04:52:42 EDT References: <24072@sun.uucp> Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 12 Read the AT&T SVR3 license agreement about SVID (System V Interface Dovcument) compliance. That's why STREAMS is the only game in town. If you sell a UNIX System under the binary licensing provisions of SVR3, and it has networking, that networking MUST conforn to the SVID networking extnesions, which include STREAMS as the TLI. While you could provide the socket() interface as well, you must provide STREAMS. The SVID requirements have caused a lot of UNIX vendors to not upgrade from SVR2 to SVR3, despite the more attractive binary license pricing. It makes it very difficult to provide 4.3BSD functionality, since you've also got to provide SVR3/SVID/SVVS compatability.