The OSI Reference Model

Chapter 2 — The OSI Reference Model | Network+ Study Map
CompTIA Network+ ~ Domain 1.0

Chapter 2 — The OSI Reference Model

Seven layers, one job each. The OSI model is the shared blueprint that lets a Windows laptop, a Linux server, and a phone on the other side of the planet actually understand each other. This is the study map for the seven layers, how the Transport layer keeps data honest, how routers and switches split up the work, and how a single user message gets wrapped — and unwrapped — on its way across the wire.

17 sections Layer-by-layer explorer TCP handshake animator Encapsulation stack builder Written lab + exam-check quiz
01

Internetworking Models

Early networks could only talk to machines from the same manufacturer — a complete DECnet shop, or a complete IBM shop, never both at once. In the late 1970s the International Organization for Standardization (ISO) created the Open Systems Interconnection (OSI) reference model to break that barrier and let different vendors' equipment interoperate.

A reference model is a conceptual blueprint for how communication should happen. It breaks the job into logical groupings called layers — a layered architecture. Communication processes that relate to each other are grouped, or bound, at a particular layer, so a developer working on one layer's protocol never has to worry about what's happening at any other layer.

Exam angleThe OSI model isn't a physical thing — it's a conceptual, fluid set of guidelines that application developers and hardware vendors design against.
02

Advantages of Reference Models

These benefits apply to any layered model — OSI, or the TCP/IP model that grew out of the Department of Defense.

03

The Seven Layers

The top three layers (Application, Presentation, Session) govern how applications talk to each other and to end users. The bottom four (Transport, Network, Data Link, Physical) govern how the actual data gets transmitted end to end. None of the upper layers knows anything about networks or addresses — that's entirely the bottom four's job.

MnemonicPlease Do Not Throw Sausage Pizza Away — Physical, Data Link, Network, Transport, Session, Presentation, Application, from layer 1 up to layer 7.
LayerNamePrimary Function
7ApplicationFile, print, message, database, and application services
6PresentationData encryption, compression, and translation services
5SessionDialog control
4TransportEnd-to-end connection
3NetworkRouting
2Data LinkFraming
1PhysicalPhysical topology
04

Layer Explorer

Click through each layer for what the exam actually expects you to know about it.

05

Application, Presentation & Session

The upper three layers, flipped for the detail worth memorizing.

Exam angleApplications don't reside at the Application layer — they interface with it. Microsoft Word doesn't live at layer 7; it calls on layer 7 protocols like SFTP or TFTP only when it needs the network.
06

Transport Layer — Connection-Oriented Communication

Before a sending host's TCP process transmits a single segment, it contacts the destination's TCP process to build a virtual circuit. This is connection-oriented communication — the TCP three-way handshake.

SYN → SYN/ACK → ACK. Click to watch the handshake complete.

A service is connection-oriented if it...

Sets up a virtual circuit ~ uses sequencing ~ uses acknowledgments ~ uses flow control

TCP vs. UDP

Set up a virtual circuit → you're using TCP (connection-oriented). Skip that setup → you're using UDP (connectionless).

07

Flow Control & Windowing

Flow control lets the receiver govern how much data the sender pushes at once, so a fast sender can't overflow a slow receiver's buffer. The number of unacknowledged bytes a sender is allowed to have in flight is the window size. Drag the slider to see how window size changes how many segments go out before an acknowledgment is required.

Window size: 3 segments before ACK
Exam angleA window of 1 means the sender waits for an ACK after every single segment — slow, but safe. If a receiver keeps missing segments it should acknowledge, it can improve the session by decreasing the window size.
08

Acknowledgments & Reliable Delivery

TCP uses positive acknowledgment with retransmission: the receiver acknowledges what it gets, the sender starts a timer on everything it sends, and anything that doesn't get acknowledged before the timer expires gets sent again.

09

Network Layer

The Network layer handles logical addressing, tracks where devices live on the network, and figures out the best way to move data between them — including hosts that aren't locally attached. Routers are the layer 3 devices that do this work.

What's in a routing table

FieldWhat it holds
Network AddressProtocol-specific destination network, tracked per routing protocol (IP, IPv6, etc.)
InterfaceThe exit interface a packet takes to reach that network
MetricDistance to the remote network — hop count for RIP; bandwidth, delay, or tick count for others

Data Packets

Carry user data through the internetwork. The protocols that support them are routed protocols — IP and IPv6.

Route-Update Packets

Update neighboring routers about connected networks. Sent by routing protocols — RIP, RIPv2, EIGRP, OSPF.

Rule to memorizeRouters break up broadcast domains. Switches break up collision domains. A router can also be called a layer 3 switch — the terms are interchangeable.
10

Data Link Layer

The Data Link layer delivers messages to the right device on a local network using hardware (MAC) addresses, and translates Network layer messages into bits the Physical layer can transmit. It formats data into frames, adding a header with source and destination hardware addresses. It's the only OSI layer with sublayers.

11

Project 802

The IEEE 802 subcommittees, formed in February 1980 (80 + 2 = "802"), standardized LAN and MAN technologies. Only a handful of these are still active — the rest have been disbanded or gone into hibernation.

Exam angle802.3 = Ethernet. 802.11 = wireless. Those two, plus 802.1 and 802.15, are the only Active standards — memorize those two pairings cold.
12

Physical Layer

The bottom of the stack does two things: sends bits, and receives bits. It defines the electrical, mechanical, procedural, and functional requirements for activating and deactivating a physical link, and it's where the interface between DTE (data terminal equipment — the attached device) and DCE (data communication equipment — usually a modem or CSU/DSU) is defined.

DTE

Data terminal equipment. The device attached to the network — your computer.

DCE

Data communication (or circuit-terminating) equipment. Usually a modem or CSU/DSU, typically at the customer premises.

The Physical layer also defines the transmission media's layout — its topology: bus, star, ring, or mesh.

13

Encapsulation

As data travels down the stack from a transmitting host, each layer wraps it with its own control information — a protocol data unit (PDU) — usually in a header, sometimes a trailer. Step through the process below.

Start with raw user information at the Application layer.
Exam angleOrder matters: Data → Segments → Packets (or datagrams) → Frames → Bits. That's Application/Presentation/Session, Transport, Network, Data Link, Physical.
14

Modulation Techniques

Modulation varies a carrier signal's properties to encode information onto it — the step that turns bits into something that can actually be transmitted on the wire, fiber, or airwave.

15

Exam Essentials

Know the layers cold

Application/Presentation/Session handle user-to-application communication. Transport segments, sequences, and builds virtual circuits. Network handles logical addressing and routing. Data Link frames and places data on the medium. Physical encodes bits for transmission.

Know the Data Link sublayers

LLC multiplexes and identifies Network layer protocols. MAC handles physical addressing and decides when to place data on the network.

16

Written Lab

Fill in the OSI layers in order, from layer 7 down to layer 1.

17

Exam Check

Twenty review questions pulled straight from this chapter.

Score: 0 / 0
NETWORK+ STUDY MAP ~ CHAPTER 2 ~ DOMAIN 1.0 — THE OSI REFERENCE MODEL