Week 3 · Lesson 4

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.

CCNA 200-301 Domain 1.0 Network Fundamentals Verified 2026-10-11
Part 1

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.

Definition — reference model. A reference model is a conceptual framework that divides the complex job of network communication into layers, and describes the function of each layer and how it relates to its neighbours. It is a design blueprint, not a piece of software, and it does not by itself say how to implement anything.

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 key distinction. OSI is a reference model; TCP/IP is a protocol suite that also has a reference model. OSI was designed first, as a theoretical standard; TCP/IP grew out of working software and won in practice. Exams test both, and test how they map onto one another.
Part 2

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 layerFunctionExamples
7ApplicationServices and interfaces the user’s software uses to reach the network.HTTP, DNS, SMTP, FTP
6PresentationData format, translation, compression, and encryption.TLS, JPEG, GIF, ASCII
5SessionOpens, manages, and closes conversations between applications.RPC, NetBIOS session
4TransportEnd-to-end delivery: segmentation, reliability, flow control, ports.TCP, UDP
3NetworkLogical addressing and routing between networks.IPv4, IPv6, ICMP
2Data LinkFraming, physical (MAC) addressing, error detection on the local link.Ethernet, Wi-Fi (802.11), PPP
1PhysicalTransmits 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 seven OSI layers · select one

Part 3

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 layerFunctionCovers OSI layers
ApplicationAll user-facing and session/format functions; the protocols an app uses to communicate.7, 6, 5
TransportEnd-to-end delivery, ports, reliability (TCP) or speed (UDP).4
InternetLogical addressing and routing across networks.3
Network AccessFraming, 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

The TCP/IP names group these jobs differently: Application = OSI 7–5, Transport = OSI 4, Internet = OSI 3, Network Access = OSI 2–1.

Part 4

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 layerTCP/IP layerFunctionPDUAddress / identifier
7 ApplicationApplicationNetwork services for applicationsDataNames (URL / FQDN)
6 PresentationFormat, compression, encryption
5 SessionStart, maintain, end conversations
4 TransportTransportEnd-to-end delivery, ports, reliabilitySegment (TCP) / Datagram (UDP)Port numbers
3 NetworkInternetRouting between networksPacketIP addresses
2 Data LinkNetwork AccessFraming and local-link deliveryFrameMAC addresses
1 PhysicalTransmit bits as signalsBits— (none)
Which TCP/IP layer covers this OSI layer? · select one
7 Application 6 Presentation 5 Session 4 Transport 3 Network 2 Data Link 1 Physical Application Transport Internet Network Access PDU: Data Address: names (URL / FQDN) HTTP, DNS, TLS, SMTP, FTP PDU: Segment / Datagram PDU: Packet · IP addresses PDU: Frame · MAC addresses

Exam tip. The three OSI layers that collapse into the TCP/IP Application layer are 7, 6 and 5 — Application, Presentation, Session. At the bottom, OSI 2 and 1 collapse into the single TCP/IP Network Access layer. The middle layers (4 and 3) keep their own names.
Part 5

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).

Four layers or five? · select the model
TCP/IP — 4 layers Cisco variant — 5 layers Application Application Transport Transport Internet Internet Network Access OSI 2 + 1 Data Link Physical

Cisco 5-layer modelEqualsWhat it does
ApplicationTCP/IP ApplicationUser services and application protocols
TransportTCP/IP TransportEnd-to-end delivery and ports
InternetTCP/IP InternetIP addressing and routing
Data Linkbottom half of Network AccessFraming and MAC addressing
Physicalbottom half of Network AccessSignals on the medium
Which model is “official”? The canonical TCP/IP model is four layers. The five-layer form is a teaching variant that Cisco uses to make the physical/data-link split explicit. Learn the four-layer model as the standard, and recognise the five-layer one when you see it.
Part 6

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.

ModelStrengthsLimitations
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

Mnemonics · select one

Key terms

TermMeaning
Reference modelA conceptual, layered blueprint describing the function of each layer of network communication; not an implementation.
OSI modelThe ISO seven-layer Open Systems Interconnection reference model (ISO/IEC 7498-1).
TCP/IP modelThe four-layer model matching the protocol suite the Internet runs on (Application, Transport, Internet, Network Access).
PDUProtocol Data Unit; the name of the data unit at each layer (data, segment/datagram, packet, frame, bits).
Cisco five-layer variantA teaching form of the TCP/IP model that splits Network Access into Data Link and Physical.
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. ISO/IEC. 7498-1:1994 — Information technology — Open Systems Interconnection — Basic Reference Model: The Basic Model. iso.org/standard/20269.
  2. Braden, R. RFC 1122: Requirements for Internet Hosts — Communication Layers, Section 1.1 (layering). rfc-editor.org/rfc/rfc1122.
  3. Socolofsky, T. & Kale, C. RFC 1180: A TCP/IP Tutorial, Sections 2–3. rfc-editor.org/rfc/rfc1180.
  4. Cisco. CCNA (200-301) Exam Topics, Network Fundamentals. cisco.com.
  5. 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.