KEMBAR78
11.) Lecture 4 TCPIP Overview | PDF | Internet Protocol Suite | Computer Network
0% found this document useful (0 votes)
28 views19 pages

11.) Lecture 4 TCPIP Overview

The document outlines the TCP/IP model, which is a four-layered suite of communication protocols developed by the Department of Defense. It compares the TCP/IP model with the OSI model, highlighting the functions of each layer, including the Process/Application, Host-to-Host, Internet, and Network Access layers. The document also discusses the historical context of TCP/IP's development and its significance in the evolution of the Internet.

Uploaded by

czaetvwp
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
28 views19 pages

11.) Lecture 4 TCPIP Overview

The document outlines the TCP/IP model, which is a four-layered suite of communication protocols developed by the Department of Defense. It compares the TCP/IP model with the OSI model, highlighting the functions of each layer, including the Process/Application, Host-to-Host, Internet, and Network Access layers. The document also discusses the historical context of TCP/IP's development and its significance in the evolution of the Internet.

Uploaded by

czaetvwp
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 19

Network Models: TCP/IP Model

School of Computer Science Engineering and Technology


Bennett University
Greater Noida – 201310
OSI Versus DoD Model

Outline
TCP/IP Model
OSI and DoD Model

The DoD model is a condensed version of the OSI


model—it's composed of four, instead of seven,
layers.

❖ A vast array of protocols combine at the DoD


model's Process/Application layer to integrate the
various activities and duties spanning the focus of
the OSI's corresponding top three layers
(Application, Presentation, and Session). The
Process/Application layer defines protocols for
node-to-node application communication and
also controls user-interface specifications.
OSI and DoD Model II

❖ The Host-to-Host layer parallels the functions of the


OSI's Transport layer, defining protocols for setting
up the level of transmission service for applications.
It tackles issues such as creating reliable end-to-end
communication and ensuring the error-free delivery
of data. It handles packet sequencing and maintains
data integrity.
❖ The Internet layer corresponds to the OSI's Network
layer, designating the protocols relating to the
logical transmission of packets over the entire
network. It takes care of the addressing of hosts by
giving them an Internet Protocol (IP) address, and it
handles the routing of packets among multiple
networks.
OSI and DoD Model III

❖ At the bottom of the DoD model, the Network


Access layer implements the data exchange
between the host and the network. The equivalent
of the Data Link and Physical layers of the OSI
model, the Network Access layer oversees hardware
addressing and defines protocols for the physical
transmission of data.
OSI Model: Protocol and Specification Layout
DoD Model: Protocol and Specification Layout
TCP/IP Network Model

❖ The DoD and OSI models are alike in design and


concept and have similar functions in similar layers.
Figure shows the TCP/IP protocol suite and how its
protocols relate to the DoD model layers.

❖ TCP/IP Reference Model is a four-layered suite of


communication protocols. It was developed by the
DoD (Department of Defense) in the 1970s-80s. It is
named after the two main protocols that are used in
the model, namely, TCP and IP. TCP stands for
Transmission Control Protocol and IP stands for
Internet Protocol.
TCP/IP Protocol Stack
TCP/IP
❖ The name TCP/IP refers to a suite of data communication protocols. The name is misleading because TCP and
IP are only two of dozens of protocols that compose the suite. Its name comes from two of the more
important protocols in the suite: the Transmission Control Protocol (TCP) and the Internet Protocol (IP).
❖ TCP/IP originated out of the investigative research into networking protocols that the Department of
Defense (DoD) initiated in 1969. In 1968, the DoD Advanced Research Projects Agency (ARPA) began
researching the network technology that is now called packet switching.
❖ The original focus of this research was to facilitate communication among the DoD community. However, the
network that was initially constructed as a result of this research, then called ARPANET, gradually became
known as the Internet. The TCP/IP protocols played an important role in the development of the Internet. In
the early 1980s, the TCP/IP protocols were developed. In 1983, they became standard protocols for
ARPANET.
❖ Because of the history and resemblance of the TCP/IP protocol suite, it is often referred to as the DoD
protocol suite or the Internet protocol suite.
Physical + Data Link Layer
❖ The design of TCP/IP hides the function of this layer from users--it is
concerned with getting data across a specific type of physical network
(such as Ethernet, Token Ring, etc.).
❖ This design reduces the need to rewrite higher levels of a TCP/IP stack
when new physical network technologies are introduced (such as ATM
and Frame Relay).
❖ The functions performed at this level include encapsulating the IP
datagrams into frames that are transmitted by the network. It also maps
the IP addresses to the physical addresses used by the network.
❖ IP address must be converted into whatever address is appropriate for
the physical network over which the datagram is transmitted.
❖ Data to be transmitted is received from the internetwork layer. The
network access layer is responsible for routing and must add its routing
information to the data. The network access layer information is added in
the form of a header, which is appended to the beginning of the data.
Network Layer
❖ This layer is responsible for routing messages through internetworks. Two
types of devices are responsible for routing messages between networks.
The first device is called a gateway, which is a computer that has two
network adapter cards.
❖ Gateway accepts network packets from one network on one network card
and routes those packets to a different network via the second network
adapter card. The second device is a router, which is a dedicated hardware
device that passes packets from one network to a different network. These
two terms are often used interchangeably, but distinct differences exist in
their ability to route packets.
❖ The internetwork layer protocols provide a datagram network service.
Datagrams are packets of information that comprise a header, data, and a
trailer. The header contains information, such as the destination address,
that the network needs to route the datagram. A header can also contain
other information, such as the source address and security labels. Trailers
typically contain a checksum value.
Network Layer II
❖ The communicating entities--which can be computers, operating systems,
programs, processes, or people--that use the datagram services must
specify the destination address (using control information) and the data for
each message to be transmitted. The network layer protocols package the
message in a datagram and send it off.

❖ A datagram service does not support any concept of a session or


connection. Once a message is sent or received, the service retains no
memory of the entity with which it was communicating. If such a memory is
needed, the protocols in the host-to-host transport layer maintain it. The
abilities to retransmit data and check it for errors are minimal or
nonexistent in the datagram services. If the receiving datagram service
detects a transmission error during transmission using the checksum value
of the datagram, it simply ignores (or drops) the datagram without notifying
the receiving higher-layer entity.
❖ It is responsible for providing end-to-end data
integrity and provides a highly reliable
communication service for entities that want to
carry out an extended two-way conversation.
❖In addition to the usual transmit and receive
functions, the transport layer uses open and
Transport/ close commands to initiate and terminate the
connection. This layer accepts information to be
Host-to-Host transmitted as a stream of characters, and it
returns information to the recipient as a stream.
Layer ❖The service employs the concept of a connection
(or virtual circuit). A connection is the state of the
host-to-host transport layer between the time
that an open command is accepted by the
receiving computer and the time that the close
command is issued by either computer.
Application Layer
❖ This layer provides functions for users or their programs, and it is highly
specific to the application being performed. It provides the services that
user applications use to communicate over the network, and it is the layer
in which user-access network processes reside.
❖ These processes include all of those that users interact with directly, as well
as other processes of which the users are not aware.
❖ This layer includes all applications protocols that use the host-to-host
transport protocols to deliver data. Other functions that process user data,
such as data encryption and decryption and compression and
decompression, can also reside at the application layer.
❖ The application layer also manages the sessions (connections) between
cooperating applications. In the TCP/IP protocol hierarchy, sessions are not
identifiable as a separate layer, and these functions are performed by the
host-to-host transport layer. Instead of using the term "session," TCP/IP
uses the terms "socket" and "port" to describe the path (or virtual circuit)
over which cooperating applications communicate.
TCP/IP
Reference
Example
(Layers)
❖ Difference between TCP/IP and OSI reference
Further Models.
❖ ARPANET Packet Switching Network and

Study DoD Model


❖ Pros and Cons of TCP/IP
❖ What is NetBEUI or IPX/SPX ?
(For Students)
❖ https://datatracker.ietf.org/doc/html/rfc1180

References ❖ https://datatracker.ietf.org/doc/html/rfc793
❖ https://datatracker.ietf.org/doc/html/rfc791

https://www.cisco.com/c/en/us/support/docs/i
p/routing-information-protocol-rip/13769-
5.html
❖ https://www.cisco.com/E-
Learning/bulk/public/tac/cim/cib/using_cisco
_ios_software/linked/tcpip.htm

https://www.juniper.net/documentation/en_U
S/junose15.1/topics/concept/ip-
overview.html

https://www.juniper.net/documentation/us/en/
software/junos/flow-packet-
processing/topics/topic-map/security-tcp-
session-checks.html

You might also like