Return-Path: <gooseman@on.on-luebeck.de>
Received: (from mail@localhost)
	by hugin.oden.se (8.8.5/8.8.5) id GAA04651
	for <dlanor@oden.se>; Tue, 25 Feb 1997 06:42:59 +0100
Received: from on.on-luebeck.de(194.25.93.130) by hugin.oden.se via smap (V1.3)
	id sma004646; Tue Feb 25 06:42:52 1997
Received: (from majordomo@localhost)
	by on.on-luebeck.de (8.8.5/8.8.5) id GAA17383
	for stik-outgoing; Tue, 25 Feb 1997 06:42:36 +0100
Date: Mon, 24 Feb 1997 23:38:31 -0600 (CST)
From: -Magic Marmot Studios- <marmot@magic-marmot.com>
X-Sender: marmot@riptide.wavetech.net
To: stik@ON-Luebeck.de
Subject: STIK: Detail on ISO/OSI model
Message-ID: <Pine.GSO.3.93.970224232916.9500A-100000@riptide.wavetech.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: stik@ON-Luebeck.de
Precedence: bulk
Reply-To: stik@ON-Luebeck.de
X-UIDL: 91b8243d2045a28daeb1be8433cf555f



Here is the more detailed information that I promised earlier. 

Just as a note, this is not the only network model, but it is a very good
general model to work from for complex networking functions. It is my
recommendation that further STiK/network development follow this model.

Hey, it's just a suggestion. Take it for what it's worth.  :)

-Rob-

--------------------------------------------------------------------------
   ISO/OSI NETWORK MODEL
--------------------------------------------------------------------------

APPLICATION LAYER

     The application layer contains all the details related to specific 
     applications that use the network.

     This layer is appropriate for the applications that the user has
     direct 
     interaction with (i.e. CAB, a Mail Reader, Telnet application, etc.).


PRESENTATION LAYER

     The presentation layer contains all of the network services that are 
     commonly available to all network applications.

     This layer is appropriate for OS services such as printer drivers and 
     screen drivers, as well as FTP, SMTP, POP, Telnet routines, etc. 
     (different than the user interface, which would be an application).
     Note 
     that a Berkeley Sockets type of interface (API) fits well here.

     This level also deals with data encryption/decryption, and data 
     compression.


SESSION LAYER

     The session layer controls the access of the network by the
     applications; 
     for instance if a mail reader and a web browser are running
     concurrently 
     on the same machine, the session layer controls who has access to
     which 
     application gets access when. It also handles authentication, and 
     communication between applications on the same node.

     This layer should be thought of as the "traffic manager" for
     application 
     data. It primarily exists to handle multitasking or "multibinding" 
     network sessions.


TRANSPORT LAYER

     The transport layer deals with "packetizing" the data from the 
     applications (actually from the session layer) into the transport 
     protocol, and converting the received packets into messages for the 
     applications.

     In many systems, the session and transport layers can be combined for 
     efficiency, especially where only one network task is allowed at a
     time.

     This layer is appropriate for TCP or UDP packetization.

     It is also the last stage that the information "chunks" are the size
     that 
     the application has sent or will be receiving.

NETWORK LAYER

     The network layer determines the route or path that the data follows
     to 
     reach its destination. As such, it must handle congestion, transfer 
     rates, packet sizes, and final network protocols. It would also
     contain 
     routing tables, if any are present.

     This layer is appropriate for IP, Ethernet protocol, ICMP, IGMP,
     MIDInet 
     protocol; also for SLIP/PPP/CSLIP (these are under IP).

     Depending on the network service, some sort of authorization may be 
     required to connect (password, etc.).


DATA-LINK LAYER

     The data-link layer serves to hide the details of the physical 
     transmission from the network layer; essentially, this layer contains 
     only the hardware drivers for the physical layer.

     This layer contains only the dumb drivers for every physical device
     that 
     is network-connectable: serial, LAN, MIDI, Paralell,
     cartridge-ethernet, 
     or what have you.


PHYSICAL LAYER

     This layer is the actual physical hardware (midi port/cables, serial 
     port/modem, etc.).

-----------------------------------------------
______________________________________________________________________________
 Magic Marmot Studios              - Audio Production and Postproduction -
 3632 Lyndale Ave. So.                    The Home of Audio Cinema 
 Minneapolis, MN 55409-1104                    (612) 823-2141

.
