Protocol Suites
One protocol does one job. A real conversation — opening a web page, sending an email — needs many protocols cooperating at once. That cooperating set is a protocol suite, and the one that runs the Internet is TCP/IP. This lesson shows how the suite is organised into layers and which protocol lives where.
What is a protocol suite?
A protocol suite is a set of interrelated protocols that work together to carry a message from an application on one host to the same application on another host. It is also called a protocol stack, because the protocols are arranged in layers that stack on top of one another. Each protocol in the suite handles one specific part of the job.
Because a single message needs many jobs done at once — address the right application, reach the right host across the world, cross the right local link, and become signals on the wire — no single protocol can do it all. Each job belongs to a different layer, and each layer has its own protocol(s).
One job each
No single protocol can address, route, transport and signal at once.
Stacked in layers
Each layer solves one problem and hands the result to the layer above.
Interoperable
Any vendor implementing the same layer will work with everyone else.
Layering and the interaction model
The power of the suite comes from a simple rule called the interaction model:
- Each layer uses the services of the layer below it.
- Each layer provides services to the layer above it.
The boundary between two layers is a defined interface, so a layer never needs to know how the layer below does its job — only what it promises to do. The Application layer asks the Transport layer to deliver data; the Transport layer asks the Internet layer to move it across networks; the Internet layer asks the Network Access layer to put it on the medium. On the receiving side the same hand-offs happen in reverse, going up.
TCP/IP versus OSI
The TCP/IP model has four layers. The OSI model has seven. TCP/IP schedules the same set of functions into fewer, broader layers, as the mapping below shows (Lesson 04 compares the two models in depth).
| TCP/IP layer | OSI equivalent | Main job |
|---|---|---|
| Application | Layers 7, 6, 5 (Application, Presentation, Session) | Services to end-user applications: web, email, name resolution, file transfer. |
| Transport | Layer 4 (Transport) | Segments data and delivers it to the correct application using port numbers. |
| Internet | Layer 3 (Network) | Logical addressing and routing of packets between different networks. |
| Network Access | Layers 2, 1 (Data Link, Physical) | Framing, hardware (MAC) addressing, and putting bits on the medium. |
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.
The protocols at each layer
Now name the protocols that live in each of the four layers. Pick a layer you think a protocol belongs to, then reveal each card to test yourself.
Application layer protocols
The Application layer is closest to the user. It provides the network services that applications call — turning a web address into an IP address, moving a file, sending mail. Its protocols include HTTP and HTTPS, DNS, DHCP, FTP, SMTP, Telnet and SSH, and SNMP. Lesson 03 explains what each of these does.
Transport layer protocols
The Transport layer moves data between applications. Its two protocols are:
- TCP (Transmission Control Protocol) — connection-oriented and reliable; it tracks delivery and retransmits what is lost.
- UDP (User Datagram Protocol) — connectionless and lightweight; it sends datagrams with no delivery guarantee in exchange for speed and low overhead.
Both use port numbers to identify which application should receive the data.
Internet layer protocols
The Internet layer moves packets between networks and is where logical addressing lives:
- IPv4 and IPv6 — the addressing and best-effort delivery protocols.
- ICMP — reports errors and provides testing (used by
pingandtraceroute). ICMPv6 does the same for IPv6. - ARP — resolves an IPv4 address to a MAC address on the local link.
Network access layer protocols
The Network Access layer (called Data Link and Physical in OSI) describes how data is framed and placed on the medium. Its protocols include Ethernet (IEEE 802.3) for wired LANs, WLAN (IEEE 802.11) for wireless, and PPP for point-to-point WAN links. This is also where MAC addresses and the physical media live.
Request/response and the header process
Most communication follows a request/response pattern. A client sends a request; a server returns a response. When you open a web page, your browser sends an HTTP request and the web server returns the page. When your computer needs a name resolved, it sends a DNS request and a DNS server returns the address.
As the request travels down the suite, each layer adds its own header — this is encapsulation (Lesson 01). The Transport header carries the port number, the Internet header carries the IP addresses, and the Network Access header carries the MAC addresses. At the server the process reverses: each layer strips its header and hands the data upward until the application receives the request. The response then travels back the same way.
Modularity: why suites survive change
Because layers are independent, the suite is modular: you can add or replace one protocol without redesigning the rest, as long as it keeps the same interface to its neighbours. Real examples prove the point.
- IPv6 was introduced alongside IPv4 at the Internet layer — the layers above did not have to be rebuilt.
- Wi-Fi (802.11) replaced Ethernet at the Network Access layer on mobile devices, while HTTP and TCP kept working unchanged.
- HTTPS was placed on top of the same Transport layer as HTTP, so secure web traffic required no change beneath it.
This modularity is why the TCP/IP suite has lasted for decades and absorbed new technologies. It is also why open, published standards matter (Lesson 01): any vendor can implement one layer at a time and still interoperate with everyone else.
Key terms
| Term | Meaning |
|---|---|
| Protocol suite | A group of cooperating protocols organised in layers; also called a protocol stack. |
| Protocol stack | Another name for a protocol suite, reflecting its layered arrangement. |
| Interaction model | The rule that each layer uses the services below it and provides services above it. |
| TCP/IP model | The four-layer model of the Internet suite: Application, Transport, Internet, Network Access. |
| Application layer | The layer providing network services to user applications (HTTP, DNS, DHCP, SMTP, and others). |
| Transport layer | The layer that delivers data to the correct application using ports; contains TCP and UDP. |
| Internet layer | The layer responsible for logical addressing and routing; contains IPv4, IPv6, ICMP, and ARP. |
| Network Access layer | The layer handling framing, MAC addressing, and the physical medium (Ethernet, WLAN, PPP). |
| Modularity | The property that lets one protocol be replaced without changing the others, because layers are independent. |
Sources & references
- Braden, R. RFC 1122: Requirements for Internet Hosts — Communication Layers (1989), Section 1.1 (layering). rfc-editor.org/rfc/rfc1122.
- Socolofsky, T. & Kale, C. RFC 1180: A TCP/IP Tutorial (1991). rfc-editor.org/rfc/rfc1180.
- IEEE. IEEE 802.3 (Ethernet) and IEEE 802.11 (Wireless LAN). standards.ieee.org.
- IANA. Service Name and Transport Protocol Port Number Registry. iana.org.
- Cisco. CCNA (200-301) Exam Topics, Network Fundamentals. cisco.com.
Review
Check what you have learned with these review questions.
Sources & references
- Braden, R. RFC 1122: Requirements for Internet Hosts — Communication Layers (1989), Section 1.1 (layering). rfc-editor.org/rfc/rfc1122.
- Socolofsky, T. & Kale, C. RFC 1180: A TCP/IP Tutorial (1991). rfc-editor.org/rfc/rfc1180.
- IEEE. IEEE 802.3 (Ethernet) and IEEE 802.11 (Wireless LAN). standards.ieee.org.
- IANA. Service Name and Transport Protocol Port Number Registry. iana.org.
- Cisco. CCNA (200-301) Exam Topics, Network Fundamentals. cisco.com.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.