Mapping the Internet Evolution
Shire writes "Science magazine is running a story on the DIMES project, which has ventured to map the structure and evolution of the Internet (PDF) using open source distributed clients in the style of SETI@Home and such. DIMES has already collected more than 40 Millions measurements which resulted in some nice pictures and several scientific presentations. Those who use traceroute may find it a useful (and colorful) alternative."
Rebel spies have intercepted the plans to the Death Star and posted them on this site.
http://www.netdimes.org/ipmap.png
They obviously don't know that much about internet evolution...
I have freaks! I did something right...
http://mirrordot.org/
:-)
All the links mirrored.
"Your effort to remain what you are is what limits you."
The Internet is far too complex to have just "Evolved". Things like this don't just spring into being without an Intelligent Designer. We even know exactly who the designer was: Al Gore. And we know exactly why he designed it: to route around nuclear wars. The media needs to stop trying to represent unproven theories as the truth when we already know the truth.
Mirrordot Science magazine is running a story on the DIMES project, which has ventured to map the structure and evolution of the Internet (PDF) using open source distributed clients in the style of SETI@Home and such. DIMES has already collected more than 40 Millions measurements which resulted in some nice pictures and several scientific presentations
If you pay your taxes you support terrorism!
Cmon now... can't we all agree that this was intelligent design? I mean, look at a router... its so intricate, so... functional.... it must have been put here for this purpose by a higher power.
There's nothing Intelligent about Intelligent Design.
Blasphemy indeed! Everyone knows the internet is FLAT! Only heretics believe the internet is ROUND! If you send a packet with a large enough TTL, it falls right off the edge!
Generally speaking, one is not Slashdotted every day. I've been Slashdotted once before (and I consider myself lucky for it). I can remember feeling a sense of relief/pride when the servers held and my Open Source PHP CMS project didn't crap out into oblivion due to the pressure. There was no outage... just a crapload of pages served.
Sensible code and good bandwidth are the only way to fly.
The dangers of knowledge trigger emotional distress in human beings.
Did anyone look at the IP Map and immediately think, "Boy that looks a lot like a Skittles commerical." ?
Hi guys, hopefully I'm not shooting my self in the foot here, but here are some screenshots of how traceroutes look from our agent: by ISP, by country and here's another one. You are all welcomed to try our agent out. Linux version will be coming soon.
In a nutshell, it's kinda showing you connectivity and relative size of an ISP. What it's showing with the red spheres is that there are a few Autonomous Systems (AS) that have lots (hundreds or thousands) of inbound and outbound links to other ASes. Think UUNet or Sprint, alot of people are connected to them, as well as some ISPs. Then you have those smaller (tier-2, the orange to blue skittles) ISPs that are connected to UUnet and also connected to tens of other ISPs. All the way at the edge, you have people who are single homed only to their ISP, but they are not a transit network, meaning they don't send traffic from one AS to another. Any traffic on their link is either from their network or to their network. And there are lots and lots of those, they are the little purple skittles on the outside.
The lines represent the connections between these ASs. All the real connections arent there, the entire background would most likely be completely black if they were.
So it's showing that there are some really huge ISPs that form the "backbone" of the internet, and lots of smaller ISPs and thousands of even smaller ISPs. When you see a line that does not connect to/from the center, that's a connection between a tier-2 ISP to another tier-2 ISP. Usually this is done as a backup mechanism, sometimes it can also be done to more effectively get traffic to another network. For example, if UUNet charges you per byte, and they can get to anyone, you would think that you could just send all your traffic to UUnet. But you might find that a large percentage of your traffic is going to networks that are directly attached (peered) to Level3's network, and Level3 charges less per byte. It might make sense then to peer with Level3 in addition to UUNet, or completely with Level3. I'm leaving some stuff out here but this is the general idea, and what the picture is showing you.
Incidentally, there is also a concept in the internet backbone called "hot potato routing". If I am in LA with Sprint and sending traffic to NY to a UUnet customer, Sprint will do everything it can to put the traffic on UUNet's network while in LA. In otherwords, if this traffic is for a UUnet customer, it won't be sent across Sprint's network from LA to NY. Sprint drops it on UUNet's network at the first opportunity. The routing protocol for the backbone, BGP, has more than 10 different metrics it looks at to decide which route to take, and several rules to follow to decide what is the "best" path. Best is not always shortest or fastest once all the metrics are taken into account. So if you thought the internet was a big harmonious cooperative effort, guess again!