Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!sun-barr!newstop!east!hinode!geoff
From: geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Info on implementation details...
Message-ID: <718@east.East.Sun.COM>
Date: 17 Aug 89 13:21:32 GMT
References: <21853@louie.udel.EDU>
Sender: news@east.East.Sun.COM
Reply-To: geoff@East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Distribution: usa
Organization: Sun Microsystems, Billerica MA
Lines: 23

In article <21853@louie.udel.EDU> lap@udel.EDU (Larry Pearlstein) writes:
>Can anyone tell me:
>
>At what levels (interrupt, daemon, system driver, application 
>program) are each of the seven network layers generally 
>implemented in a typical TCP/IP system. 

What seven levels? Not even ISO has seven levels. You need to read
Mike Padlipsky's "Elements of Networking Style" to get rid of
any such mystical numerological superstitions before embarking on
a study of real-world implementations. Then go read RFC817: Dave Clark
on "Modularity and efficiency in protocol implementation", and McKusick
on 4.3BSD.  One day John Romkey et al may get around to writing about
the PC/IP experience (John?). Comer's Xinu and TCP/IP books are
invaluable.

The bottom line: there are a LOT of different solutions that have been
tried.

Geoff Arnold,                              Internet: geoff@East.Sun.COM
PCDS Group, Sun Microsystems Inc.
---------------------------------------------------------------------------
My disclaimer is available via anonymous FTP as a compressed tar archive....