OSI Model: Data Units, Encapsulation, and Layer Protocols
Question 1: Segments, Packets, and Frames in the OSI Stack
Although the terms Segment, Packet, and Frame are sometimes used loosely to mean "a chunk of data,"
each one is tied to a specific layer of the OSI model and refers to the data unit only after that layer has
attached its own control information. The technical distinction is the header (and in one case, header plus
trailer) that gets wrapped around the payload at that stage.
Data Unit Layer it belongs to What makes it distinct
Segment Transport (Layer 4) Raw application data gets a transport header attached, carrying
source/destination port numbers plus sequencing and
flow-control information (TCP) or a lightweight delivery header
(UDP).
Packet Network (Layer 3) The segment is wrapped with a network-layer header that adds
the source and destination IP addresses, enabling the data to
be routed across different networks.
Frame Data Link (Layer 2) The packet is wrapped with both a header (containing
source/destination MAC addresses) and a trailer (containing an
error-checking value, typically a CRC), preparing it for delivery
across a single local link.
How a message is transformed on its way down (encapsulation)
Picture a user typing the message "Hello Bob" and hitting send. As the message descends through the
sender's OSI stack, every layer treats the data handed to it from the layer above as a black box and simply
tacks on its own control information before passing it further down:
Application, Presentation, Session (L7-L5): The text is packaged into an application message, and along
the way it may be formatted, compressed, and character-encoded (for example into UTF-8), while a session
is kept open to track the ongoing exchange.
Transport (L4): A transport header is attached containing the sender's and receiver's port numbers, plus
sequencing/reliability details if TCP is used. At this point the data unit is officially called a Segment.
Network (L3): A network header is attached containing the sender's and receiver's IP addresses. The data
unit is now called a Packet.
Data Link (L2): A frame header (with source/destination MAC addresses) and a frame trailer (with a CRC
value for error checking) are attached. The data unit is now called a Frame.
Physical (L1): The frame is converted into raw bits and transmitted as electrical signals, light pulses, or
radio waves over the physical medium.
How the message is rebuilt on the way up (decapsulation)
At the receiving host, the exact same process runs in reverse. Each layer strips off the header (or header
and trailer) that its counterpart layer on the sender's side added, reads the control information it needs, and
passes the remaining payload upward:
Physical: Reconstructs raw bits from the incoming electrical, optical, or radio signal.
Data Link: Checks the trailer's CRC for transmission errors, removes the frame header/trailer, and hands
the packet upward.
Network: Reads and removes the IP header, confirming the packet reached the right destination address,
then passes up the segment.
Transport: Reads and removes the transport header, using port numbers to hand the data to the correct
application, reassembling data in order if needed.
Session, Presentation, Application: The session is managed/closed, the data is decrypted or
decompressed and decoded back to readable text, and the application layer finally displays the original
message: "Hello Bob".
In short: a Segment, Packet, and Frame are really the same underlying message at three different stages of
encapsulation, each distinguished by the specific header/trailer information added at that OSI layer.
Decapsulation at the receiver removes these wrappers in the exact opposite order in which they were
added, which is what allows the original message to be reconstructed correctly.
Question 2: Major Protocols Across the Seven OSI Layers
The table below summarizes the main protocols associated with each OSI layer, along with the addressing
scheme (or port numbers) used at that layer and a short description of the layer's core job.
Layer Key Protocols Addressing / Ports Core Function & Role
7. HTTP, HTTPS, FTP, Well-known ports: HTTP Sits closest to the end user and
Application SMTP, POP3, IMAP, 80, HTTPS 443, FTP provides the actual network
DNS, DHCP, SSH 20/21, SMTP 25/587, services an application relies on —
POP3 110, IMAP 143, web browsing, email delivery and
SSH 22, DNS 53, DHCP retrieval, file transfer, remote login,
67/68 and translating domain names into
IP addresses.
6. Presentat TLS/SSL, JPEG, PNG, Uses the port already Acts as the translator of the stack:
ion MPEG, GIF, ASCII, opened by the application encrypts/decrypts data,
UTF-8 layer above it (no ports of compresses or decompresses it,
its own) and converts between
character-encoding or file formats
so the two ends can understand
each other.
5. Session NetBIOS, RPC, SIP, NetBIOS 137-139; SIP Opens, coordinates, and cleanly
PPTP 5060/5061 closes the ongoing conversation
between two devices, keeping
track of which exchange belongs to
which session so data streams
don't get mixed up.
4. TCP, UDP, SCTP Port numbers (0-65535) Breaks data into segments,
Transport identify the sending and ensures end-to-end delivery, and
receiving manages reliability, ordering, and
process/application flow control. TCP guarantees
ordered, acknowledged delivery;
UDP trades reliability for speed
with no connection setup.
3. Network IPv4, IPv6, ICMP, OSPF, Logical addressing via IP Handles logical addressing and
RIP, BGP addresses; BGP 179, RIP path selection, deciding how a
520 packet gets routed from its source
network to a different destination
network.
2. Data Link Ethernet, Wi-Fi (802.11), Physical/hardware Organizes bits into frames for
ARP, PPP, VLAN addressing via MAC delivery across a single local link,
tagging addresses resolves IP-to-MAC mapping
(ARP), and performs error
detection using a CRC trailer.
1. Physical Ethernet physical No logical addressing — Converts frames into a raw
standards, Fiber Optics, concerned only with the bitstream and transmits it as
Bluetooth, Wi-Fi PHY physical transmission electrical signals, light pulses, or
medium radio waves over cable or wireless
media.
Note on addressing: only the Network layer (IP addresses) and Data Link layer (MAC addresses) use true
logical/physical addressing schemes. The Transport layer instead uses port numbers to identify which
application a segment belongs to, while the Application, Presentation, and Session layers largely reuse the
addressing already established below them and are better characterized by their function than by a distinct
address format of their own.