Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!CUNYVM.CUNY.EDU!PIRARD%vm1.ulg.ac.be
From: PIRARD%vm1.ulg.ac.be@CUNYVM.CUNY.EDU (Andr'e PIRARD)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: TCP/IP, PC LAN, and token ring
Message-ID: <9102080433.aa10227@louie.udel.edu>
Date: 8 Feb 91 08:58:15 GMT
References: <OWEN@DUCVAX.AUBURN.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 27

On Mon, 4 Feb 91 15:25:00 CST Larry Owen said:
>...
>approaches:
>  2. A stack written to the ASI interface, allowing NetBIOS traffic
>     to be multiplexed with the ip traffic (using IBM's device drivers,
>     which, if I understand IBM's marketing, is the PC LAN Support
>     Program).  The vendors that I *think* support this are FTP,
>     Wollongong, and IBM.  Is this correct?  Are there others?
>     What about U. of Maryland's stuff?

Yes, both OS/2 CM and PC's LAN support program are of the best OSI layering
and will multiplex (these) network protocols.
For OS/2, IBM's TCP/IP should be the standard for the other layers.
For the PC, use the T/R packet drivers on top on LAN SP, for example.
Only one of the possibilities, unhappily.
I wish a standard be established on the PC for common data link, network
and transport APIs so that PC TCP/IP application writers could concentrate
on applications, administrators install and configure these interfaces "once
in a life" and users choose any application and install them at minimal risk.
Of a stack of choice, I see DIS, the packet drivers and FTP Software's
socket API. The application API should support the multitasking additions to
MSDOS, mainly DESQview and MS Windows, for true TCP/IP on MSDOS.
Take MacTCP as an example.

Andr'e PIRARD             SEGI, Univ. de Li`ege
B26 - Sart Tilman         B-4000 Li`ege 1 (Belgium)
pirard@vm1.ulg.ac.be  or  PIRARD%BLIULG11.BITNET@CUNYVM.CUNY.EDU