Layer 3: The Network Layer - IP, Names & Routing

📛 What's in a name?

IP = your public persona, like "John Doe" — but global and registered

At Layer 3 we deal with IP addresses. In our mail analogy, an IP address is like a full legal name — think "John Doe." It's the name you put on a resume, a shipping label, or a conference badge. It's your reachable identity beyond your own front door.

The "John Doe" problem: There are thousands of people named "John Doe" in the world. If I write a letter addressed only to "John Doe, USA" — where does it go? How does the postal service know which John Doe gets the message? That's exactly the challenge with IP addresses. Many devices can share the same IP concept (like private IP ranges or overlapping networks), but we need extra magic to deliver correctly.

Here's the critical difference: Your IP (your name) is something you must register with an organization — either a small local registrar (like your home router handing out private IPs) or a huge global authority (like IANA giving public IP blocks to ISPs). Think of these registration organizations as "Routers." They keep the directory that maps "John Doe" to a physical mailbox location.

Local registrar

Your home router (DHCP server) says: "Inside this house, 192.168.1.5 means YOU." That's like a neighborhood club giving you a nickname. It only works inside the local block. Other routers don't know that private name — and they shouldn't!

Global authority

Your ISP gets a block of public IPs from the big registries (ARIN, RIPE, etc.). That IP (e.g., 203.0.113.42) is globally unique — like a legal name + social security number combo. Any router in the world can find you.

"I am John Doe, registered with the city post office on Maple Street."
That registration is what makes delivery possible. Without registration, your name is just a ghost in the machine.

So how do we get the message to the right John Doe? Great question. This is where routers and routing tables shine. Each router maintains a list (like a phonebook) that says: "To reach John Doe from THIS organization, send mail to THAT next-stop." If your router doesn't know the exact John Doe, it asks a bigger router — upstream until someone says "Ah, that's my John Doe!"

Registering your name (IP assignment)

Local registration (Private IP): Your router assigns you an IP like 192.168.1.22 — only meaningful inside your home network. Like being "John Doe" in your apartment building. The world outside doesn't know this name, so your router performs NAT (Network Address Translation) to rewrite the return address.
Global registration (Public IP): Your ISP gives you a unique IP 98.139.183.24 — this is like having a legal name + passport number registered with the UN. Any router on the internet can forward traffic to that exact address.

The beautiful thing? The registration hierarchy mirrors routing: small routers (like home gateways) only know local names. Core internet routers (Tier-1 ISPs) have the full phonebook of the planet. You can register with a tiny post office, or with a giant one — but either way, the name only works within the scope of that organization's reach.

This is as deep as we'll touch here, because at this level: there is a TON you can do with a name. Subnetting, CIDR, classless routing, BGP, route aggregation, policy-based forwarding... the list goes on. But the core truth remains: Layer 3 is the layer of globally significant names and organized directories. Without the registration and the routers acting as registrars, an IP is just a meaningless string — like shouting "John Doe!" in an empty stadium.

Mind blown? You've just learned why the internet doesn't collapse: because IP addresses are registered pieces of identity, not just random tags. MAC addresses are birthmarks (hardware level). IP addresses are chosen, assigned, and announced — exactly like registering a legal name with a government or a club.

🔗 From SSN to Public Persona

MAC = private family identifier, IP = your official registered name

If you remember from Layer 2: MAC addresses were like Social Security Numbers — only your close family/household knows them, and they never leave the local neighborhood. But an IP address? That's the name you put on your mailbox, your driver's license, your global shipping address.

Here's the magic glue: ARP (Address Resolution Protocol) bridges the two layers. When a router or device says, "I know the IP name 'John Doe' (192.168.1.10), but what's his MAC/SSN inside this subnet?" ARP yells across the local broadcast domain: "Who has IP 192.168.1.10? Tell me your MAC!" That's how your device connects the registered global name to the physical hardware identifier.

Local Registrar: Home Router (DHCP) Regional Registrar: ISP / ARIN Global Root: IANA

Without registration, IP is just a fantasy. With registration, the whole world can find you. And routers? They're the postal clerks that look at the "To: John Doe, Apt 4B" and figure out: "Ah, I need to send this to the next sorting center on 5th Avenue." That decision — hop by hop — is routing. And you've just grasped the heart of Layer 3.

🚀 The power of a registered name

Subnets, supernets, and why hierarchy wins

When you register an IP name (or a block of them), you get to control routing. Big organizations register entire prefixes — like 192.0.2.0/24 — that's like owning the last name "Doe" on a whole city block. Routers then only need to remember the block, not every single John, Jane, and Jack within it. This is called route aggregation, and it's why the internet routing table doesn't explode.

A glimpse of the possibilities: With Layer 3 naming, you can build virtual private networks (VPNs), traffic engineering, anycast (one name, many locations), and even move your IP address between data centers (thanks to BGP). All because an IP is a registered name, not etched in silicon like a MAC.

But for now, celebrate: you now understand that "What's in a name?" — at Layer 3, the answer is registration, hierarchy, and routability. Without those three things, your message to "John Doe" would never arrive.

Continue to Layer 4 → Ports & Transport

OSI Home Back to Top