Week 3 · Lesson 1

Protocols

Your laptop, a Cisco switch, a Linux web server, and a phone on the other side of the planet all talk to each other even though no single company built them. They can, because they all obey the same rules. Those rules are protocols — and this lesson explains exactly what they are.

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

What is a protocol?

A protocol is a set of rules that governs how two or more devices exchange information. The rules are not optional suggestions — every device must follow exactly the same ones, or the messages are meaningless. A protocol answers questions like: How is the data turned into signals? What does the message look like? Who is allowed to send, and when? How long do I wait for a reply?

Definition — protocol. A protocol is an agreed set of rules that determines the format, the order, and the actions taken when data is exchanged between devices. A group of cooperating protocols is called a protocol suite — see Lesson 02.

Two things can be true at once: the hardware may be made by completely different vendors, and the operating systems may be completely different, yet communication still works. That is only possible because both sides implement the same protocol. The rules, not the hardware, are what make the conversation possible.

Format

What the message looks like: which fields, in which order, with which values.

Order

Who talks, in what sequence, and what happens when a step is missed.

Actions

What a device does on receipt: decode, check, forward, acknowledge, retry.

The three rules · select one to highlight it
Sender source host Protocol = agreed rules 1. Message encoding 2. Formatting & encapsulation 3. Message timing Receiver destination host message message sent using the rules decoded with the same rules

Part 2

Rule 1: Message encoding

Computers store information as bits — ones and zeros. Before those bits can travel across a network they must be changed into a form the medium can carry. That conversion is encoding: converting information into another acceptable form for transmission. The receiving device performs the reverse, decoding, to turn the signals back into information.

MediumHow bits are encoded
Copper cableAs patterns of electrical impulses (voltage).
Fibre-optic cableAs pulses of light on a glass strand.
Wireless (radio)As radio waves transmitted through the air.

A simple familiar example is text. A letter such as A is encoded as a number by a character set (for example ASCII or UTF-8), and that number becomes a specific pattern of bits. Both sides must agree on the character set, just as two people must agree which language they are using. The same idea scales up: images, voice, and video each have their own encoding schemes, and the sender and receiver must share the same one.

Encoding · pick the medium

Exam tip. Remember the direction: encoding = information → signals; decoding = signals → information. Encoding happens when a message leaves a host; decoding happens when it arrives at the next host. Both ends must use the same scheme.
Part 3

Rule 2: Formatting and encapsulation

Raw bits are not enough. Every message must follow a specific format or structure, and the structure depends on the type of message and the channel used. A video stream, an email, and a web request are all formatted differently, because the receiver must know where one thing ends and the next begins.

To carry a message across a network, each layer of the protocol stack wraps the data with its own control information. This wrapping is called encapsulation. The pieces are:

Header
Control information placed in front of the data — for example the sending and receiving addresses, or a port number.
Payload
The actual data. It is never changed, only surrounded. Trailer — control information placed after the data; at the Data Link layer this holds the Frame Check Sequence (FCS), a checksum used to detect corruption.
Definition — encapsulation. Encapsulation is the process of adding a header (and sometimes a trailer) to data as it moves down the protocol stack, so that each layer can deliver and control the message correctly. The reverse process, on the way up at the receiver, is de-encapsulation.
Message structure · select a part of the message
A message on the medium

Header

There is one more rule in this family that Cisco lists alongside formatting: message size. Long messages must be broken into smaller pieces that fit the minimum and maximum frame sizes the medium allows. A frame that is too large cannot be sent; a frame that is too small may be rejected. The sender splits the data, and the receiver reassembles it in order.

Part 4

Rule 3: Message timing

Even with perfect encoding and formatting, communication fails if devices do not agree about when to talk. Message timing covers three problems.

RuleThe problem it solvesWhat happens without it
Flow controlManaging the rate of data transmission so a fast sender does not overwhelm a slow receiver.The receiver’s buffer overflows and data is lost.
Response timeoutSetting how long a host waits for a reply before assuming none is coming.The host waits forever, or gives up too early and resends.
Access methodDeciding when a device is allowed to transmit on a shared medium.Two devices transmit at once, the signals collide, and both messages are destroyed.

Flow control is a negotiation of speed. If a server can send far faster than a phone can process, the phone tells the server to slow down or pause. Response timeout is a rule for patience: a host waits a defined time for an acknowledgement, and if none arrives it assumes the message was lost and acts accordingly (often retransmitting). Access method matters most on shared media such as a wireless network, where several devices use the same radio channel and must take turns.

Note. These three ideas reappear later with different names. Flow control and acknowledgements are the heart of TCP (Lesson 03 and Week 8), and the access method is what Ethernet’s CSMA/CD and Wi-Fi’s CSMA/CA implement (Week 4).
Part 5

Message delivery options

Finally, a protocol must specify who the message is for. There are three delivery options, and a broadcast behaves very differently from a unicast at the edge of the network.

Delivery options · select one
Sender one source Receiver A a single host Receiver B group member Receiver C group member

OptionMeaningExample
UnicastOne to one. One sender, one specific receiver. A browser requesting a web page from one server.
MulticastOne to many (a group). One sender, a defined group of receivers that have joined. A router sending video to subscribed IPTV viewers.
BroadcastOne to all. One sender, every device on the local network. An ARP request asking “who has this IP address?”
Watch out. A broadcast reaches every device on the local network only — it does not cross a router into other networks. This is why a broadcast storm can cripple one network while leaving its neighbours unaffected, and why a router is said to break up a broadcast domain (Week 2).
Part 6

Shared rules, standards bodies, and key terms

Imagine what networking would be like without shared, open rules. Each vendor would invent its own format, and only devices from the same vendor could talk. You could not connect a Dell laptop to a Cisco switch to reach an Apache server on a Linux machine — every link would need a translator.

Open protocols solve this. Because a header is defined field by field in a public standard, any vendor can implement it, and any two implementations that follow the standard will interoperate. This is the single biggest reason the Internet grew from a research project into a global utility: the rules are public, and everyone implements the same ones.

The two-people analogy. Picture two people talking in a room. To understand each other they must speak the same language (encoding and formatting); speak clearly and at a pace the listener can follow (flow control); wait a sensible time for an answer before assuming they were ignored (response timeout); and take turns without both talking at once (access method). If one person speaks to the whole room, that is a broadcast; to a small named group, a multicast; and to one person, a unicast. Notice that none of this depends on the brand of their vocal cords or the language of their thoughts — only on the shared rules of the conversation.

Standards organizations

Protocols do not appear by magic; they are written, reviewed, and published by standards bodies. Each one owns a different slice of the network.

OrganizationWhat it governsExample output
IETFInternet standards, especially the TCP/IP suite; publishes RFCs (Request for Comments).RFC 1122, RFC 1180
IEEELAN/WAN standards at the physical and data-link layers.IEEE 802.3 (Ethernet), IEEE 802.11 (Wi-Fi)
IANAProtocol numbers and port numbers, plus IP address and AS number allocation.Service Name and Port Number Registry
ICANNCoordination of the DNS domain-name system and the root servers.Managing domain names and IP allocation policy
ISOInternational standards across many industries, including the OSI reference model.OSI model (ISO/IEC 7498-1)
ITU-TGlobal telecommunications standards.Voice/video codecs, DSL, optical transport
W3CWorld Wide Web standards.HTML, CSS, XML
Exam tip. Keep the roles straight. The IETF writes the RFCs that define Internet protocols; IEEE defines Ethernet and Wi-Fi at Layers 1–2; IANA assigns port numbers (HTTP 80, HTTPS 443, and so on). If an exam question asks who owns a protocol number or port, the answer is IANA.

Key terms

TermMeaning
ProtocolAn agreed set of rules for the format, order, and actions of data exchange between devices.
EncodingConverting information into signals suitable for transmission on a medium.
DecodingConverting received signals back into information.
FormattingStructuring a message in a form the receiver expects.
EncapsulationAdding a header (and sometimes a trailer) to data as it moves down the protocol stack.
Flow controlManaging the rate of transmission so a fast sender does not overwhelm a slow receiver.
Response timeoutHow long a host waits for a reply before assuming the message was lost.
Access methodThe rules for when a device may transmit on a shared medium.
Unicast / Multicast / BroadcastDelivery to one host / a subscribed group / all hosts on the local network.
RFCRequest for Comments; a published Internet standard or specification from the IETF.

Sources & references

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