pull down to refresh

When I was still in university, I started reading Computer Networking - A Top-Down Approach.
It was a very interesting book because I'm very interested in how the internet came to be, but I got distracted by actually learning what I needed for the upcoming exams, and I forgot about it afterward.
This article sparked my interest again. I should definitely finish that book.
At its core, the Internet is an interconnected fabric of separate networks. Each network which makes up the Internet is operated independently and only interconnects with other networks in clearly defined places.
For smaller networks like your home, the interaction between your network and the rest of the Internet is usually pretty simple: you buy an Internet service plan from an ISP (Internet Service Provider), they give you some kind of hand-off through something like a DSL or cable modem, and give you access to “the entire Internet”. Your router (which is likely also a WiFi access point and Ethernet switch) then only needs to know about two things; your local computers and devices are on one side, and the ENTIRE Internet is on the other side of that network link given to you by your ISP.
For most people, that’s the extent of what’s needed to be understood about how the Internet works. Pick the best ISP, buy a connection from them, and attach computers needing access to the Internet. And that’s fine, as long as you’re happy with only having one Internet connection from one vendor, who will lend you some arbitrary IP address(es) for the extend of your service agreement, but that starts not being good enough when you don’t want to be beholden to a single ISP or a single connection for your connectivity to the Internet.
That also isn’t good enough if you are an Internet Service Provider so you are literally a part of the Internet. You can’t assume that the entire Internet is that way when half of the Internet is actually in the other direction.
This is when you really have to start thinking about the Internet and treating the Internet as a very large mesh of independent connected organizations instead of an abstract cloud icon on the edge of your local network map.
What do you think of point 1 below?
To become your own Internet Service Provider with customers who pay you to access the Internet, or be your own web hosting provider with customers who pay you to be accessible from the Internet, or your own transit provider who has customers who pay you to move their customer’s packets to other people’s customers, you need a few things:
  1. Your own public IP address space allocated to you by an Internet numbering organization
  2. Your own Autonomous System Number (ASN) to identify your network as separate from everyone else's networks
  3. At least one router connected to a different autonomous system speaking the Border Gateway Protocol to tell the rest of the Internet that your address space is accessible from your autonomous system.
It seems like the internet isn't really that decentralized because the address space is controlled by a centralized body.
reply
67 sats \ 0 replies \ @ek OP 3h
There are even more layers where similar problems exist: registrars for DNS, root certificate authorities for TLS, and CDNs like Cloudflare.
But I’d say it works well enough, since we literally built the darknet and permissionless money on it. If we don’t consider the internet decentralized, then we also can’t consider bitcoin decentralized.
For all practical purposes, I think we can consider the internet decentralized, as long as I can buy weed online and pay with cryptocurrency.
reply
100 sats \ 0 replies \ @optimism 3h
I learned how the internet works in the 80s, so I'm going to read that book; it will be fun. Thanks.
reply
100 sats \ 0 replies \ @Scoresby 3h
I would zap good sats for a killer article explaining the architecture of the internet. It's something I've often wanted to spend time learning about but have never taken the time to pursue.
I'll bookmark your book recommendation and perhaps someday come back to it.
reply
All you gotta know is the TCP/UDP stack! ~lol