Week 3 · Lesson 2

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.

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

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.

Definition — protocol suite. A protocol suite is a group of cooperating protocols organised in layers. Each layer addresses one part of the communication problem; together they deliver the message end to end. The suite used by the Internet is TCP/IP.

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.

Part 2

Layering and the interaction model

The power of the suite comes from a simple rule called the interaction model:

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.

Think of it this way. Layering is “divide and conquer.” A problem too big for one protocol is split into small, independent jobs. Each layer solves one job and trusts the layer below to solve the rest. This is why a web developer never has to think about Ethernet, and a cable installer never has to think about HTTP.
The four TCP/IP layers · select one

Part 3

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 layerOSI equivalentMain job
ApplicationLayers 7, 6, 5 (Application, Presentation, Session)Services to end-user applications: web, email, name resolution, file transfer.
TransportLayer 4 (Transport)Segments data and delivers it to the correct application using port numbers.
InternetLayer 3 (Network)Logical addressing and routing of packets between different networks.
Network AccessLayers 2, 1 (Data Link, Physical)Framing, hardware (MAC) addressing, and putting bits on the medium.
Application HTTP · HTTPS · DNS · DHCP · FTP · SMTP SSH · Telnet · SNMP OSI 7-5 Transport TCP · UDP OSI 4 Internet IPv4 · IPv6 · ICMP · ARP OSI 3 Network Access Ethernet (802.3) · WLAN (802.11) · PPP OSI 2-1 end-user services delivery to the app routing the wire

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.

Part 4

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.

Which layer does it belong to?

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:

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:

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.

Part 5

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.

One web request, step by step

Exam tip. Learn the layer for each protocol by memorising just a few anchors: ports → Transport (TCP/UDP), IP addresses → Internet (IPv4/IPv6), MAC addresses → Network Access (Ethernet). If an exam question says “port number,” it is talking about Layer 4; if it says “MAC address,” it is Layer 2.
Part 6

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.

Swap one layer · select the change

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.

Note. The OSI model defines seven conceptual layers but specifies no actual protocols. The TCP/IP suite is the reverse: it is a working set of protocols that is described using the OSI reference model. Keep the two categories separate — model versus working suite.

Key terms

TermMeaning
Protocol suiteA group of cooperating protocols organised in layers; also called a protocol stack.
Protocol stackAnother name for a protocol suite, reflecting its layered arrangement.
Interaction modelThe rule that each layer uses the services below it and provides services above it.
TCP/IP modelThe four-layer model of the Internet suite: Application, Transport, Internet, Network Access.
Application layerThe layer providing network services to user applications (HTTP, DNS, DHCP, SMTP, and others).
Transport layerThe layer that delivers data to the correct application using ports; contains TCP and UDP.
Internet layerThe layer responsible for logical addressing and routing; contains IPv4, IPv6, ICMP, and ARP.
Network Access layerThe layer handling framing, MAC addressing, and the physical medium (Ethernet, WLAN, PPP).
ModularityThe property that lets one protocol be replaced without changing the others, because layers are independent.

Sources & references

  1. Braden, R. RFC 1122: Requirements for Internet Hosts — Communication Layers (1989), Section 1.1 (layering). rfc-editor.org/rfc/rfc1122.
  2. Socolofsky, T. & Kale, C. RFC 1180: A TCP/IP Tutorial (1991). rfc-editor.org/rfc/rfc1180.
  3. IEEE. IEEE 802.3 (Ethernet) and IEEE 802.11 (Wireless LAN). standards.ieee.org.
  4. IANA. Service Name and Transport Protocol Port Number Registry. iana.org.
  5. Cisco. CCNA (200-301) Exam Topics, Network Fundamentals. cisco.com.
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Braden, R. RFC 1122: Requirements for Internet Hosts — Communication Layers (1989), Section 1.1 (layering). rfc-editor.org/rfc/rfc1122.
  2. Socolofsky, T. & Kale, C. RFC 1180: A TCP/IP Tutorial (1991). rfc-editor.org/rfc/rfc1180.
  3. IEEE. IEEE 802.3 (Ethernet) and IEEE 802.11 (Wireless LAN). standards.ieee.org.
  4. IANA. Service Name and Transport Protocol Port Number Registry. iana.org.
  5. 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.