Networking Models
Networking is too complex to solve in one piece. Engineers split the problem into layers, and once you can name the layers and say what each one does, you have a map for the whole course. This lesson introduces the two models every exam assumes: OSI and TCP/IP.
Why layered models exist
Sending one message across a network involves dozens of separate jobs: formatting the data, finding the destination, getting it across the local link, and finally converting it into signals. Trying to do all of that at once would be unmanageable. A layered model divides the problem into a stack of smaller, independent jobs. Each layer solves one part and offers its service to the layer above.
- Modularity (divide and conquer) — a change in one layer does not force a rewrite of the others. You can swap Wi-Fi for Ethernet at the lower layers without touching the web browser at the top.
- Easier troubleshooting — you can test one layer at a time. Is the cable plugged in (Layer 1)? Is the IP address right (Layer 3)? Is the service running (Layer 7)?
- Vendor standards — agreed layers let different companies build interoperable products. A Windows PC can talk to a Linux server through a Cisco switch because everyone implements the same rules at each layer.
The OSI 7-layer model
The Open Systems Interconnection (OSI) model was defined by the ISO/IEC 7498-1 standard. It is a reference model — a common vocabulary — rather than the model the Internet actually runs on. Learn each layer’s one-line job:
| # | Layer | One-line function |
|---|---|---|
| 7 | Application | Provides the network services and interface that user applications use (HTTP, DNS, SMTP, FTP). |
| 6 | Presentation | Formats and represents data — translation, compression, and encryption/decryption — so both systems understand it. |
| 5 | Session | Establishes, manages, and terminates the dialogs (sessions) between applications. |
| 4 | Transport | Provides end-to-end delivery: segmentation, reliability, flow control, and port addressing (TCP/UDP). |
| 3 | Network | Provides logical addressing (IP) and routing so data can travel between different networks. |
| 2 | Data Link | Provides physical (MAC) addressing, frames the data, and detects errors on the local link. |
| 1 | Physical | Transmits raw bits as signals over the medium — encoding, cabling, and connectors. |
Mnemonics, both directions
The exam can ask about the stack from either end, so memorise both sentences. Notice the two mnemonics are mirror images — if you can go up, you can go down.
Bottom-up (Layer 1 → 7): “Please Do Not Throw Sausage Pizza Away” = Physical, Data Link, Network, Transport, Session, Presentation, Application.
The TCP/IP model
The TCP/IP model is the model the Internet actually uses. It was developed by DARPA and is described in standards such as RFC 1122. It has four layers:
| # | TCP/IP layer | One-line function |
|---|---|---|
| 4 | Application | All the protocols and services used by applications (HTTP, DNS, DHCP, SMTP, SSH). |
| 3 | Transport | End-to-end delivery between processes, using TCP or UDP and port numbers. |
| 2 | Internet | Logical addressing and routing between networks — IP. |
| 1 | Network Access | Physical addressing, framing, and transmission over the medium (Ethernet, Wi-Fi). |
RFC 1122 names the bottom layer the Link layer; Cisco and most textbooks use the name Network Access for the same thing.
Mapping OSI to TCP/IP
The two models describe the same journey with a different number of boxes. OSI’s three upper layers collapse into TCP/IP’s single Application layer, and OSI’s two lower layers collapse into Network Access.
| OSI layer | TCP/IP layer | PDU name |
|---|---|---|
| 7, 6, 5 — Application, Presentation, Session | Application | Data |
| 4 — Transport | Transport | Segment (TCP) / Datagram (UDP) |
| 3 — Network | Internet | Packet |
| 2 — Data Link | Network Access | Frame |
| 1 — Physical | Network Access | Bits |
PDUs and encapsulation
As data descends the stack, each layer wraps it and gives it a new name — its Protocol Data Unit (PDU):
| Layer (OSI) | PDU name | Header added |
|---|---|---|
| Application / upper | Data | Application protocol data |
| Transport (4) | Segment / Datagram | TCP or UDP header |
| Network (3) | Packet | IPv4 / IPv6 header |
| Data Link (2) | Frame | Ethernet header + FCS trailer |
| Physical (1) | Bits | None (encoded as signals) |
Review
Check what you have learned with these review questions.
Sources & references
- ISO/IEC 7498-1:1994. Information technology — Open Systems Interconnection — Basic Reference Model: The Basic Model (the OSI seven-layer model). iso.org/standard/20269.
- Braden, R. RFC 1122: Requirements for Internet Hosts — Communication Layers (1989), Section 1.1.3 (layering). rfc-editor.org/rfc/rfc1122.
- Socolofsky, T. & Kale, C. RFC 1180: A TCP/IP Tutorial (1991), Section 2 (the layered model). rfc-editor.org/rfc/rfc1180.
- Cisco. CCNA (200-301) Exam Topics, Network Fundamentals (network models). cisco.com.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.