Understanding Common Internet Protocols: A Beginner-Friendly Guide

I've been exploring how computers communicate and exchange information over the Internet.

One thing I've come to appreciate is that communication between computers doesn't happen randomly. There are established rules that define how information is addressed, transmitted, received, and managed.

These rules are known as network protocols.

In this article, I'm sharing my understanding of some common Internet protocols, their functions, and practical examples to make them easier to understand.

1. What Are Internet Protocols?

Internet protocols are sets of rules that allow computers and other devices to communicate over a network.

Most Internet communication relies on the TCP/IP protocol suite, which provides the foundation for exchanging data between devices across interconnected networks.

Think of protocols as a common language that computers use to communicate. Without these rules, devices would struggle to understand how to send, receive, and process information.

Different protocols perform different responsibilities, depending on the type of communication required.

Let's explore some of the most common ones.

2. ARP (Address Resolution Protocol)

ARP is used to find the physical (MAC) address associated with a given IP address on a local network.

To understand this, remember that devices use IP addresses for logical addressing, while MAC addresses identify network interfaces at the hardware level.

Example:

Imagine your computer wants to communicate with another device on the same local network. It knows the device's IP address but needs its MAC address to deliver the Ethernet frame.

ARP helps discover that MAC address.

Key takeaway: ARP translates an IP address into a MAC address.

3. IP (Internet Protocol)

The Internet Protocol is responsible for addressing and routing data packets between devices and networks.

It allows data to travel from a source device to a destination using IP addresses.

For example, when you visit a website, IP helps ensure that your request can be routed towards the server hosting that website.

IP itself does not guarantee that packets will arrive successfully or in the correct order. Other protocols, such as TCP, can provide additional reliability.

Key takeaway: IP handles logical addressing and packet delivery across networks.

4. RARP (Reverse Address Resolution Protocol)

RARP performs the opposite function of ARP.

It allows a device to discover its IP address using its MAC address.

Historically, it was used by diskless computers that did not have permanent local storage and needed to obtain their IP addresses when starting up.

RARP has largely been replaced by more flexible protocols such as BOOTP and DHCP.

Key takeaway: RARP translates a MAC address into an IP address.

5. TCP (Transmission Control Protocol)

TCP is a connection-oriented protocol that provides reliable data transmission between devices.

Before exchanging data, TCP establishes a connection between the communicating devices.

It provides several important features:

• Ensures data is delivered reliably.
• Maintains the correct order of data.
• Detects lost or corrupted segments.
• Retransmits missing data when necessary.
• Uses acknowledgements to confirm successful receipt.

Practical example:

When downloading an important document, you want the complete file rather than missing sections. TCP helps ensure reliable delivery.

Key takeaway: TCP provides reliable and ordered communication.

6. UDP (User Datagram Protocol)

UDP is a connectionless transport protocol.

Unlike TCP, it does not establish a connection before sending data and does not guarantee delivery or packet ordering.

However, it has less communication overhead, making it useful for applications where speed and low latency are important.

Practical examples:

• Online gaming.
• Live video and audio communication.
• Voice calls.
• Real-time streaming applications.

For these applications, waiting for every missing packet to be retransmitted may affect the user experience.

Key takeaway: UDP provides fast, connectionless communication without guaranteed delivery.

7. FTP (File Transfer Protocol)

FTP is used to transfer files between computers over a network.

It supports operations such as:

• Uploading files to a remote server.
• Downloading files from a server.
• Managing files on remote systems.

Traditionally, FTP uses username and password authentication.

However, standard FTP does not encrypt its communication. More secure alternatives include SFTP and FTPS.

Practical example:

A developer may use a file transfer client to upload website files to a remote hosting server.

Key takeaway: FTP is used for transferring files between computers.

8. HTTP (Hypertext Transfer Protocol)

HTTP is the protocol used for communication between web browsers and web servers.

When you enter a website address into your browser, the browser sends an HTTP request to the server. The server processes the request and sends back a response.

For example:

1. You enter a website address.
2. Your browser sends a request to the web server.
3. The server processes the request.
4. The server returns the requested web resource.
5. Your browser displays the content.

HTTPS is the secure version of HTTP. It uses TLS encryption to protect communication between the browser and server.

Key takeaway: HTTP enables communication between web browsers and web servers.

9. DHCP (Dynamic Host Configuration Protocol)

DHCP automatically assigns IP addresses and other network configuration details to devices joining a network.

Without DHCP, network administrators would often need to configure IP addresses manually.

Practical example:

When you connect your laptop or smartphone to a Wi-Fi network, DHCP can automatically provide:

• An IP address.
• A subnet mask.
• A default gateway.
• DNS server information.

This makes network management easier, especially in environments with many connected devices.

Key takeaway: DHCP automatically provides IP configuration to network devices.

10. RIP (Routing Information Protocol)

RIP is a dynamic routing protocol that allows routers to exchange information about available network routes.

It uses a distance-vector routing algorithm to determine the best route based on the number of router hops.

A hop represents a router that a packet passes through when travelling towards its destination.

RIP has a maximum of 15 usable hops. A distance of 16 is considered unreachable.

Key takeaway: RIP helps routers exchange routing information and select routes using hop count.

11. OSPF (Open Shortest Path First)

OSPF is another dynamic routing protocol used to determine the best paths for forwarding data through a network.

Unlike RIP, which uses a distance-vector approach, OSPF uses a link-state approach.

Routers exchange information about their network links and use this information to calculate the shortest paths.

OSPF is suitable for larger and more complex networks.

Key takeaway: OSPF is a link-state routing protocol that calculates optimal network paths.

12. POP3 (Post Office Protocol Version 3)

POP3 is an email retrieval protocol that allows email clients to download messages from a mail server.

Traditionally, POP3 downloads emails to a local device, although modern implementations may support additional server-side options.

Practical example:

An email application can use POP3 to retrieve messages from your email account.

Key takeaway: POP3 is used to retrieve emails from a mail server.

13. IMAP4 (Internet Message Access Protocol Version 4)

IMAP4 is an email access protocol that allows users to access and manage messages stored on a mail server.

Unlike traditional POP3 usage, IMAP keeps messages on the server and synchronises changes across connected devices.

Practical example:

You can read an email on your laptop and later access the same mailbox on your smartphone, with your email activities synchronised.

Key takeaway: IMAP4 allows users to access and synchronise emails across multiple devices.

14. Telnet

Telnet is a protocol that allows users to establish remote command-line sessions with another computer over a network.

It relies on TCP for communication.

Although it was historically used for remote administration and troubleshooting, Telnet sends information, including login credentials, without encryption.

Because of this security weakness, SSH (Secure Shell) is preferred for modern remote administration.

Key takeaway: Telnet provides remote command-line access but is insecure because it does not encrypt communication.

---

15. Comparing Some Important Protocols

Understanding the differences between similar protocols makes networking concepts easier to remember.

TCP vs UDP

TCP	UDP
Connection-oriented	Connectionless
Reliable transmission	No delivery guarantee
Maintains data order	No ordering guarantee
Retransmits missing data	No automatic retransmission
More communication overhead	Less communication overhead

ARP vs RARP

ARP	RARP
IP address to MAC address	MAC address to IP address
Discovers hardware addresses	Historically discovers IP addresses

POP3 vs IMAP4

POP3	IMAP4
Retrieves emails	Accesses and manages emails
Traditionally downloads emails locally	Keeps emails on the server
Less suited to multi-device synchronisation	Supports multi-device synchronisation

RIP vs OSPF

RIP	OSPF
Distance-vector protocol	Link-state protocol
Uses hop count	Uses link cost
Maximum 15 usable hops	Supports larger networks
Simpler routing approach	More advanced routing approach

---

16. Quick Reference: Common Internet Protocols

Protocol	Main Function
ARP	Finds a MAC address using an IP address
IP	Addresses and routes data packets
RARP	Historically finds an IP address using a MAC address
TCP	Provides reliable data transmission
UDP	Provides connectionless data transmission
FTP	Transfers files
HTTP	Transfers web resources
DHCP	Automatically assigns IP configuration
RIP	Exchanges routing information using hop count
OSPF	Calculates routes using link-state information
POP3	Retrieves emails
IMAP4	Accesses and synchronises emails
Telnet	Provides remote command-line access

Final Thoughts

Learning about Internet protocols has helped me understand that communication over the Internet involves several layers of processes working together.

Previously, I mostly interacted with the Internet as an end user. Now, I'm beginning to understand some of the mechanisms that make that communication possible.

One important lesson is that not every protocol performs the same task. Some handle addressing, others manage data transmission, while others support services such as email, file transfers, and web browsing.

I'm sharing these notes as part of my learning journey in Information Technology. If you have additional insights, corrections, or practical examples, feel free to share them in the comments.