Important Internet Protocols

In the previous chapter, "The Rules of E-mail Protocols", we looked at the specific rules—like SMTP and IMAP—that allow our devices to send and receive electronic mail. But those e-mail protocols do not operate in a vacuum. They are passengers riding on a much larger, much older transportation system: the core protocols of the internet itself.

Whether you are sending an e-mail, streaming a cricket match, downloading a PDF syllabus, or simply loading a web page, your data is travelling across the world in milliseconds. How does a video sitting on a server in Mumbai reach your smartphone in Srinagar without turning into a scrambled mess of digital noise?

It happens because every single device on the internet has agreed to speak the exact same foundational languages. We call these languages protocols. In this chapter, we are going to look under the hood of the internet. We will break down the master protocol that runs everything (TCP/IP), the protocols that make the web visible (HTTP and HTTPS), and the heavy-lifting protocol used for moving large files (FTP).

By the end of this chapter, you will not just know what these acronyms stand for; you will understand exactly how they work together to make the modern internet possible.

What Exactly is a Protocol?

Before we dive into the specific acronyms, we need to understand what a protocol actually is in the world of computers.

Imagine you pick up a telephone and call a friend. When they answer, they say, "Hello?" You reply, "Hi, it's me." You then take turns speaking. If you both start shouting at the exact same time, neither of you understands the other. If you speak in Hindi and they only understand French, communication fails. You both unconsciously follow a set of social rules for a phone call: a greeting, a shared language, taking turns, and a goodbye.

Computers need rules, too. But because computers are machines, their rules must be mathematically precise, rigidly structured, and completely unforgiving of errors.

If an Apple iPhone wants to load a web page hosted on a Linux server, they can communicate perfectly because they both obey the same internet protocols. Protocols are the great equalizers of the digital world.

The Bedrock of the Internet: TCP/IP

If you strip away the web browsers, the mobile apps, and the e-mail clients, the entire internet runs on one foundational suite of rules known as TCP/IP.

TCP/IP is actually two separate protocols working together as a team: the Transmission Control Protocol (TCP) and the Internet Protocol (IP). They are so deeply intertwined that they are almost always written together with a slash.

To understand how they work, we have to understand a fundamental problem with computer networks: you cannot send a large file all at once.

The Problem: Traffic Jams

Imagine you want to move an entire brick house from Delhi to Jammu. You cannot put a whole house on a single truck; it would block the entire highway, and if the truck broke down, the entire house would be lost. Instead, you dismantle the house. You number every single brick, load them into thousands of small delivery vans, and send them up the highway. Some vans might take the main highway; others might take a detour if there is a traffic jam. When they all arrive in Jammu, the builders look at the numbers on the bricks and reassemble the house perfectly.

This is exactly how the internet works. It is called Packet Switching.

TCP: The Master Builder

The Transmission Control Protocol (TCP) is the protocol responsible for dismantling and reassembling the house.

When you want to send a photograph to a friend, TCP takes that image file and chops it up into thousands of tiny digital chunks called packets.

TCP does not just chop the file up; it gives every single packet a sequence number (Brick 1, Brick 2, Brick 3...).

TCP is famous for being a reliable protocol. This means it guarantees delivery. When the packets arrive at your friend's phone, the receiving TCP checks the sequence numbers. If it receives packets 1, 2, and 4, it realizes packet 3 is missing. The receiving TCP will immediately send a message back to the sender saying, "I am missing packet 3, please send it again." It will hold onto the other packets and wait until packet 3 arrives before reassembling the photograph and showing it on the screen.

IP: The Postal Service

If TCP is the builder numbering the bricks, the Internet Protocol (IP) is the postal service delivering them.

While TCP handles the chopping and reassembling, IP handles the addressing and routing. IP takes every single packet created by TCP and slaps a "To" address and a "From" address on it. (These are IP addresses, which we covered in a previous chapter).

Once the packet has its IP addresses attached, it is sent out into the internet. The routers on the internet only look at the IP part of the packet. They read the destination address and say, "Okay, this packet needs to go to Srinagar. The fastest route right now is through this cable."

Because the internet is a web of connections, packet 1 and packet 2 might take completely different routes to get to the same destination. Packet 1 might go through a direct cable, while packet 2 might get routed through a different city because of a temporary network outage. This is why packets often arrive out of order, and why TCP's numbering system is so crucial.

The TCP Three-Way Handshake

Because TCP is a reliable protocol that guarantees delivery, it doesn't just start throwing packets at a destination blindly. It politely introduces itself first to make sure the receiving computer is ready. This introduction is a famous concept in networking known as the Three-Way Handshake.

Before a single byte of your photograph is sent, the two computers have a rapid, invisible conversation:

1. 1SYN (Synchronize): Your computer sends a message to the server saying, "Hello, I would like to open a connection and send you some data. Are you there?"
2. 2SYN-ACK (Synchronize-Acknowledge): The server replies, "Hello! Yes, I am here, and I am ready to receive your data."
3. 3ACK (Acknowledge): Your computer replies, "Great, I received your confirmation. I am starting the data transfer now."

Only after this three-step handshake is complete does the actual data begin to flow.

HTTP: The Language of the Web

TCP/IP is the underlying road network of the internet. It can carry any type of data. But when that data specifically represents a web page (like a news article or a shopping site), we need another protocol layered on top of TCP/IP to tell the browser how to display it.

That protocol is HTTP, which stands for Hypertext Transfer Protocol.

Invented by Tim Berners-Lee in 1989 alongside the World Wide Web, HTTP is the set of rules that allows web browsers (like Chrome or Firefox) and web servers to talk to each other.

The Request and Response Cycle

HTTP works on a very simple Client-Server model.

• The Client is your web browser.
• The Server is the powerful computer sitting somewhere in the world that holds the website's files.

When you type a website address into your browser and hit Enter, your browser (the client) sends an HTTP Request to the server. It essentially says, "Please give me the file for your homepage."

The server receives this request, finds the file, and sends back an HTTP Response. This response includes a status code (to say if the request was successful) and the actual content of the web page (the text, images, and layout instructions).

The Problem with HTTP: It is a Postcard

For the early days of the internet, HTTP was perfect. People were just reading static text pages about academic research.

But as the internet grew, people started using it for online shopping, banking, and private messaging. Here, HTTP revealed a massive flaw: HTTP sends all data in plain text.

Imagine writing your credit card number, expiry date, and CVV on the back of a physical postcard and dropping it in a public mailbox. The postman can read it. The sorting facility can read it. The delivery driver can read it. Anyone who intercepts that postcard along its journey can see your secret information.

Because HTTP data travels across dozens of routers on the internet before reaching its destination, any hacker sitting on the same public Wi-Fi network as you, or intercepting traffic at a router, can read your passwords and messages perfectly.

HTTPS: Adding the 'S' for Security

To solve the postcard problem, the internet engineers created HTTPS, which stands for Hypertext Transfer Protocol Secure.

HTTPS is exactly the same as HTTP, but with one crucial addition: a layer of heavy encryption wrapped around the data before it leaves your computer.

How the Encryption Works (SSL/TLS)

HTTPS uses a security protocol called TLS (Transport Layer Security). You will often hear it referred to by its older name, SSL (Secure Sockets Layer).

Instead of sending a postcard, HTTPS is like putting your letter inside an indestructible, locked steel box. You lock the box, and only the specific server you are sending it to has the unique key to unlock it.

If a hacker intercepts an HTTPS packet while you are logging into your bank, they will not see: `Username: Rahul123 | Password: SecretPassword`

Instead, because of the TLS encryption, they will just see a scrambled, mathematical mess of random characters: `x9$kL2pQ!mZ8vN4bY@1cW#7tR%5yU^3iO*`

Even with the world's most powerful supercomputers, it would take millions of years to guess the key and unscramble that text.

Port Numbers: The Doors to the Server

How does a server know if an incoming packet is a regular HTTP request or a secure HTTPS request? It uses Port Numbers.

Think of an IP address as the street address of an apartment building. The Port Number is the specific apartment number inside that building. A server has thousands of virtual "ports" (doors) it can listen to, and different protocols are assigned standard port numbers by international agreement.

• Port 80 is the standard door for unencrypted HTTP traffic.
• Port 443 is the standard door for encrypted HTTPS traffic.

When your browser wants a secure connection, it specifically addresses its packets to Port 443 on the server.

FTP: The Heavy Lifter for Files

While HTTP and HTTPS are fantastic for loading web pages and downloading small attachments, they were not originally designed for heavy-duty file management.

If you are a web developer who needs to upload 5,000 image files to a server to build a new website, doing it one by one through a web browser using HTTP would be a nightmare. If your internet connection drops halfway through, HTTP usually makes you start the download or upload all over again from zero.

For bulk file transfers, the internet relies on FTP, which stands for File Transfer Protocol.

Why Use FTP?

FTP is a dedicated protocol built entirely for moving files between a client and a server. It has several distinct advantages over HTTP for this specific task:

1. 1Directory Management: FTP allows you to see the server's files as if they were folders on your own computer. You can create folders, rename files, and delete directories directly on the server.
2. 2Resuming Transfers: If you are downloading a massive 50 GB file via FTP and your power goes out at 49 GB, FTP can "resume" the transfer when you reconnect, downloading only the final 1 GB.
3. 3Bulk Uploads: You can drag and drop an entire folder containing thousands of files into an FTP client, and it will systematically queue and transfer every single one.

The Two-Port System of FTP

FTP is unique because it uses two separate ports to do its job, splitting the communication into two channels:

• Port 21 (The Command Channel): This is the control room. It is used to send instructions like "log me in," "list the files in this folder," or "delete this file." No actual file data moves through this port.
• Port 20 (The Data Channel): This is the cargo door. When you actually say "download this movie," the heavy file data flows entirely through Port 20.

By keeping the commands and the data separate, FTP remains highly stable even when massive files are clogging up the data channel.

(Note: Just like HTTP, standard FTP sends passwords in plain text. Today, professionals use SFTP—Secure File Transfer Protocol—which wraps the FTP connection in heavy encryption, much like HTTPS does for the web).

Worked Example: Loading a Secure Web Page

To truly understand these protocols, let us look at a step-by-step walkthrough of what happens when you type `https://www.jk.gov.in` into your browser and press Enter. We will see how all the protocols we have learned work together in a matter of milliseconds.

Step 1: The Address Lookup (DNS) Your browser cannot read English words like "jk.gov.in". It needs an IP address. It silently asks a Domain Name System (DNS) server to translate the URL. The DNS server replies: "The IP address is 164.100.14.212."

Step 2: The TCP Handshake Your computer uses TCP to reach out to the server at 164.100.14.212. It sends a SYN packet to Port 443 (because you typed https). The server replies with SYN-ACK, and your computer replies with ACK. The reliable connection is now open.

Step 3: The Security Handshake (TLS/SSL) Because we are using HTTPS, your computer and the server now do a quick mathematical dance to agree on a secret encryption key. From this millisecond onward, everything they say to each other will be locked in a digital vault.

Step 4: The HTTP Request Your browser sends an encrypted HTTP GET Request through the secure tunnel: "Please send me the homepage HTML file."

Step 5: Chopping and Sending (TCP/IP) The server finds the homepage file. It is too big to send at once. The server's TCP chops the homepage into 500 small packets and numbers them. The server's IP slaps your computer's IP address on every single packet and fires them into the internet.

Step 6: Reassembly and Display The packets arrive at your computer, taking various routes. Your TCP checks the sequence numbers, realizes packet 42 is missing, asks the server for it again, and then perfectly reassembles the 500 packets into the original HTML file.

Step 7: The Browser Renders Your browser reads the HTML file and paints the text, colours, and images onto your screen.

All of this happens in the time it takes you to blink, entirely governed by the strict, invisible rules of internet protocols.

Quick Revision

• Protocol: A standardized set of rules that allows computers to communicate, regardless of their hardware or software.
• TCP/IP: The foundational suite of the internet.
• IP (Internet Protocol): Handles addressing and routing. It puts the destination address on the data.
• TCP (Transmission Control Protocol): Handles breaking data into numbered packets, ensuring reliable delivery, and reassembling them at the destination.
• Packets: Small chunks of data. Breaking data into packets prevents network congestion and allows data to route around broken cables.
• HTTP (Hypertext Transfer Protocol): The rules for fetching web pages. It operates on Port 80 and sends data in plain text (insecure).
• HTTPS (Hypertext Transfer Protocol Secure): The secure version of HTTP. It operates on Port 443 and uses TLS/SSL encryption to scramble data, protecting passwords and banking details from hackers.
• FTP (File Transfer Protocol): Used for bulk file transfers and server directory management. It uses Port 21 for commands and Port 20 for actual data transfer.