How the Internet Actually Works

Oren: If the Internet feels a little like weather, everywhere, important, vaguely mysterious... today, we make it more concrete. Mateo: Yes, please. Because people say, "the Internet," like it’s one giant machine humming in a basement somewhere. Oren: Right, and it isn’t. The Internet is a global system of interconnected computer networks and electronic devices that communicate using shared, standardized protocols. In plain language, it’s a network of networks. Mateo: So, not one company, not one box, not even one owner. Oren: Exactly. It’s infrastructure. Many networks, run by many organizations, all agreeing on the same basic rules so information can move between them. Mateo: Like roads, maybe... built by different places, but your trip can continue because the signs and lanes make sense? Oren: That’s the idea. And the roots go back to 1969, when ARPANET was conceived by the U.S. Department of Defense’s Advanced Research Projects Agency to connect research computers at different universities. That same year, Charley Kline at UCLA tried to send "LOGIN" to Bill Duvall at Stanford... but the system crashed after "LO." Mateo: A very humble beginning. Oren: It really was. Then, in 1974, Vint Cerf and Robert Kahn introduced TCP/IP, which standardized how data could move across networks. And in 1995, commercial restrictions were lifted, opening the way to widespread public access. Mateo: Okay, quick picture. I send an email from home to someone at a university. What happens? Oren: Briefly... it leaves your computer, enters your home network, moves into your provider’s network, crosses other providers’ networks, then reaches the university’s network. Mateo: Different hands, same shared rules. Oren: Yes. And today, that system spans millions of computers across hundreds of thousands of smaller networks. Mateo: That’s the takeaway, huh... the Internet is a network of networks. Oren: Exactly. Next time, we’ll talk about how information travels across it, in packets. Mateo: See you then.

Oren: Last time, we were talking about addresses... how devices know where something is supposed to go. And today is the next step... how the data actually moves once you hit send. Mateo: Right, because it does not feel like a thousand little couriers leave my phone every time I send a photo. Oren: It kind of does, though. The internet breaks data into small pieces called packets. So, um, that photo is not usually traveling as one big block. It becomes many small packets, and each one carries part of the photo plus some directions... things like the source and destination IP addresses. Mateo: So each packet has, basically, its own little mailing label. Oren: Exactly. And then we can follow one. Say you tap send on your smartphone. One packet leaves the phone, reaches your home router... the router reads the addressing information and says, okay, not for me, onward. It sends that packet to your internet provider’s router. Mateo: First hop. Oren: First hop, yes. Then the ISP router does the same thing. It checks its routing table, picks the next best stop, and forwards the packet along. Hop by hop, across different networks, it moves toward the server. Mateo: And meanwhile other packets from the same photo might take slightly different paths, right? Oren: Right. That’s part of what makes packet switching efficient. Lots of people can share the same roads. Then, at the far end, TCP/IP does the quiet organizing work. IP handles the addressing and routing. TCP helps make sure packets are sequenced properly, and if something goes missing, corrected so the data can be reassembled in the right order. Mateo: So the takeaway is... your data travels in lots of small pieces, routers guide those pieces along, and the receiving device puts the whole thing back together. Oren: That’s it. Next time, we’ll stay with the journey... and look at what happens when the road gets crowded.

Oren: Last time, packets were the envelopes and protocols were the rules of the road. Today, uh, we need the street name and the house number. Mateo: Yeah, because "send it to the internet" is not, um, super helpful. Oren: Exactly. Every device online has an IP address, a unique numeric identifier. It's the network version of an address. Mateo: So my phone, your laptop, the server holding a website, all of them. Oren: Right. But people remember names better than numbers, so we type example.com. DNS, the Domain Name System, translates that human name into the IP address a browser can actually use. Mateo: So, basically, the internet's phonebook. Oren: Very much. Quick demo? Mateo: Okay. DNS, I'd like example.com. Oren: And, for our little simulation, the reply is, "example.com maps to 192.0.2.1." Plain English, the name you typed points to this numeric destination. Mateo: I remember the name, the network remembers the number. Oren: Exactly. The older address system, IPv4, gives us about 4.3 billion addresses. IPv6 is the newer, much larger version, meant to support many, many more devices. Mateo: So the takeaway is simple, DNS is the phonebook that turns names into the numeric addresses devices actually use. Oren: Yeah... and next time we'll follow what happens once you reach that address. Mateo: See you then.

Oren: Last time, in Names and Addresses, IP and DNS gave the internet a way to find things. Today, um, we look at the roads and buildings underneath. Mateo: Right, because "the cloud" sounds fluffy... and then you remember, wait, some of this is literally under the ocean. Oren: Exactly. The internet feels invisible, but its backbone is deeply physical. Huge amounts of cable carry it, including undersea fiber-optic cables that connect continents. So, if the internet is a city, these are the highways and bridges. Mateo: And the apartment buildings are... data centers? Oren: Pretty much, yeah. Data centers house servers, the machines that store and process web content. Your photos, a video stream, a search result, they all have to live somewhere, and be handled by something. Mateo: Okay, do the trace-the-request thing. I love that part. Oren: All right. You open a laptop and click a website. First hop, over Wi‑Fi to your router. Mateo: And that matters, because Wi‑Fi carries over 60 percent of global traffic, which is kind of wild. Oren: It is. Or you might use cellular instead. But that wireless part is usually just the last hop. From there, the request often drops into a local fiber line, travels across larger networks, maybe through an undersea cable, and ends up in a data center rack where a server answers back. Mateo: So... not magic, not air, not really. Oren: Air for the first step, cables and buildings for much of the rest. And the internet’s speed and reach depend on those massive systems we rarely see. Next time, we’ll talk about what that means for privacy.

Oren: Last time we ended up under the ocean, with those cables quietly doing the work... Mateo: ...and that raises the very normal question: okay, who, uh, runs all this? Oren: The short answer is, no one does, alone. The Internet is more like a city than a company. Lots of people build parts of it, maintain parts of it, depend on it... but there isn't one central boss. Mateo: So no giant master keyboard. No one in a swivel chair deciding where my cat video goes. Oren: Afraid not. Internet providers run their networks. Companies run services. Governments, the private sector, civil society, universities, engineers, users... all of them have a role. That's the multi-stakeholder idea. Many hands, not one ruler. Mateo: And the shared rules, the protocols, those get made how? Oren: Usually out in the open. People propose changes, test them, argue a little, revise them, and if enough of the right people agree, they get adopted. Mateo: Tiny demo? Oren: Sure. ISP engineer: "This update could move traffic more smoothly." Standards group person: "Okay, but is it documented clearly, and can different networks use it?" University researcher: "And is it secure enough?" They talk, adjust, agree on a version they can all live with. Mateo: Not glamorous, but kind of beautiful. Oren: It is. You'll hear names like ICANN or the Internet Governance Forum, but those coordinate pieces or host discussion. They don't run the whole Internet. Mateo: And it's still changing. More infrastructure, better performance... and bigger questions about privacy, security, surveillance, censorship, and fair access. Oren: So maybe the takeaway is this: the Internet is run by many hands, through shared rules, and it keeps evolving. Mateo: Messy, human, and very much alive. Thanks for listening.