This chapter discusses the OSI network model. The topics of this chapter are:
The way a network works can be understood in terms of a model of a network that was created by the International Organization for Standardization, called the ISO for short. (No it isn't an acronym, it is from the Greek word isos, meaning equal.) Their model is called the Open Systems Interconnection (OSI) Reference Model, hence the ISO-OSI model.
Once you understand this model, you will have a general, powerful reference for examining and comparing networks. In the Novell curriculum, we spent nine chapters on this model. I will present an overview here, in keeping with your text. For those who would like to understand the subject better, look over the notes for course CNE 250.
The seven layers of the model are usually written in a list, numbering
the top as layer seven and the bottom as layer one.
Several mnemonic sentences exist to help us remember the proper order. I recommend "Please Do Not Throw Sausage Pizza Away", because this is in the correct numeric order (bottom to top). If you must have one that goes from top to bottom, try "All People Studying This Need Drastic Psychotherapy". Warning: you MUST remember the correct order, the correct numbers, and the correct details for each layer.
The processes that happen in each layer communicate with the next layer. Which way is next, up or down? It depends whether data is being passed out of the stack (down) or into it (up). Typically, a computer generates a request starting at the top layer, and working down. The request is passed across the network (probably to a server) and the received request is passed up the layers. When a response is generated, the process reverses.
The Novell texts for this subject provide another metaphor for the model: think of each layer of the model as being like a shelf in a bookcase. There are seven shelves, and each shelf has several books on it. The books represent the topics that we discuss in our study of that layer. In fact, in each book are discussions of the various methods that relate to that topic. A method is a way of implementing a task the topic covers. For instance, the Physical layer includes the Connection Type topic (a task), and we will see that there are two classic methods for making connections (ways to do it).
Using the metaphor of the bookcase, consider that the ISO might made different choices about which shelf some the books belong on. Some books fit the subject matter of more than one shelf. Other network models exist that place some topics on different layers. This explains why some actual networks do not fit the ISO model as cleanly as they might. There is no definitive rule that says either is right, only that each must follow its own standard.
The chapter continues with an overview of the functions of the seven layers:
As a request is passed down the layers, a header is added to the request at each new layer. The header holds information that is added to the request by processes at that layer. So, by the time the request leaves the computer, it has had six more parts added to it. When the request is received by the server, the receiving layers strip off the information added to the request by their counterpart layers. The request increases in size as it leave the requester, and decreases in size as it is processed by the receiver. This is a simplification to get the idea across to you, but then ,"it's only a model". (Patsy, Monty Python and the Holy Grail.)