Network Models & Standards — OSI and

TCP/IP
Advanced Reading Notes
Sources:
UTSA Pressbooks — Networking: Part II, The Layers of the OSI Model
Medium (HackTrace) — Day 2: Network Models Explained: OSI vs TCP/IP and the Protocols That
Power the Internet

1. Why Network Models Exist

In the early days of computer networking (1960s), machines from different vendors (IBM, early
Apple/Microsoft-era systems, etc.) each used proprietary communication schemes and could not
talk to one another — comparable to different companies speaking mutually unintelligible
languages.
ARPANET (1969), built by the U.S. Department of Defense, was the first real computer network —
groundbreaking, but it exposed how chaotic and incompatible vendor systems were.
This incompatibility drove the tech community to build standardized frameworks for
communication — giving rise to the OSI Model and the TCP/IP Model, essentially "translators"
that let any two systems interoperate regardless of maker.
Big picture takeaway: network models are architectural blueprints. They break the complex,
messy task of "getting data from Device A to Device B" into clean, layered, manageable stages —
each layer handling one job and passing results to the next.
2. The Two Models at a Glance
OSI Model TCP/IP Model

Transmission Control Protocol / Internet

Full name Open Systems Interconnection
Protocol

Number of 4 (classic) — sometimes taught as 5

7
layers when Physical and Data Link are split

Practical, real-world implementation

Nature Theoretical / conceptual reference model model — what the actual internet runs
on

Standardize and describe how

Get data actually moving across real
Purpose communication should work, for teaching &
networks
troubleshooting

Status Not directly implemented as-is in devices, "Won" in practice — it's the model the
today but still the shared vocabulary engineers use modern internet is built on

Key mental model:

OSI = conceptual understanding (the theory / the map) TCP/IP = real-world implementation (the
terrain / what's actually running)
Even though TCP/IP is what's deployed, engineers still talk in OSI terms day-to-day ("that's a Layer
3 routing problem," "we need a Layer 7 firewall") because OSI's granularity makes it easier to
pinpoint where in the communication process a problem lives.

3. The OSI Model — 7 Layers (bottom-up)

The OSI model is best understood bottom-up (Physical → Application) because that mirrors the
literal order data actually flows through as it leaves a device, or top-down (Application → Physical)
to mirror the user's experience. Below is bottom-up, illustrated with the classic example of sending
an email with an attachment.
# Layer Core Job Worked Example (sending an email)

Converts data into raw electrical signals, Your outgoing email is turned into
1 Physical light pulses, or radio waves for electrical signals or radio waves the
transmission over cables/air instant you hit "send"

Handles node-to-node delivery on the Email packets get tagged with MAC
2 Data Link local network; adds physical (MAC) addresses so switches/bridges can
addresses; managed by switches/bridges route them within your local network

Routers use IP addresses to forward

Handles routing across different networks
your email packets across the globe,
3 Network using logical (IP) addressing; the job of
crossing network/geographic
routers
boundaries

Breaks data into manageable

Your email message is divided into
segments/packets; ensures reliable,
4 Transport smaller packets for efficient
efficient end-to-end delivery (this is where
transmission
TCP lives)

Opens, manages, and closes the Keeps the email exchange coherent and
5 Session "conversation" (session) between two orderly so packets arrive as a cohesive
devices; dialogue control conversation

Translates, encrypts/decrypts, and Applies encryption/compression so the

6 Presentation compresses/decompresses data so it's email's content stays secure and is
usable by the Application layer understood correctly by both ends

Your email client uses protocols like

Closest layer to the end user; where user-
7 Application SMTP and IMAP to actually initiate and
facing protocols and software operate
manage the send

Layers 5–7 (Session, Presentation, Application) are often grouped together conceptually since
they're all about preparing/handling data for the end user, versus Layers 1–4 which are about
actually getting bits from point A to point B.

4. The TCP/IP Model — 4 Layers

TCP/IP condenses OSI's 7 layers into 4 (sometimes taught with 5, splitting Physical/Data Link):
 TCP/IP Layer Roughly Maps to OSI Layer(s)

Application Application, Presentation, Session (5, 6, 7)

Transport Transport (4)

Internet Network (3)

Network Access (Link) Data Link, Physical (1, 2)

Nicknamed the "TCP/IP Stack" because data literally "stacks up" — gaining headers/wrappers —
as it passes down through the layers on the sending side, and gets unwrapped in reverse on the
receiving side.
TCP/IP is the model actually deployed across the real internet — routers, switches, OS network
stacks, etc. are built around it, not the full 7-layer OSI spec.

5. Protocols by Layer (Reference Table)

Common protocols engineers associate with each layer/function — useful for the practice exercises
below and for real troubleshooting:

Function / Layer Example Protocols

Application (user-facing
HTTP/HTTPS, SMTP, IMAP, POP3, FTP, DNS, DHCP
services)

Transport (end-to-end delivery) TCP, UDP

Network/Internet (routing) IP (IPv4/IPv6), ICMP

Data Link / Network Access

Ethernet, Wi-Fi (802.11), ARP
(local delivery)

Cabling standards, radio signaling — not really a "protocol" layer

Physical
so much as the physical medium

6. Real-World Troubleshooting Shorthand

Engineers frequently diagnose problems by OSI layer number even when working in a pure TCP/IP
environment, because it narrows down where to look:
Layer 1 (Physical): e.g., a cable is unplugged, no signal
Layer 3 (Network): e.g., wrong/misconfigured IP address
Layer 7 (Application): e.g., a misconfigured web service or app-level bug
This is the practical payoff of learning OSI even though the "real" internet runs on TCP/IP: it gives
you a shared, precise vocabulary for isolating faults.
7. Study / Practice Activities
A. Layer Identification Pick 5 devices/applications (e.g., router, switch, browser, Wi-Fi adapter, FTP
server) and identify:
Which OSI layer each one primarily operates at
Which protocol(s) it typically uses
B. Protocol Mapping Match each protocol to its correct TCP/IP layer: HTTP , DNS , IP , Ethernet ,
TCP , DHCP
C. Packet Capture Exercise Open Wireshark, visit a website, and:
Observe the captured packets
Identify which layer (OSI and/or TCP/IP) each protocol you see belongs to
Goal: see that every packet represents a journey through both models, from Application down to
Physical and back up on the receiving end

8. Key Takeaways / Exam-Ready Summary

OSI = 7 layers, conceptual/reference model. TCP/IP = 4 layers, actually implemented model.
Data traveling out moves top-down (Application → Physical, gaining headers at each layer —
"encapsulation"); data arriving moves bottom-up (Physical → Application, stripping headers —
"decapsulation").
OSI's extra granularity (splitting Session/Presentation/Application) makes it better for teaching
and precise troubleshooting language, even though it isn't literally how software is built.
TCP/IP's leaner structure reflects how the internet is actually engineered — the model predates
and shaped real-world protocol design.
Both models coexist in professional vocabulary: you'll hear "Layer 2 switch," "Layer 3 routing,"
"Layer 4 load balancer," "Layer 7 firewall/proxy" constantly in real networking, cloud, and security
work — all OSI terms describing tools/concepts that run on top of the TCP/IP internet.

9. Encapsulation & Decapsulation (How Data Actually Moves

Through the Layers)
This is the mechanical process underlying everything above — worth knowing cold.
Encapsulation (sending side, top → bottom): Each layer takes what it receives from the layer
above and wraps it with its own header (and sometimes a trailer), then hands it down to the next
layer. Nothing is stripped away — data just keeps getting wrapped, like nesting envelopes inside
envelopes.
Decapsulation (receiving side, bottom → top): The reverse happens — each layer strips off its
corresponding header/trailer, reads what it needs, and passes the remainder up to the next layer,
until only the original application data is left.
Protocol Data Unit (PDU) — the name for "data" changes at each layer
OSI Layer PDU Name

7 – Application Data

6 – Presentation Data

5 – Session Data

4 – Transport Segment (TCP) / Datagram (UDP)

3 – Network Packet

2 – Data Link Frame

1 – Physical Bits

A handy mnemonic: "Do Sergeants Pay for Beer?" → Data, Segment, Packet, Frame, Bits
(Transport→Physical, top to bottom).

10. Addressing at Each Layer

Different layers use different types of "address" to get data where it's going:

Layer Address Type Example

Data Link MAC address (physical/hardware address, burned

00:1A:2B:3C:4D:5E
(2) into the NIC)

Network (3) Logical/IP address (assigned, routable) [Link] or 2001:db8::1

Transport Port number (identifies the specific 80 (HTTP), 443 (HTTPS), 25

(4) application/process) (SMTP)

This is why a full "conversation" over the internet is often summarized as: MAC gets you across
the local network, IP gets you across the internet, and the Port gets you to the right
application once you arrive.
11. Devices Mapped to OSI Layers
Layer Typical Device(s)

1 – Physical Hubs, repeaters, cables, NICs (physical transmission only)

2 – Data Link Switches, bridges, wireless access points

3 – Network Routers, Layer 3 switches

4 – Transport Load balancers (Layer 4), firewalls (stateful, port-based)

7 – Application Application-layer/next-gen firewalls, proxies, gateways

This is the practical root of expressions like "Layer 2 switch" or "Layer 7 firewall" — the device is
named for the highest layer at which it makes forwarding/filtering decisions.

12. The Standards Bodies Behind These Models

ISO (International Organization for Standardization) — published the OSI Reference Model
(formalized in the early-to-mid 1980s) as a vendor-neutral standard so any manufacturer's
equipment could theoretically interoperate.
IETF (Internet Engineering Task Force) — governs the actual protocols that make up the TCP/IP
suite today (HTTP, TCP, IP, DNS, etc.) via RFC (Request for Comments) documents. This is why
TCP/IP is described as the "practical"/implemented model — it grew organically out of working
protocols rather than being designed top-down like OSI.
IEEE (Institute of Electrical and Electronics Engineers) — standardizes much of the Physical and
Data Link layer technology in practice, e.g., 802.3 (Ethernet) and 802.11 (Wi-Fi).
Historical note: TCP/IP actually predates the finalized OSI model (TCP/IP's core design dates to
the 1970s–early 1980s out of DARPA-funded research; OSI was formalized by ISO around 1984).
OSI was meant to become the universal standard, but by the time it was finished, TCP/IP was
already widely deployed and "won" adoption — which is why today OSI mainly survives as a
teaching/reference tool rather than a deployed stack.

13. The "Hybrid" / 5-Layer TCP/IP Model

Some textbooks (including many intro networking courses) teach a 5-layer version of TCP/IP
instead of the classic 4-layer version, by splitting "Network Access" into two separate layers so it
lines up more directly with OSI:
 5-Layer TCP/IP Corresponding OSI Layer(s)

Application 5, 6, 7 (Session, Presentation, Application)

Transport 4

Network (Internet) 3

Data Link 2

Physical 1

This is the version referenced in the UTSA course material's framing of "TCP/IP model (five layers)
and OSI model (seven layers)" — it's a middle ground that keeps TCP/IP's practical simplicity for
layers 5–7 while still separating Physical and Data Link for clarity.

14. Connection-Oriented vs. Connectionless Transport (Layer

4 Deep Dive)
Since Transport is where a lot of real troubleshooting and protocol decisions happen, it's worth
contrasting the two core Transport-layer protocols:

TCP UDP

Full name Transmission Control Protocol User Datagram Protocol

Connection-oriented (handshake
Connectionless (no handshake, just
Connection type required — the "3-way handshake": SYN,
send)
SYN-ACK, ACK)

Reliable — guarantees delivery, ordering, Unreliable — "fire and forget," no

Reliability
retransmits lost segments delivery guarantee

Speed/overhead Slower, more overhead Faster, minimal overhead

Web browsing (HTTP/HTTPS), email Streaming, VoIP, DNS lookups, online

Typical uses (SMTP/IMAP), file transfer (FTP) — gaming — anywhere speed matters
anywhere data integrity matters more than a guarantee
15. Quick Comparison Cheat-Sheet (Everything in One Place)
Question OSI Answer TCP/IP Answer

How many
7 4 (or 5 in hybrid teaching versions)
layers?

Designed by Evolved from DARPA/ARPANET research,

ISO
whom? standardized via IETF RFCs

Purpose Reference/teaching model Actual working model of the internet

Is it deployed
No Yes
as-is?

Explaining concepts and precisely Building and running real

Best for...
diagnosing where a problem lives networks/protocols

Famous
"Layer 3 problem," "Layer 7 firewall" "The TCP/IP stack"
shorthand

Notes compiled from: UTSA Pressbooks Networking textbook (Part II), HackTrace's "Day 2"
Medium article on OSI vs TCP/IP, and standard networking-fundamentals reference
knowledge (PDUs, addressing, standards bodies, TCP vs UDP) for additional depth beyond the
two source articles.