Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!ames!oliveb!pyramid!sas From: sas@pyramid.UUCP (Scott Schoenthal) Newsgroups: comp.dcom.lans,comp.protocols.misc Subject: Re: OSI-model software Message-ID: <3002@pyramid.UUCP> Date: Thu, 11-Jun-87 13:07:51 EDT Article-I.D.: pyramid.3002 Posted: Thu Jun 11 13:07:51 1987 Date-Received: Sat, 20-Jun-87 11:45:23 EDT References: <223@diab.UUCP> <233@idacrd.UUCP> <526@alliant.UUCP> <19265@ucbvax.BERKELEY.EDU> <492@houxa.UUCP> <1204@botter.cs.vu.nl> Reply-To: sas@pyramid.UUCP (Scott Schoenthal) Distribution: world Organization: Pyramid Technology Corp., Mountain View, CA Lines: 32 Xref: mnetor comp.dcom.lans:538 comp.protocols.misc:69 In article <1204@botter.cs.vu.nl> ast@cs.vu.nl (Andy Tanenbaum) writes: >There has been a lot of generalized disgust with OSI expressed here and >elsewhere. I would be very interested in hearing specific comments about > 1. What is wrong with the OSI model itself. > 2. What is wrong with the specific protocols ISO has adopted. > > [ ... ] > >Nevertheless, there are certainly plenty of valid criticisms of the model and >the protocols (e.g., the session layer is pointless, the presentation layer >is practically empty, they forgot about encryption altogether etc.). I would >like to see a discussion of this subject, preferably by people who know what >they are talking about. > >Andy Tanenbaum (ast@cs.vu.nl) I believe that Andy knows what he is talking about and I would certainly be interested if he would expand on the criticisms he mentions in his posting. While I did refer in an earlier posting to the political aspects of adoption of an international standard (the phrase '"bomb-crazed" American military' was an impetuous addition which I now regret), I believe that we should consider here (or hopefully in a comp.protocols.iso) mainly the technical issues of the ISO/OSI model and protocol definition and implementation. Hopefully, this could include MAP/TOP specific protocols (e.g., Directory Services, Network Management) and relevant CCITT protocols (e.g., X.400) as well. sas ---- Scott Schoenthal Pyramid Technology Corp. pyramid!sas Mountain View, California