home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.dcom.isdn:1119 comp.protocols.ppp:1058
- Path: sparky!uunet!gatech!destroyer!news.itd.umich.edu!dabo.citi.umich.edu!rees
- From: rees@dabo.citi.umich.edu (Jim Rees)
- Newsgroups: comp.dcom.isdn,comp.protocols.ppp
- Subject: Re: dp2.2 on Interactive V3.2 & ISDN
- Date: 9 Jan 1993 14:44:35 GMT
- Organization: University of Michigan CITI
- Lines: 26
- Distribution: world
- Message-ID: <5d76ad8d.cb12@dabo.citi.umich.edu>
- References: <5d7385d3.1bc5b@pisa.citi.umich.edu> <C0KL1M.LuI@world.std.com>
- Reply-To: Jim.Rees@umich.edu
- NNTP-Posting-Host: dabo.citi.umich.edu
-
- In article <C0KL1M.LuI@world.std.com>, ariel@world.std.com (Robert L Ullmann) writes:
-
- Ah, the standard myth. The problem was that a lot of X.25 implementations
- (the *OLD* Sunlink comes to mind) were really awful; they were usually
- "designed" to run at maybe 9.6K and do badly even at that.
-
- I wasn't speaking of the implementation. I was speaking of the protocol.
- There is a basic mismatch between the tcp/ip architecture and the
- x.25 architecture. x.25 was invented before the concept of layered
- protocols became fashionable, and it contains transport, network, and
- data link layers all in one big rat's nest. It does all sorts of things
- like flow control that you don't necessarily want sitting under a proper
- transport protocol like tcp.
-
- X.25 can blow the doors off of PPP when it comes to real interoperation
- and effective reliability.
-
- I won't argue with that; however...
-
- If all you want is a freebie hack that might work
- most of the time, by all means use PPP.
-
- There are good commercial implementations of ppp out there, Morningstar for
- example (and given the unnecessary complexity of ppp, these people have my
- respect). And as you yourself pointed out, there are poor commercial
- implementations of x.25.
-