Computer networks can seem complex, but they follow a set of rules, much like a postal service. To make sense of these rules, experts created conceptual frameworks called models. These models break down the process of sending information from one computer to another into smaller, manageable steps called layers.

The most famous conceptual model is the Open Systems Interconnection (OSI) model. It has seven layers, each with a specific job. Think of it as a detailed, seven-step guide for sending a package. While it's great for understanding theory, it's not what the modern internet actually uses.

The internet actually runs on a simpler, more practical model called the TCP/IP model. It combines some of the OSI layers into four broader categories. It's the real-world blueprint for how your computer sends a request to a website and gets a webpage back.

Within the TCP/IP model, a few key protocols do most of the heavy lifting. A protocol is simply a set of rules for communication. The most important ones are IP, TCP, and UDP.

Once a packet arrives at the correct computer, the Transport layer takes over. Here, we have two main choices for how to handle the delivery: TCP and UDP.

Transmission Control Protocol (TCP) is the reliable option. Before sending data, it establishes a connection with the receiver in a process called a three-way handshake. It then numbers each data packet, sends them, and waits for confirmation that they arrived safely and in the right order. If a packet gets lost, TCP resends it. This makes it perfect for things where accuracy is critical, like loading a webpage or sending an email.

User Datagram Protocol (UDP) is the fast, no-frills option. It just sends the data packets and hopes for the best. There's no handshake, no confirmation, and no re-sending lost packets. This might sound bad, but it's great for real-time applications where speed is more important than perfect accuracy. A few dropped pixels in a video stream or a split-second of lag in a game is better than waiting for a lost packet to be resent.

Every device on the internet needs a unique address, just like every house on a street. This is its IP address. The most common format you'll see is IPv4, which looks like four numbers separated by periods.

Each of the four numbers, called an octet, can range from 0 to 255. This address serves two purposes: it identifies the network the device is on, and it identifies the specific device (or host) on that network. But how does a computer know which part of the address is the network and which part is the host?

That's where the subnet mask comes in. It's another set of four numbers that looks like an IP address (e.g., 255.255.255.0). By applying the mask, a device can figure out its network address.

This process of using a subnet mask to divide a larger network into smaller, more manageable pieces is called subnetting. It's like taking a large city (a big network) and dividing it into zip codes (subnets). This helps organize traffic, improve performance, and enhance security by keeping data within the right 'neighborhood' unless it's specifically meant to go elsewhere.

Understanding these models, protocols, and addressing schemes is the first step to mastering how the internet works.