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.
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?
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.
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.
| Medium | How bits are encoded |
|---|---|
| Copper cable | As patterns of electrical impulses (voltage). |
| Fibre-optic cable | As 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.
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:
Control information placed in front of the data — for example the sending and receiving addresses, or a port number.
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.
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.
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.
| Rule | The problem it solves | What happens without it |
|---|---|---|
| Flow control | Managing 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 timeout | Setting 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 method | Deciding 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.
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.
| Option | Meaning | Example |
|---|---|---|
| Unicast | One to one. One sender, one specific receiver. | A browser requesting a web page from one server. |
| Multicast | One to many (a group). One sender, a defined group of receivers that have joined. | A router sending video to subscribed IPTV viewers. |
| Broadcast | One to all. One sender, every device on the local network. | An ARP request asking “who has this IP address?” |
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.
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.
| Organization | What it governs | Example output |
|---|---|---|
| IETF | Internet standards, especially the TCP/IP suite; publishes RFCs (Request for Comments). | RFC 1122, RFC 1180 |
| IEEE | LAN/WAN standards at the physical and data-link layers. | IEEE 802.3 (Ethernet), IEEE 802.11 (Wi-Fi) |
| IANA | Protocol numbers and port numbers, plus IP address and AS number allocation. | Service Name and Port Number Registry |
| ICANN | Coordination of the DNS domain-name system and the root servers. | Managing domain names and IP allocation policy |
| ISO | International standards across many industries, including the OSI reference model. | OSI model (ISO/IEC 7498-1) |
| ITU-T | Global telecommunications standards. | Voice/video codecs, DSL, optical transport |
| W3C | World Wide Web standards. | HTML, CSS, XML |
Key terms
| Term | Meaning |
|---|---|
| Protocol | An agreed set of rules for the format, order, and actions of data exchange between devices. |
| Encoding | Converting information into signals suitable for transmission on a medium. |
| Decoding | Converting received signals back into information. |
| Formatting | Structuring a message in a form the receiver expects. |
| Encapsulation | Adding a header (and sometimes a trailer) to data as it moves down the protocol stack. |
| Flow control | Managing the rate of transmission so a fast sender does not overwhelm a slow receiver. |
| Response timeout | How long a host waits for a reply before assuming the message was lost. |
| Access method | The rules for when a device may transmit on a shared medium. |
| Unicast / Multicast / Broadcast | Delivery to one host / a subscribed group / all hosts on the local network. |
| RFC | Request for Comments; a published Internet standard or specification from the IETF. |
Sources & references
- Braden, R. RFC 1122: Requirements for Internet Hosts — Communication Layers (1989). rfc-editor.org/rfc/rfc1122.
- Socolofsky, T. & Kale, C. RFC 1180: A TCP/IP Tutorial (1991). rfc-editor.org/rfc/rfc1180.
- IANA. Service Name and Transport Protocol Port Number Registry. iana.org.
- IEEE. IEEE 802.3 (Ethernet) and IEEE 802.11 (Wireless LAN). standards.ieee.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). rfc-editor.org/rfc/rfc1122.
- Socolofsky, T. & Kale, C. RFC 1180: A TCP/IP Tutorial (1991). rfc-editor.org/rfc/rfc1180.
- IANA. Service Name and Transport Protocol Port Number Registry. iana.org.
- IEEE. IEEE 802.3 (Ethernet) and IEEE 802.11 (Wireless LAN). standards.ieee.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.