Reference Models
Two models describe how network communication is organised: the seven-layer ISO OSI model and the four-layer TCP/IP model. Neither is a product. They are reference models — shared blueprints that let engineers, vendors, and examiners talk about the same thing. This lesson puts them side by side.
Why reference models exist
A network is built from equipment made by many different companies. A laptop from one vendor must talk to a switch from a second, a router from a third, and a server from a fourth. Without a shared agreement about what each part of the system is responsible for, none of those devices could cooperate.
Layering is the “divide and conquer” strategy. Instead of one enormous problem, you get small, independent problems with clean boundaries. That gives four practical benefits:
Interoperability
Any vendor can build a product that does one layer’s job and trust that it will fit with everyone else’s products.
Modularity
A layer can be changed or replaced without rewriting the others — swap copper for fibre and nothing above Layer 1 notices.
Easier troubleshooting
A fault can be isolated to one layer and fixed there.
A shared vocabulary
“That’s a Layer 3 problem” communicates instantly.
The ISO OSI model
The Open Systems Interconnection (OSI) model was published by the International Organization for Standardization (ISO) as ISO/IEC 7498-1. It has seven layers, numbered from the bottom (Layer 1, the wire) to the top (Layer 7, the application). Each layer provides a service to the layer above and uses the service of the layer below.
| # | OSI layer | Function | Examples |
|---|---|---|---|
| 7 | Application | Services and interfaces the user’s software uses to reach the network. | HTTP, DNS, SMTP, FTP |
| 6 | Presentation | Data format, translation, compression, and encryption. | TLS, JPEG, GIF, ASCII |
| 5 | Session | Opens, manages, and closes conversations between applications. | RPC, NetBIOS session |
| 4 | Transport | End-to-end delivery: segmentation, reliability, flow control, ports. | TCP, UDP |
| 3 | Network | Logical addressing and routing between networks. | IPv4, IPv6, ICMP |
| 2 | Data Link | Framing, physical (MAC) addressing, error detection on the local link. | Ethernet, Wi-Fi (802.11), PPP |
| 1 | Physical | Transmits raw bits as signals over the medium. | Copper, fibre, radio |
Week 1 treated each layer in turn: Lesson 11 (Application), 12 (Presentation), 13 (Session), 14 (Transport), 15 (Network), 16 (Data Link), and 17 (Physical).
The TCP/IP model
The TCP/IP model (sometimes called the DoD model, after the US Department of Defense, which funded its development) has four layers. It was built from the protocols that actually run the Internet, so it is far more pragmatic than OSI: it collapses everything an application needs into one layer and everything the local hardware does into another.
| TCP/IP layer | Function | Covers OSI layers |
|---|---|---|
| Application | All user-facing and session/format functions; the protocols an app uses to communicate. | 7, 6, 5 |
| Transport | End-to-end delivery, ports, reliability (TCP) or speed (UDP). | 4 |
| Internet | Logical addressing and routing across networks. | 3 |
| Network Access | Framing, MAC addressing, and physical transmission on the local link. | 2, 1 |
Notice what is missing: there are no separate Session or Presentation layers. In TCP/IP those duties belong to the application protocols themselves (for example, TLS handles encryption, and an application protocol manages its own session state). That is a deliberate simplification, not an omission.
Layer responsibilities in brief
- Application (OSI 7) — the doorway between the user’s program and the network; the protocols it speaks. Week 1, Lesson 11.
- Presentation (6) — makes data presentable: character encoding, compression, encryption. Lesson 12.
- Session (5) — sets up, coordinates, and tears down dialogues between applications. Lesson 13.
- Transport (4) — chops data into segments, numbers them, can retransmit and control flow; adds port numbers. Lesson 14.
- Network (3) — adds IP addresses and chooses the path between networks (routing). Lesson 15.
- Data Link (2) — frames the packet, adds MAC addresses, and detects errors on one link. Lesson 16.
- Physical (1) — encodes and transmits bits as electrical, optical, or radio signals. Lesson 17.
The TCP/IP names group these jobs differently: Application = OSI 7–5, Transport = OSI 4, Internet = OSI 3, Network Access = OSI 2–1.
Side by side: function, PDU, address
This is the heart of the lesson. Learn it row by row: for any layer you should be able to name its function, its PDU, and its addressing. The PDU names are the same in both models, whatever the layer is called.
| OSI layer | TCP/IP layer | Function | PDU | Address / identifier |
|---|---|---|---|---|
| 7 Application | Application | Network services for applications | Data | Names (URL / FQDN) |
| 6 Presentation | Format, compression, encryption | |||
| 5 Session | Start, maintain, end conversations | |||
| 4 Transport | Transport | End-to-end delivery, ports, reliability | Segment (TCP) / Datagram (UDP) | Port numbers |
| 3 Network | Internet | Routing between networks | Packet | IP addresses |
| 2 Data Link | Network Access | Framing and local-link delivery | Frame | MAC addresses |
| 1 Physical | Transmit bits as signals | Bits | — (none) |
The Cisco five-layer variant
Cisco teaching materials often present a five-layer version of the TCP/IP model. It is the same four-layer model with the bottom layer split in two, because in practice the physical medium and the data-link framing are genuinely different jobs (and mapping them one-to-one to OSI Layers 2 and 1 makes the correspondence obvious).
| Cisco 5-layer model | Equals | What it does |
|---|---|---|
| Application | TCP/IP Application | User services and application protocols |
| Transport | TCP/IP Transport | End-to-end delivery and ports |
| Internet | TCP/IP Internet | IP addressing and routing |
| Data Link | bottom half of Network Access | Framing and MAC addressing |
| Physical | bottom half of Network Access | Signals on the medium |
Strengths, limitations, and the mnemonics
Both models describe the same process. OSI is vendor-neutral and is the common reference language for teaching and troubleshooting; TCP/IP is the suite that was actually implemented and that the Internet runs on.
| Model | Strengths | Limitations |
|---|---|---|
| OSI (7 layers) | Clear, vendor-neutral standard; separates Session and Presentation; excellent as a universal teaching and troubleshooting reference. | Purely theoretical — the protocols never won the market; some layers (Session, Presentation) are thinly populated; slower to standardise. |
| TCP/IP (4 layers) | Matches the software that actually runs the Internet; proven, pragmatic, simple; the basis of every real device. | No dedicated Session/Presentation layers; the Network Access layer lumps two very different jobs together. |
In practice engineers use both: OSI for vocabulary and troubleshooting depth, TCP/IP for the protocols actually in the stack.
The three mnemonics
Key terms
| Term | Meaning |
|---|---|
| Reference model | A conceptual, layered blueprint describing the function of each layer of network communication; not an implementation. |
| OSI model | The ISO seven-layer Open Systems Interconnection reference model (ISO/IEC 7498-1). |
| TCP/IP model | The four-layer model matching the protocol suite the Internet runs on (Application, Transport, Internet, Network Access). |
| PDU | Protocol Data Unit; the name of the data unit at each layer (data, segment/datagram, packet, frame, bits). |
| Cisco five-layer variant | A teaching form of the TCP/IP model that splits Network Access into Data Link and Physical. |
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. iso.org/standard/20269.
- Braden, R. RFC 1122: Requirements for Internet Hosts — Communication Layers, Section 1.1 (layering). rfc-editor.org/rfc/rfc1122.
- Socolofsky, T. & Kale, C. RFC 1180: A TCP/IP Tutorial, Sections 2–3. rfc-editor.org/rfc/rfc1180.
- Cisco. CCNA (200-301) Exam Topics, Network Fundamentals. cisco.com.
- Tanenbaum, A. S. & Wetherall, D. Computer Networks, the OSI and TCP/IP model chapters.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.