OSI MODEL

Tech Academy – Day Tree

– Jose Quiros

Non-Juniper
TRANSPORT LAYER
(LAYER 4)

Non-Juniper
 TRANSPORT LAYER (LAYER 4)

01 02 03 04
Tracking the individual Segmenting data and Reassembling the Identifying the
communication managing each piece segments into streams different applications
between applications of application data
on the source and
destination hosts

Non-Juniper
 Segmenting Data

Each piece of application

The Transport layer data requires headers to be
protocols describe services added at the Transport
that segment this data layer to indicate to which
from the Application layer. communication it is
associated.

Non-Juniper
 Reassembling Segments

• Individual pieces of data must also be reconstructed into a

complete data stream that is useful to the Application layer.

Non-Juniper
 Identifying the Applications

Transport layer assigns an This port number is used

application an identifier. in the transport layer
The TCP/IP protocols call header to indicate to
this identifier a port which application that
number. piece of data is associated.

Non-Juniper
Non-Juniper
Non-Juniper
 • Segmentation and Reassembly
• Conversation Multiplexing
• Connection-oriented conversations
Controlling the • Reliable delivery
Conversations • Ordered data reconstruction
• Flow control

Non-Juniper
 Controlling the Conversations

Establishing Reliable Same Order Flow

a Session Delivery Delivery Control

Non-Juniper
 TCP and UDP

The two most common Transport layer protocols of TCP/IP protocol suite
are Transmission Control Protocol (TCP) and User Datagram Protocol (UDP).

Both protocols manage the communication of multiple applications.

The differences between the two are the specific functions that each
protocol implements.

Non-Juniper
 • UDP is a simple, connectionless
protocol.
• It has the advantage of providing for
low overhead data delivery.
• The pieces of communication in UDP
User Datagram are called datagrams.
Protocol (UDP) • These datagrams are sent as "best
effort" by this Transport layer protocol.
• Applications that use UDP include:
Domain Name System (DNS), Video
Streaming, Voice over IP (VoIP)

Non-Juniper
 • TCP is a connection-oriented protocol.
• TCP incurs additional overhead to gain
functions.
• Order delivery, reliable delivery, and
flow control.
Transmission • Each TCP segment has 20 bytes of
Control overhead in the header encapsulating
the Application layer data.
Protocol (TCP) • Each UDP segment only has 8 bytes of
overhead.
• Applications that use TCP are: Web
Browsers, E-mail, File Transfers

Non-Juniper
UDP | TCP HEADERS

Non-Juniper
 • Port numbers identify
Port Addressing applications at Layer 4.

Non-Juniper
Port addressing

Non-Juniper
 • Well Known Ports (Numbers 0 to 1023)
There are • Registered Ports (Numbers 1024 to
different types 49151)
• Dynamic or Private Ports (Numbers
of port 49152 to 65535)
numbers:

Non-Juniper
 Using both TCP and UDP

• Some applications may use both TCP and UDP. For example, the
low overhead of UDP enables DNS to serve many client requests
very quickly.
• When communication is for replication between servers, the
well-known port number of 53 is used by both protocols with
this service.

Non-Juniper
TCP and UDP Handle Segmentation
Differently.

Non-Juniper
 The key distinction between TCP and
UDP is reliability.

The TCP Protocol -

Communicating
with Reliability

Non-Juniper
TCP Server
Processes

Non-Juniper
TCP Connection
Establishment
and
Termination

Non-Juniper
TCP Connection
Establishment
and
Termination

Non-Juniper
TCP Connection
Establishment
and
Termination

Non-Juniper
TCP Connection
Establishment
and
Termination

Non-Juniper
TCP Connection
Establishment
and
Termination

Non-Juniper
TCP Connection
Establishment
and
Termination

Non-Juniper
TCP Connection
Establishment
and
Termination

Non-Juniper
TCP Three-Way
Handshake

Non-Juniper
TCP Three-Way
Handshake

Non-Juniper
TCP Three-Way
Handshake

Non-Juniper
 TCP Session Termination

• 1. When the client has no more data to send in the stream, it sends a
segment with the FIN flag set.
• 2. The server sends an ACK to acknowledge the receipt of the FIN to
terminate the session from client to server.
• 3. The server sends a FIN to the client, to terminate the server to
client session.
• 4. The client responds with an ACK to acknowledge the FIN from the
server.

Non-Juniper
Resequencing Segments to Order
Transmitted

Non-Juniper
 • Confirming Receipt of Segments

TCP
Acknowledgement
with Windowing

Non-Juniper
Handling Segment Loss

Non-Juniper
 TCP Congestion Control - Minimizing
Segment Loss

• Flow Control

Non-Juniper
Reducing Window Size

Non-Juniper
 UDP - Low Overhead vs. Reliability

key Application layer protocols that

The UDP Protocol use UDP include:
- Communicating • Domain Name System (DNS)
with Low • Simple Network Management Protocol
(SNMP)
Overhead • Dynamic Host Configuration Protocol
(DHCP)
• Routing Information Protocol (RIP)
• Trivial File Transfer Protocol (TFTP)
• Online games

Non-Juniper
UDP Datagram
Reassembly

Non-Juniper
UDP Server Processes and Requests

Non-Juniper
UDP Client
Processes

Non-Juniper
UDP Client
Processes

Non-Juniper
Session Layer
(Layer 5)

Non-Juniper
 Session Layer
• The session layer controls the conversations
between different computers.
• A session or connection between machines is set up,
managed, and ended at layer 5. Session layer
services also include authentication and
reconnections.

Non-Juniper
As the name of the Session layer implies, functions
at this layer create and maintain dialogs between
source and destination applications. The Session
layer handles the exchange of information to
initiate dialogs, keep them active, and to restart
sessions that are disrupted or idle for a long period
of time.

Non-Juniper
Presentation Layer
(Layer 6)

Non-Juniper
 Presentation Layer

The presentation layer Because of this, it at times

formats or translates data also called the syntax layer.
for the application layer This layer can also handle
based on the syntax or the encryption and
semantics that the decryption required by the
application accepts. application layer.

Non-Juniper
Application Layer
(Layer 7)

Non-Juniper
 Application Layer

The application layer

At this layer, both the end This layer sees network identifies communication
user and the application services provided to end- partners, resource
layer interact directly with user applications such as a availability, and
the software application. web browser or Office 365. synchronizes
communication.

Non-Juniper
 • Domain Name Service Protocol (DNS) is
used to resolve Internet names to IP
addresses.
• Hypertext Transfer Protocol (HTTP) is
used to transfer files that make up the
Web pages of the World Wide Web.
Common • Simple Mail Transfer Protocol (SMTP) is
used for the transfer of mail messages
Application and attachments.
• Telnet, a terminal emulation protocol,
layer protocols is used to provide remote access to
servers and networking devices.
• File Transfer Protocol (FTP) is used for
interactive file transfer between
systems.

Non-Juniper
Application Layer - Making
Provisions for Applications
and Services
The Client/Server model

Non-Juniper