Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!linus!alliant!steckel
From: steckel@alliant.UUCP
Newsgroups: comp.dcom.lans,comp.protocols.misc,comp.sources.wanted
Subject: Re: OSI-model software
Message-ID: <526@alliant.UUCP>
Date: Thu, 4-Jun-87 23:09:07 EDT
Article-I.D.: alliant.526
Posted: Thu Jun  4 23:09:07 1987
Date-Received: Sat, 6-Jun-87 07:17:38 EDT
References: <223@diab.UUCP> <233@idacrd.UUCP>
Reply-To: steckel@alliant.UUCP (Geoff Steckel)
Distribution: world
Organization: Omnivore Technology, Newton, MA
Lines: 16
Keywords: OSI layered protocols
Xref: utgpu comp.dcom.lans:446 comp.protocols.misc:21 comp.sources.wanted:1116
Summary: Read Padlipsky and weep

Anyone contemplating using OSI protocols should read Padlipsky's comments
in the tcp-ip mailgroup (comp.dcom.tcp-ip I think).  He exposes far better
than I can the fundamental flaws in network protocols prescribed by PTTs
(national postal/telegraph/telephone monopolies) or other monolithic entities.
He has also published a book on the subject - suitable for making implementors
cry and standards committee members break out in flames.  (Sorry, I can't
remember the title but I could find out if enough interest)

OSI doesn't tell you how to make a network.  It only tells you how to
(supposedly) connect to a (supposedly perfect) network.  All OSI protocols
fall extremely short on error handling.  Even X.25, the closest to usable
of all the OSI protocols, has had several revisions because of this problem
and it's a low level!

Read Padlipsky and weep (or break into hysterical laughter!).
	geoff steckel (steckel@alliant.uucp, gwes@wjh12.uucp)