Open Systems Interconnection: Internetworking Models
Open Systems Interconnection: Internetworking Models
Open Systems Interconnection: Internetworking Models
Internetworking Models
First a little history: When networks first came into being, computers could typically communicate only
with computers from the same manufacturer. For example, companies ran either a complete DECnet
solution or an IBM solution, never both together. In the late 1970s, the Open Systems
Interconnection (OSI) reference model was created by the International Organization for
Standardization (ISO) to break through this barrier. The OSI model was meant to help vendors create
interoperable network devices and software in the form of protocols so that different vendor networks
could work in peaceable accord with each other.
Advantages of Reference Models
Here’s a list of some of the more important benefits for using the OSI layered model:
uu It divides the network communication process into smaller and simpler components, facilitating
component development, design, and troubleshooting.
uu It allows multiple-vendor development through the standardization of network components.
uu It encourages industry standardization by clearly defining what functions occur at each layer of the
model.
uu It allows various types of network hardware and software to communicate.
uu It prevents changes in one layer from affecting other layers to expedite development.
The OSI Reference Model
The following network devices operate at all seven layers of the OSI model:
uu Network management stations (NMSs)
uu Web and application servers
uu Gateways (not default gateways)
uu Servers
uu Network hosts
The Transport layer can either be connectionless or connection-oriented, but because
Cisco really wants you to understand the connection-oriented function of the Transport layer, I’m going to
go into that in more detail here. Connection-oriented it is also known as call setup or a three-way handshake.
Once this process is complete, the data transfer occurs, and when it’s finished, a call termination takes
place to tear down the virtual circuit.
But what actually happens when a machine receives a flood of datagrams too quickly for
it to process? It stores them in a memory section called a buffer.
Flow Control
Since floods and losing data can both be tragic, we have a fail-safe solution in place known as
flow control. Its job is to ensure data integrity at the Transport layer by allowing applications
to request reliable data transport between systems. Flow control prevents a sending host on
one side of the connection from overflowing the buffers in the receiving host.
Windowing
The quantity of data segments, measured in bytes, that the transmitting machine is allowed to send without
receiving an acknowledgment is called a window.
Acknowledgments
Reliable data delivery ensures the integrity of a stream of data sent from one machine to the other through
a fully functional data link. It guarantees that the data won’t be duplicated or lost. This is achieved through
something called positive acknowledgment with retransmission— a technique that requires a receiving
machine to communicate with the transmitting source by sending an acknowledgment message back to the
sender when it receives data.
The Application layer: of the OSI model marks the spot where users actually communicate to
the computer and comes into play only when it’s clear that access to the network will be
needed soon. Take the case of Internet Explorer (IE). You could actually uninstall every trace of
networking components like TCP/IP, the NIC card, and so on and still use IE to view a local HTML
document.
The Presentation layer: gets its name from its purpose: It presents data to the Application layer and is
responsible for data translation and code formatting.
The Session layer: is responsible for setting up, managing, and dismantling sessions between
Presentation layer entities and keeping user data separate. Dialog control between devices also occurs at
this layer.
The Transport layer: segments and reassembles data into a single data stream. Services located at this
layer take all the various data received from upper-layer applications, then combine it into the same,
concise data stream. These protocols provide end-to-end data transport services and can establish a logical
connection between the sending host and destination host on an internetwork.
The Network layer or layer 3: manages device addressing, tracks the location of devices on the network,
and determines the best way to move data.
The Data Link layer: provides for the physical transmission of data and handles error notification,
network topology, and flow control. This means that the Data Link layer will ensure that messages are
delivered to the proper device on a LAN using hardware addresses and will translate messages from the
Network layer into bits for the Physical layer to transmit.
Physical layer: does two things: it sends bits and receives bits. The Physical layer specifies the electrical,
mechanical, procedural, and functional requirements for activating, maintaining, and deactivating a
physical link between end systems.