Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!decvax!ucbvax!PEGASUS.SCRC.SYMBOLICS.COM!sned From: sned@PEGASUS.SCRC.SYMBOLICS.COM.UUCP Newsgroups: mod.protocols.tcp-ip Subject: Was: Protocol Development on SUN 2 and 3 computers. Message-ID: <861218102502.5.SNED@MEADOWLARK.SCRC.Symbolics.COM> Date: Thu, 18-Dec-86 10:25:00 EST Article-I.D.: MEADOWLA.861218102502.5.SNED Posted: Thu Dec 18 10:25:00 1986 Date-Received: Fri, 19-Dec-86 20:53:37 EST References: <8612161801.AA01095@sluggo.sun.com> Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 32 Approved: tcp-ip@sri-nic.arpa From an equally biased source with a different viewpoint.... Date: Tue, 16 Dec 86 10:01:55 PST From: melohn@Sun.COM (Bill Melohn) Speaking as an admittedly biased source, the Sun Datacomm group has managed to implement OSI (MAP/TOP) with a minimum of kernel changes using the basic protosw, ioctl facility, and even the routing table routines from the standard SunOS. We also have implementations of X.25, SNA, and DECnet which all use the ifnet structure to layer different protocol instances on top of different datalinks (HDLC, SDLC, 802.x). As you might expect, the farther your protocol is from the TCP/IP model, the less useful the standard networking code will be. If your goal is XNS under Unix, it makes sense to use the 4.3 implementation. I can't really disagree with that. As a general platform for protocol/network development, we believe SunOS offers most of the facilities you need. If your goal is general protocol/network development or cross-system integration, the Symbolics Lisp Machine's "Generic Network System" is probably 10x more powerful. Use UN*X to develop UN*X software, particularly when there are no deep design issues involved. Use something far better if there are any hard or unresolved issues to be solved. I could easily justify my 10x claim, but this conversation wasn't about that. Steve Sneddon Manager of Networks and Communications Symbolics, Inc.