Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!decvax!ucbvax!SUN.COM!melohn From: melohn@SUN.COM.UUCP Newsgroups: mod.protocols.tcp-ip Subject: Re: Protocol Development on SUN 2 and 3 computers. Message-ID: <8612161801.AA01095@sluggo.sun.com> Date: Tue, 16-Dec-86 13:01:55 EST Article-I.D.: sluggo.8612161801.AA01095 Posted: Tue Dec 16 13:01:55 1986 Date-Received: Wed, 17-Dec-86 23:29:14 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 13 Approved: tcp-ip@sri-nic.arpa 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. As a general platform for protocol/network development, we believe SunOS offers most of the facilities you need.