Comparison and Contrast

between the OSI and TCP/IP

Model

Introduction
The topics that we will be discussing would be
based on the diagram below.
OSI

TCP / IP

Application (Layer7)
Presentation (Layer6)

Application

Session (Layer 5)
Transport (Layer 4)

Transport

Network (Layer 3)

Internet

Data Link (Layer 2)

Physical (Layer 1)

Subnet or Network Access

Outline
Compare the protocol layers that correspond
to each other.
General Comparison
Focus of Reliability Control
Roles of Host system
De-jure vs. De-facto

The Upper Layers

OSI

TCP / IP

Application (Layer7)

Presentation (Layer6)
Session (Layer 5)

Session
Presentation

Application

Application

The Session Layer

The Session layer permits two parties to hold
ongoing communications called a session
across a network.
Not found in TCP/IP model
In TCP/IP this is handled by the TCP protocol.
(Transport Layer)

The Presentation Layer

The Presentation Layer handles data format
information for networked communications. This is
done by converting data into a generic format that
could be understood by both sides.
Not found in TCP/IP model
In TCP/IP, this function is provided by the Application
Layer.
e.g. External Data Representation Standard (XDR)
Multipurpose Internet Mail Extensions (MIME)

The Application Layer

The Application Layer is the top layer of the reference model. It provides a
set of interfaces for applications to obtain access to networked services as
well as access to the kinds of network services that support applications
directly.
OSI

FTAM
VT
MHS
DS
CMIP

(File transfer, access, and management like TCP/IP FTP and NFS)
(Virtual terminal protocol like TCP/IP telnet)
(Message handling system like TCP/IP SMTP and other email protocols)
(Directory services , later modified for the TCP/IP stack as LDAP )
(Common Management Information Protocol like TCP/IP SNMP)

TCP/IP
FTP
(File Transfer Protocol)
SMTP (Simple Mail Transfer Protocol)
TELNET
DNS
(Domain Name Service)
SNMP (Simple Network Management Protocol)

Although the notion of an application process is common to both, their

approaches to constructing application entities is different.

ISO Approach
Sometime called the Horizontal Approach
OSI asserts that distributed applications operate over a
strict hierarchy of layers and are constructed from a
common tool kit of standardized application service
elements.
In OSI, each distributed application service selects
functions from a large common toolbox of application
service element (ASEs) and complements these with
application service elements that perform functions
specific to given end-user service .

TCP/IP Approach
Sometime called the Vertical Approach
In TCP/IP, each application entity is composed of
whatever set of function it needs beyond end to end
transport to support a distributed communications
service.
Most of these application processes builds on what
it needs and assumes only that an underlying
transport mechanism (datagram or connection) will
be provided.

Transport Layer
OSI

TCP / IP

Transport (Layer 4)

Transport (TCP/UDP)

The functionality of the transport layer is to

provide transparent transfer of data from
a source end open system to a destination
end open system (ISO / IEC 7498: 1984).

Transport Layer
Transport is responsible for creating and
maintaining the basic end-to-end connection
between communicating open systems,
ensuring that the bits delivered to the
receiver are the same as the bits transmitted
by the sender; in the same order and without
modification, loss or duplication

OSI Transport Layer

It takes the information to be sent and breaks it into
individual packets (segments) that are sent and
reassembled into a complete message by the
Transport Layer at the receiving node
Also provide a signaling service for the remote node
so that the sending node is notified when its data is
received successfully by the receiving node

OSI Transport Layer

Transport Layer protocols include the
capability to acknowledge the receipt of a
packet; if no acknowledgement is received,
the Transport Layer protocol can retransmit
the packet or time-out the connection and
signal an error

OSI Transport Layer

Transport protocols can also mark packets with
sequencing information so that the destination system
can properly order the packets if theyre received outof-sequence
In addition, Transport protocols provide facilities for
insuring the integrity of packets and requesting
retransmission should the packet become garbled when
routed.

OSI Transport Layer

Transport protocols provide the capability for
multiple application processes to access the
network by using individual local addresses to
determine the destination process for each data
stream
This is what makes Network Address Translation
(NAT) and Port Address Translation (PAT) possible,
thus allowing a LAN Administrator to assign as many
as 65,536 different private addresses to nodes
within a LAN, while using as few as 1 public address
that is visible to anyone outside the LAN.

TCP/IP Transport Layer

Defines two standard transport protocols: TCP
and UDP
TCP implements a reliable data-stream
protocol
connection oriented

UDP implements an unreliable data-stream

connectionless

TCP/IP Transport Layer

Many programs will use a separate TCP connection
as well as a UDP connection FTP, for example

TCP/IP Transport Layer

TCP is responsible for data recovery
by providing a sequence number with each packet
that it sends

TCP requires ACK (ackowledgement) to ensure

correct data is received
Packet can be retransmitted if error detected

TCP/IP Transport Layer

Use of ACK

TCP/IP Transport Layer

Flow control with Window (sliding windows)
via specifying an acceptable range of sequence numbers

TCP/IP Transport Layer

TCP and UDP introduce the concept of ports
Common ports and the services that run on
them:

FTP
telnet
SMTP
http
POP3

21 and 20
23
25
80
110

TCP/IP Transport Layer

By specifying ports and including port numbers with
TCP/UDP data, multiplexing is achieved
Multiplexing allows multiple network connections to
take place simultaneously
The port numbers, along with the source and
destination addresses for the data, determine a
socket

Comparing Transport for both Models

The features of UDP and TCP defined at TCP/IP
Transport Layer correspond to many of the
requirements of the OSI Transport Layer. There is a
bit of bleed over for requirements in the session
layer of OSI since sequence numbers, and port
values can help to allow the Operating System to
keep track of sessions, but most of the TCP and UDP
functions and specifications map to the OSI
Transport Layer.

Comparing Transport for both Models

The TCP/IP and OSI architecture models both employ all
connection-oriented and connectionless models at
transport layer.
However, the internet architecture refers to the two models
in TCP/IP as simply connections and datagrams.
But the OSI reference model, with its penchant for
precise terminology, uses the terms connection-mode
and connection-oriented for the connection model and the
term connectionless-mode for the connectionless model.

Network vs. Internet

OSI

TCP / IP

Network (Layer 3)

Internet

Like all the other OSI Layers, the network layer

provides both connectionless and connectionoriented services.
(But note, this is for WANs only. With LANs, layer 3 and its
protocol (IP) is strictly a connectionless layer.)

As for the TCP/IP architecture, the internet layer is

exclusively connectionless.

Data link / Physical vs. Subnet

OSI

TCP / IP

Data Link (Layer 2)

Subnet
Physical (Layer 1)

Data link layer

The function of the Data Link Layer is provides for the control of the physical
layer, and detects and possibly corrects errors which may occur (IOS/IEC
7498:1984).
In another words, the Data Link Layer transforms a stream of raw bits (0s and
1s) from the physical into a data frame and provides an error-free transfer
from one node to another, allowing the layers above it to assume virtually
error-free transmission

Data link / Physical vs. Subnet

Physical layer
The function of the Physical Layer is to provide
mechanical, electrical, functional, and procedural
means to activate a physical connection for bit
transmission (ISO/IEC 7498:1984).
Basically, this means that the typical role of the physical
layer is to transform bits in a computer system into
electromagnetic (or equivalent) signals for a particular
transmission medium (wire, fiber, ether, etc.)

Data link / Physical vs. Subnet

Comparing to TCP/IP
These 2 layers of the OSI correspond directly to the
subnet layer of the TCP/IP model
After much deliberation by organizations, it was decided
that the Network Interface Layer in the TCP/IP model
corresponds to a combination of the OSI Data Link
Layer and network specific functions of the OSI network
layer.

De-jure vs. De-facto (OSI)

OSI
Standard legislated by official recognized body. (ISO)
The OSI reference model was devised before the protocols were
invented. This ordering means that the model was not biased
toward one particular set of protocols, which made it quite
general. The down side of this ordering is that the designers did
not have much experience with the subject and did not have a
good idea of which functionality to put in which layer.
Being general, the protocols in the OSI model are better hidden
than in the TCP/IP model and can be replaced relatively easily as
the technology changes.
Not so widespread as compared with TCP/IP. (complex , costly)
More commonly used as teaching aids.

De-jure vs. De-facto (TCP/IP)

TCP/IP
Standards adopted due to widespread use. (Internet)
The protocols came first, and the model was really just a
description of the existing protocols. There was no problem with
the protocols fitting the model, but it is hardly possible to be use
to describe other models.
Get the job done" orientation.
Over the years it has handled most challenges by growing to meet
the needs.
More popular standard for internetworking for several reasons :
relatively simple and robust compared to alternatives such as
OSI
available on virtually every hardware and operating system
platform (often free)
the protocol suite on which the Internet depends.

 More popular standard for internetworking for several

reasons :
relatively simple and robust compared to alternatives
such as OSI
available on virtually every hardware and operating
system platform (often free)
the protocol suite on which the Internet depends.