Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:2988 comp.os.linux.misc:20845 Newsgroups: comp.os.386bsd.misc,comp.os.linux.misc Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!constellation!news.uoknor.edu!ns1.nodak.edu!netnews.nwnet.net!reuter.cse.ogi.edu!cs.uoregon.edu!usenet.ee.pdx.edu!fastrac.llnl.gov!lll-winken.llnl.gov!ames!elroy.jpl.nasa.gov!usc!nic-nac.CSU.net!charnel.ecst.csuchico.edu!olivea!news.hal.COM!decwrl!amd!netcomsv!calcite!vjs From: vjs@calcite.rhyolite.com (Vernon Schryver) Subject: Re: source of TCP/IP (was I hope this wont ignite a major flame ...) Message-ID: <Ctv4Go.83A@calcite.rhyolite.com> Organization: Rhyolite Software Date: Mon, 1 Aug 1994 15:31:36 GMT References: <31fd07$6pq@cesdis1.gsfc.nasa.gov> <31guc7$g6p@starbase.neosoft.com> <31hvpt$8i9@cesdis1.gsfc.nasa.gov> Lines: 28 In article <31hvpt$8i9@cesdis1.gsfc.nasa.gov> becker@cesdis.gsfc.nasa.gov (Donald Becker) writes: > ... >>Why can't they? >> >>If I can run an X application over a link that's got X.25 and PPP sections in >>the middle, why would *anyone* have the slightest difficulty running ANY >>networking application over ATM? > >Extrapolating from a single connection-oriented protocol over point-to-point >links to "ANY networking application" is quite a stretch! What about >connectionless protocols? What about protocols that expect a broadcast >medium? > ... Before saying such things, look at what the IETF, ATM Forum, and ATM switch and interface vendors are actually doing. If those reasons were valid, then my position that ATM is a non-starter for the desktop would not be controversial. All of the ATM vendors and advocates would close up and go home. IP traffic, which is connectionless, must, will be, and is supported. Multicast traffic, the generalization of broadcast traffic, is also supported one way or another. Vernon Schryver vjs@rhyolite.com