Slashdot Mirror
Is The Internet Growing Too Fast?
SpunOne writes: "According to this article, the Internet is growing faster than today's routers can handle. After years of predictable growth, the size of the routing table and traffic in it exploded during the past six months, topping 104,000 entries in March, compared with 75,000 a year ago. Even more troubling is evidence that frequent updates to the routing table entries by network managers are causing instability in the Internet's backbone routing infrastructure."
Multihoming and pulling full routes from both providers does not require that much hardware. BGP is not particularly processor intensive. A cisco 2650 with 128 MB of ram can handle the job just fine. In fact a 2620 would work too (processor-wise), but they max out at 64 MB of ram.
You can fix the prefix load caused by multihoming by not multihoming at an IP level: What is IP's approach to everything that's hard to scale? Put it in the end node..
Today, Multihoming (an important feature for realibility) prevents signifant aggregation, thus inflating the route table.
The solution:
Give each node addresses on each of the connected networks (easy with IPv6), multihome only on a limited scale (I.e. Tell provider B about provider A's addresses, but he should not propagate it any farther), then let a next generation replacement for TCP/UDP impliment the multihoming..
Guess what, this protocol alread exists, it's called SCTP. It's already implimented for Linux, but Microsoft will likely signifantly hamper it's
adoption just like they have with IPv6.
Face it.. Cisco/Juniper/etc are the only way.
Like hell. If my (very large) ISP didn't occasionally wipe out our mission-critical connection for an hour or so, maybe I wouldn't care about multihoming. I'm not multihomed yet for budget reasons, unfortunately, but once we can afford to go that route we damn well will.
I did propose to the IPv6 group that two things in the new IP space be done. First, that a bit toggle whether this is a roaming/DHCP IP address (an opt-out system, plus additional space to indicate if you were even on earth, or in orbit, etc.), and the second, including a rough latitude and longitude for the system with the IP. It was never necessary nor possible to get an exact location for every device. Besides, everything in a rack would have the same IP.
When a pitched it then, it was quickly shot down. However, it allowed for regional routing, which is where you just sent packets to the router responsible for a major lat/lon, which then forwarded packets to things in its area. Really simple.
It also allowed you to figure out where things were coming from (if the user opted in), which meant you could redirect them to a regional mirror. As a side-effect, folks like Yahoo could actually keep all the French out of websites, since the IP would actually have some sort of location information in it.
Routing would be more efficient, and smaller, and faster. But hey, I'm just a nutcase, as the IPv6 guys said.
the fact here is that a multihomed router taking full BGP routes from their upstreams today needs atleast 256 megs of RAM and a big cpu (example cisco 7500 MINUMUM) in order to handle it..
The problem is all the recent "hey let's be a DSL provider!!" idiots that have no understanding of route summarization and addressing.. Thankfully many of these ISPs are going bankrupt now so hopefully all their /23's and /24's will be withdrawn after their lights go out.
The ISPs need GOOD engineers who can design a network in a manner that only the most aggregate route will be announced to external peers.. the biggest problem is they assign smaller blocks and then that customer gets multihomed and the original provider has to cut holes in their BGP filters in order for it to work right.
If you're going to multihome, GET YOUR OWN ADDRESSES FROM ARIN!!! Places like Verio have very Nazi-ish filtering policies and their routing tables only hit about 85,000.. While verio makes bad routing decisions, this shows an example of what the internet routing table SHOULD look like.
SUMMARIZE, SUMMARIZE, FUCK YOUR TOASTER, IT DOESN'T NEED AN IP ADDRESS!@@!#@!#
Whatever. /. has sucked since user 204.
--
"Don't trolls get tired?"
- A.P.
--
* CmdrTaco is an idiot.
"Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
--
* CmdrTaco is an idiot.
"Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
Well, isn't that what those people get paid to do?
-A.P.
--
* CmdrTaco is an idiot.
"Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
You're absolutely right that our ability to cope with the net is what's suffering. A friend of mine once said that the Internet is "like giving +1 to everyone's intelligence. If they don't know something, they now have a tool that lets them look it up and get a ton of information quickly." But now we realize that you only get the +1 bonus if you are already fairly intelligent, because it takes intelligence to be able to do Internet research, more intelligence to determine if the sites that you're looking at are good sites and/or responsible with facts.
With the wisdom of hundreds of other netters, and the net's gift of great communication, I can be more intelligent than a doctor is about a given prescription drug, for example. But if I don't select sources correctly, I can be downright dangerously ignorant about that drug.
If the tools that we have for research improve, THEN we can add +1 to everyone's intelligence. So what we have in the meantime is a tool where the smart get smarter and the dumb stay pretty much where they are.
It may be that the current economic contraction may be just what the net needs. It may stagnate in growth for a little bit -- and then we'll have a little bit of time to catch our collective breaths and allow humans to catch up with what is possible. One reason we have all these fucked companies is that the masses didn't adapt as quickly as the netted elite. The main reason is the temporarily insane marketplace, sure, but a lot of online things are much better than their offline counterparts, it's just that people couldn't catch up with the growth of the net. It's better to meet online than to travel 2000 miles to meet, but today we are still adapting to the idea that we can shop for airline tickets over the net.
The net has allowed us to see what's possible and to implement new and better approaches. But it could not hold our hand and show us the new and better approaches. With time at a premium in everyone's lives, no-one can afford the time for experimentation or learning with these new approaches.
OK, I'll stop now before I become Katz.
The result - the Internet's population CAN exceed its useful capacity. (It has, several times. I've experienced outages on international links of up to 14 days, due to catastrophic hardware overload.)
The problem is that the AVERAGE load needs to be less than 1/3 the total capacity, if you want to avoid major packet loss. However, when you look at profit-run businesses, it makes no sense to have three times the capacity you can get away with. That's just going to eat profits.
The major failure of a profit-driven IP-based network is that you hit maximum profits when you hit minimum quality of service. There's no way round that.
In the end, privatizing the Internet may turn out to be a failure. Upgrades are expensive, and the increase in revenue will typically be trivial, in comparison, making maintenance unprofitable and (in a depressed tech market) marketplace suicide. (You think shareholders'll approve a plan to "throw away money"? No matter how necessary it might be, from a quality standpoint?)
In the end, enough people just use the net for music, prawn and e-mail (none of which require speed) that the Internet could, in principle, survive off just those services.
This is why projects such as Internet 2 became popular. Researchers and Universities around the world realised that the Internet is dead for any "real" (read: "Network-Intensive") work.
The now-famous live videoconference between American and Russian hospitals, over the MBone, would not be possible today. (It was barely possible, then, with networks around the globe suffering melt-downs from the incredible demands it placed on the system.)
Today, even connecting to the MBone is a nightmare. Mail the MBone mailing list, and they'll tell you to pay over hard cash or talk your ISP into doing so. Gone are the days of trading resources, knowledge and capabilities.
The Internet will live on, but we'll see further fragmentation, as commercialization forces people to build specialized, distinct networks, which will become ever-more incompatiable.
If this is the world "we" (as the users and therefore the funding) want, then oh well. It sounds b awful, to me. But this has gone far beyond anything any individual can change. I'm not even sure it's something even large corporations can change. (Microsoft tried! And is still trying!) This may well be the scenario we're locked into, no matter what.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
And this will decrease the number of routes in the average backbone router... how?
kashani
- Why is the ninja... so deadly?
Yeah in the 2501 which was EOL'ed in 96 I believe. It was replaced by the 26xx series
sho ver
cisco 2620 (MPC860) processor
kashani
- Why is the ninja... so deadly?
True, though it doesn't do much for the existing problems. Also what happens when your downstream wants to multihome? Does he get his own /64 (heh heh) or whatever or does he announce a subset of your space? I'd vote for the former, but I haven't seen, which way their leaning.
kashani
- Why is the ninja... so deadly?
DO you have any idea what you are talking about?
We need dynamic routes so that we can actually pass traffic when links fail. Link go down, route gets dropped. Router crashes routes get dropped. Also have you ever tried to static route 100K routes?
kashani
- Why is the ninja... so deadly?
Ahem.
/32 is one IP address.
/64 is 18446744073709551616 IP addresses
with 32 bits a
with 128 bits a
- Why is the ninja... so deadly?
This is the single funniest statement I've read in days.
An unfortunate side effect of high intelligence is a remarkable lack of patience for lesser intelligences.
Thus, a routing guru may have a very good reason for dismissing your proposal out of hand, but feels that it's beneath his intellect to talk down to you in terms you can understand.
Whether this is good or not is irrelavent. It's just the way we're wired.
Personally, I think your idea has merit, but then my idea of complicated routing is getting my home and office wired together across different providers. I'm no guru.
A real guru, with the vision to see beyond your idea in totality may take the idea and run with it in a similar, if not same, direction, and come up with a great solution. I wouldn't count on it, though. I've found that really, really talented/skilled people are very, very focused on their talent/skill. Thus, as a prima donna ballerina is a great dancer but sucks at fixing your car, a routing guru may not have the right-brain capability to think outside the box of routing table rules.
"Beware by whom you are called sane."
Potato chips are a by-yourself food.
please someone Quick ORDER MORE!!! HURRY!! this internet thingi is gonna Get /. ed AGAIN!!!
(plugs holes with fingers)
hurry, im running outa fingers here!!!
To err is human, to really screw things up, you need a robot.
A lot of providers have multiple separate IP address blocks. With IPv6 every provider would have more address space than they could ever use, so they would never be assigned more than one block. Just one route per provider would help things a lot.
Benny
Finally! A year of moderation! Ready for 2019?
Cellophane factory gutted by fire. No film at 11!
"The sky is not falling, but the sky is hanging a little low."
Why is that quote funny to me?
If tits were wings it'd be flying around.
Wasn't Northpoint the first step along this route?
7 November 2006: The day Americans realized corruption and incompetence weren't addressing 11 September 2001
Computing is the only field in which we consider adding a wing to the building to be maintenance.
- "History shows again and again how nature points out the folly of men" -- Blue Oyster Cult, 'Godzilla'
For one, how many people do you know have a little bio page that basically says "I'm joe shmoe, and I do nothing special, but I feel I need a web page." I'd say about 70% of personal home pages are worthless (and that's based on a very easy rating scale).
So, as a result, the engines like Yahoo and so on are trying hard to keep up with the crap, but the crap is crap, and should remain listed as such. I think it might be better worth-while to figure out some sort of sponsor-to-create system with all sorts of checks-n-balances to keep useless websites from ever existing. That won't ever happen though, because after a few more years, the novelty of the 'net will fade, and it will become a standard part of our lives. People won't see the need to have their own website anymore, unless they really are trying to share something with the world that is worthwhile. That won't prevent the crap from piling up, but it will slow and the 'net will become stable again.
I can't wait 'til that happens.
And I find that to be content oriented.
The original poster has a valid point -- compared to contemporary PCs, many Cisco routers, for simply forwarding packets (I'm excluding specelized compression/encryption cards, which aren't likely to be used in a nationwide backbone anyway) are really weakly powered and highly priced.
Why does a Cisco router with the equivilent of an Athlon and 512MB of RAM cost $50k or more? I'm sure the I/O engine of a Cisco router is actually better designed than a PC with PCI slots full of four-port hundred megabit NICs, but has anyone ever done any test to determine just how fast such a PC could be?
Gonna collapse from all this
Gonna run out of IP addresses by 1996 or so
Is IPv6 going to help this all?
Only if we give out prefixes in a sensible manner (for some definition of sensible - country? Provider? Height of user? You decide).
This is the Good Times Virus (tm) of Routing.
They blame multihoming - however there is a limit of 65535 possible autonomous systems out there under BGP4, so if each of these has an average of 3 entries, doesn't that give a max number of route entries of under 200,000? Except you also have to multiply by the number of IP address ranges (networks and subnets) advertised by each AS - but still there would seem to be a limit not too far from where we are now. Which probably does mean it's time to replace BGP...
Energy: time to change the picture.
This isn't "Nazi-ish." This is common sense. If everyone started aggregating properly, there would be a lot less overhead.
Frankly, I think IP allocations should be yanked from people who don't know how to announce them properly.
---
click a button, feed a hungry person!
Get off my launchpad!
The internet is built in such a way that it is capable of adaptiing.
The reason that routers are slow is that there isn't enough reasonable route summarisation that is relevant to a global basis.
This will fix itself over time as the internet is built in such a way that it can adapt itself in an evolutionary fashion. Very much as open source can do the same.
Stop worrying...
Let the "corporate entities" sort it all out...
OK. We'll set it up so that everybody who wants to put up a web page asks YOU whether it's worthwhile or not. Hope you've got some spare time. What's your email address again?
Why yes, I AM a rocket scientist!
We as a community must take action to prevent this most grevious of conclusions for our beloved Internet! All sites that take less than 1,000 visitors a week should hereby relinquish their domain and IP address to The Greater Good and set up camp at either Tripod or Angelfire.
All ISP or service providers: scale back your IP ranges! Everyone with a class A group of IPs should move to class B; everyone with B to C. All service providers currently shopping for IP addresses, please purchase one (1) and set up virtual domains.
You there! with the vanity domain for IRC vhosts and email - cut that shit out! And you, with the pointlessly obscure and insipidly dull "weblog" with it's own domain - to GeoCities with your ilk!
We can save ourselves, but only through moderation! (hint, hint!)
Cheers,
levine
Except DNS is entirely unrelated to routing. have a nice day. DNS would be a problem if it sent a NOTIFY to every DNS server on earth like routing does, but that's why DNS has caching and TTL's.
Regional routing allocation. Then your router only needs to know the routes to the nearby supernets, and your own subnets, and the router upstream from you will know it's own subnets, and it's neighboring supernets, and routing is a lot more aggregated, unlike know where there's morons out there advertising /18's as 64 /24s
> IP addr's aren't sacred. They should be chosen
> for the convenience of the routers -- that's
> the idea behind Class A, B & C arrd blocks
Well they weren't. This is one of the many things IPv6 is supposed to solve... though i'm still not entirely sure that a problem even exists...
A discussion on this topic at
SEO Copywriter. Just Say ON
Hi. John Galt is a moron, is your answer. Who else would want to have anything to do with that railroad bitch? ;)
Good post, thanks. Just wanted to add - The city of Sacramento actually used to own a nuclear plant (called SMUD) but they closed it down about 11 years ago. Certain groups (including myself) warned at the time that it was an irresponsible action based on unscientific feel-good eco-politics and could eventually cause brownouts and power shortages. So you have to understand that this California Stupidity thing has been going on for over a decade now.
I live in Dallas today, thank God. It's comforting to live in a state that never voted for Bill Clinton, even once, for anything. And a state that can take care of its own power grid, thank you very much.
I have seen the future, and it is inconvenient.
IPv6 is totally non-locative? Does that conflict with the goals stated in the RFC's that are worried about "transparency"?
Either way, I don't see any guarantee one way or another on 'locative' vs. 'transparency' with IPv6. There's been only a few addressing formats specified. We may not have seen the one that gets widely adopted yet.
--
First of all, there's no such thing as "growing too fast." It grows as fast as it grows. When routers stop being able to handle it, it stops growing until technology catches up. It's a standard population cycle.
:-).
Actually standard population cycles have huge crashes where the population drops, often precipitously. Let's hope the analogy doesn't quite fit
However, more important is that it's not that more people won't be able to join the internet, it's that performace will degrade to unusable long before that.
A better analogy is probably traffic gridlock. With too many cars, nobody moves. Unfortunately, that can mean financial catastrophe as people start "giving up on the net" because it's just too slow or unreliable. As if e-commerce didn't have enough problems.
The issue is not whether the pipes are saturated, the issue is whether the routers can propagate and crunch routing information fast enough. Spam is irrelevant; the size and complexity of the Internet is.
Boss of nothin. Big deal.
Son, go get daddy's hard plastic eyes.
Expanding a vast wasteland since 1996.
Looking forward to hearing your developments!
Seriously, there was somone a year or two ago who made a vast leap in voice recognition by realizing that you need to vary the timing between firings. Now I haven't heard of any practical developments, patents, licenses, or products as a result, so it may have been bullshit, but... Given that so many years of neural net research apparently overlooked this simple variation of technique, and given that any application of this to routing technology would necessarily make use of asynchronous signals, someone like myself who has no real knowledge about neural nets at all can see that it's likely that a big chunk of the theoretical groundwork for such an application is still terra incognita. Which means that we could easily be looking at 5 years research time PLUS design, development, implementation, and deployment of an utterly new routing protocol, one which would have to speak natively to at least BGP, if not other routing protocls, and which could have mission-critical implications for every major backbone provider.
Good luck!
P.S. Don't forget to post those links when you find them!
Boss of nothin. Big deal.
Son, go get daddy's hard plastic eyes.
Expanding a vast wasteland since 1996.
Screw the banners...with broadband to the home, you can run your own server and put whatever you want on it, with the only size limit being what your hard drive can hold and without those stupid "punch the monkey" banner ads. If anything, personal pages have the potential to proliferate (say that three times quickly :-) ) to an even greater extent than before, and potentially with less meddling from The Powers That Be (assuming for a moment that they don't do something really stupid, like say that you can't host your own website on your cable-modem or DSL connection).
(FWIW, I've heard from people in other parts of the country with high-bandwidth connections that their usage of those connections is somewhat restricted. Maybe I'm lucky, as the provider I'm using doesn't seem to care much what I do with the fat pipe, as long as I don't resell bandwidth or provide warez/kiddie pr0n/etc. through whatever services I might make available. Besides, with 128 kbps upstream, it's only good for a personal site that sees maybe 10-20 hits on a good day.)
20 January 2017: the End of an Error.
That just means its time to start developing AI (neural net) networks. This way the internet technically will be able to route itself more efficiently based on a few guidelines.
No. I am clueless :) But even I didn't say we don't need dynamic routes.
I asked why we need _heavily_ dynamic routes that build deep routing tables. Sounds to me like someone is abusing the tables. Or using multi-homes as pass-thrus.
Is it because somebody wants 69.69.69.69 to be on one end of the Continent and 69.69.69.99 to be on the other? Why? I'd be sorely tempted to screw'em. Drop 69.69.69.99's packets on the floor if it's away from the rest of it's C class.
IP addr's aren't sacred. They should be chosen for the convenience of the routers -- that's the idea behind Class A, B & C arrd blocks. If AOL wants to use a US IP addr for *.de traffic, fine, just drop the packet in the US and let'em route it themselves.
When a system is taxed, somebody will suffer. It shouldn't be those who follow the rules. Otherwise, nobody will follow the rules and it will get much worse.
...after a few more years, the novelty of the 'net will fade, and it will become a standard part of our lives. People won't see the need to have their own website anymore, unless they really are trying to share something with the world that is worthwhile.
:-)
No offense, but bullshit. Did the novelty of the Polaroid fade? Are the only people who have an interest in photography these days folks like Ansel and Maplethorpe? No! Now we have disposable cameras and sticky film.
Personal pages will be around as long as somebody's giving away free hosting in exchange for ad banners... Now if you want to debate the certain death of the ad banner, that's different.
"Smear'd with gumms of glutenous heat, I touch..." - Comus, John Milton
The House Between - Original Sci-Fi Series
(Sorry, couldn't resist)
Wah!
This was posted on NANOG this morning and should be required reading. It is from Sean Doran who basically built Sprint's Network in the early/mid 90s and is probably *the* authority on this kind of stuff. Read it.
The problem is with the routing tables being filled. Therefore, if you want to use the oh-so-lame "OSI Model", the problem is layer 3, while what you're talking about, HTTP, is layer 7.
-bugg
OK reality check here -- how does email traffic have ANYTHING to do with the size of routing tables? (Hint: It doesn't have anything to do with it). This article isn't talking about traffic its talking about the size of hte routing tables.
And what commision is it that is planning to "delete spammers from the internet"? I hope they don't delete me.
Troll...........
If the current infrastructure is not up to the traffic then the parts of it that are too weak need to be redone. It is pointless to cry that it is being used too heavily and even more pointless and abhorrent to talk of attempting to slow it down.
we get an article like this every few months, and the net still seems to be up... don't u get bored of reading the same over and over?
---
Thats not the point. I shouldn't have to qualify what I am going to use it for, if it's available it should be available to all.
Sigs are awesome huh?
I see everyone blaming the small multihomed sites and talk about banning multihoming on this forum, I strongly disagree with that and I strongly disatree this nasty quote from the article:
"Half of the companies that are multihomed should have gotten better service from their providers," says Patrik Faltstrom, a Cisco engineer and co-chair of the IETF's Applications Area. "ISPs haven't done a good enough job explaining to their customers that they don't need to multihome."
Yeah sure, my provider told me how I didn't need to multi-home and I got burned. Excuse me for stamping on your elitism here, but everybody wants redundancy and you shouldn't have to be a fortune 500 to get it.
About a year and a half ago our company was looking into upgrading bandwidth, and since we already had a t1 my boss figured we could buy another t1 one from a different company than our normal bandwidth provider, thus achieving increased speed redundancy with a different isp at the same time.
Well I found out that in order to do something like that I needed to run BGP to get myself into the core routers routing table because I would have multiple paths to my network. I was a big concerned about this because it sounded drastic to me and I spoke with my tech rep at my current provider and we mutually agreed that perhaps it wasn't the best thing to do as we could get redundnacy from their network and I wouldn't need to have my own AS.
Well, to make a long story not quite as long, I got burned. They had some routing problems that affected both of my links at once, and we were down for a bit. I had to explain to the boss why I had made the decision I did and he wasn't real happy about it. I am about to be installing our 3rd t1 and switching to bgp so we can be multihomed.
This is a very typical story, and is the primary reason that the BGP4 tables are so huge. Every dotcom and their mom has been going through a similar scenario the past year or so. Now of course this is starting to not work very well so we are seeing some problems, and these same dotcoms are being blamed for this.
The problem isn't the dotcom's, its due to limitations in the current system. I suppose they (we) do shoulder some of the blame, but christ shouldn't we be allowed to have some kind redundancy? What is there some kind of special "VIP's only" sign in front of the redundancy bar? To hell with that. Obvously the current situation cannot continue, but I'll tell you right now that all of these dotcom's (and their moms) are not going to be giving up redundancy, so you core router guys better figure out why to let everyone in on the redundancy bandwagon.
Sigs are awesome huh?
Meanwhile, places like Extreme offer more GigE ports than you could ever imagine using and at a much more reasonable price. Cisco has a stronghold on the market indeed.
I've worked with Extreme's switches. They're good. Simple, WICKED fast, and more cost-effective than Cisco.
My only beef is that if you want to use them as core routers, you've got to be running Ethernet. No ATM interfaces. No T1 interfaces, no DS3 intercaces, no OC3/12/96 interfaces. So you've still got to hang other vendors' boxes off the mess and you risk vendors fingerpointing when something chokes.
It's kind of a catch-22. Cisco's mature, but almost too much so, which all sorts of useless legacy equipment in their product line that they have to support and legacy code in the IOS kernel. Extreme needs to become more mature, I kind of feel their software needs some fleshing out yet and they need to add some components to their product line.
I love that crazy fast backplane on the BlackDiamonds, but for chrissake can't we do something about the purple and green color scheme?
-carl
. We've got computers, we're tapping phone lines, you know that ain't allowed - Talking Heads, "Life During Wartime"
Actually, I'm pretty sure that Cisco's 2500-series routers to have m68k processors. 68030, I believe. Everything never has a PowerPC variant. Dunno about Juniper, but I'm going to guess they're running a RISC processor of some sort.
The hardware issue was another factor covered by NANOG this morning in response to this article. The long and the short of is that throwing hardware at a problem might get you through the day, but good planning and forethought will bring you through a lot more cleanly.
With any router manufacturer, your value-added is never the hardware but rather the software (i.e. Cisco's IOS) and the service. Sure, you could grab a PII and run GNU Zebra for your BGP peering, but the CCO is a great resource to have when troubleshooting. Puts MS's TechNotes system to shame. It WORKS. Plus, working in downtown Chicago I know that if my 7200 takes a dive, Cisco's got a parts depot blocks away where I can get parts.
-carl. We've got computers, we're tapping phone lines, you know that ain't allowed - Talking Heads, "Life During Wartime"
I looked around a little but couldn't find what I'm looking for -- some introductory text that describes the current Internet routing system and the state-of-the-art with respect to it? There's a lot of stuff being thrown around here that I have little to no knowledge of, even though I'm a fairly proficient geek. Can someone point me in the right direction?
"Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
As one of the replies to your post pointed out, a lot of these jillion pages (the vast majority of homepages, anyway) are crap. Personal crap. Yes, they're sitting on a web that's supposed to be interconnected, but for these personal pages there's no need - they exist simply so their owners can tell a friend or relative, "hey, go check it out, it's got my dog's picture on it."
This majority of personal pages should be ignored by search engines simply because there is nothing to search for in them - typing "Cindy" into google when looking for your cousin's homepage wouldn't be much use no matter how many times google's been to her site.
---
If you're curious, have a look at this. It's a summary of the size of the Internet routing tables over the last few years. See a pattern?
Well, I certainly don't think that NNTP is putting a strain on any routers...
Got Rhinos?
Second of all, a greater concern might be "Is the Internet growing too disorganized?" There are ten jillion pages out there, and the vast majority of them aren't even linked to from other documents. They don't show up on search engines, they just sit there, with the web masters wondering why they've only gotten 3 visits in the past year.
Even the sites that can be found by search engines are getting increasingly hard to organize. Yahoo! is starting to wobble in their traditional high-quality, hand-picked links directory. They can't keep up with the net, so they've started implementing pay-for-listing programs. The Open Directory Project survives because of heaps and heaps of volunteer editors, but every category varies in qualities, and some basic categories don't even have editors. Many other search engines have attempted dynamically-created directories based on keywords, but these are easy to spam and often have very low-quality content.
All the disorganization also affects our information processing skills. We don't read like we used to. Hardcore web surfers are generally incapable of sitting down and enjoying a good book, because they're too accustomed to the "This page doesn't have it, go to the next one" cognitive paradigm.
What we really need is a new way to organize web sites, perhaps based on a combination of client (most visited sites), server (author-specified categories), and parsed (most linked-to sites) information.
The internet is not growing too fast. Our ability to cope with it, however, is failing to grow with it.
Got Rhinos?
Having been in the military, college, work, etc.. for the last 13 years I've travelled to a lot of places. I have found people again through their "worthless" sites that have been indexed.
t
Acording to the aticle the problem isn't with the amount of user traffic on the internet, it is with the amount of router-to-router traffic. The routing tables are being updated too quickly for the routers to handle and pass the changes onto other routers. As the number or routing entries an updates grow, because of multi-homed systems, the system can't keep up with the changes. At least thats the impression I got from the article, please tell me if i'm wrong.\ =\=\=\=\
=\=\=\=\=\=\=\=\=\=\=\=\=\=\=\=\=\=\=\=\=
Only two of the list of vendors, Cisco and Juniper, have bulletproof and fast enough BGP implementations to survive the net. In fact, Foundry admits that their bigiron products aren't up to the challenge of the Internet core.
K
Lord, don't even joke about this - they might do it...
And in this situation, this would actually put a much worse load on the operating routers that have to recalculate routing tables for flapping and downed routes.
----------
ah honey, we're all resplendent - Bill Mallonee
blah, i wish i had a megabyte of memory for every 'chicken little' technology complaint. email, napster, virii, routers, shez...
A Bugg
The same is true of telephone numbers. Originally, the area code addressed an area, the exchange prefix addressed a specific switch, and switches didn't need much routing info. Today, two adjacent phones can have completely different area codes and exchange prefixes, and most phone calls involve a database lookup to get routing info for the call. The internal architecture of the phone system has changed completely in the last twenty years to make this possible.
The Internet is going through the same transition. The endpoint is probably IPv6, totally non-locative addresses, a lookup for every routing decision, and a hierarchical cache of a distrbiuted database system for the routing info, somewhat like DNS. But we're not there yet. The existing technology was designed for a network with a hierachical address structure, so that the routers only needed to track class A, B and C networks. Now they're expected to track more finely divided portions of the IP address space, requiring more router info. BGP is hard-pressed to keep up.
I looked at this problem once in the 1980s, and concluded that part of the solution was a strong separation between information about actual topology (what nodes and links actually exist) and network status (which nodes and links are up). The former changes more slowly than the latter, and contains more data. The link state info changes more rapidly, but the data volume per link is small. Such a separation helps you get a handle on the data volume.
It also makes the network more robust, because you can afford to do more checking on topology data. You'd like to verify that both ends of a link agree on a link before putting it into the topology, for example. That is, before anybody accepts a link between A and B, they need to see A saying it has a link to B and B saying it has a link to A, preferably with digital signatures. I was trying to devise a routing protocol for DoD that would resist attacks on the network in the form of bad routing data. But we didn't get the contract to build that, so I went on to other things. Whomever gets stuck with replacing BGP needs to solve that problem.
But I did this before mobile IP was an issue, and never had to deal with that very difficult problem.
First of all, yeah, that is what they get paid to do. . . I guess I'm kind of a jerk before my morning coffee. Sorry.
What gets me is that this is the second or third flip comment I've made in the past few weeks that has been moderated beyond all reason. It's a little embarrassing.
Any sufficiently well-organized community is indistinguishable from Government.
Ignore this shit. Every year, someone predicts the internet will "collapse under its own weight". Guess what? It NEVER DOES. People have been claiming the sky is falling since NSFnet became available to the public -- I'm still waiting.
I think you misspelled "Feel free to sit back on your lazy ass while somebody else designs and implements a fix - just like they always do". HTH. HAND.
Any sufficiently well-organized community is indistinguishable from Government.
So we have your arguments for, what were the arguments against? "You're a nutcase" shouldn't stand up to peer review, ya know?
Peace,
Amit
ICQ 77863057
[o]_O
There is also some very interesting information regarding IPv6 in various sites, such as 6BONE's, and Sun's. It is really great to poke around with IPv6 stuff, there are a lot of programs that support it by now, such as lynx (-dev tree only), w3m, BitchX, epic, etc. etc. etc. And also, IPv6 is cool because it lets you create such educational hosts like dead:beef:c0ff:eeca:bf00:3:133:7.
If you don't believe me, here is my sit1 interface:
You're tired of Slashdot ads? Get junkbuster now!
Junipers run Mobile PII as their main processor. The JunOS is actually FreeBSD based and is quite happy on that processor since it just runs the chassis and coordinates the efforts of all the Interface cards. The interface cards all have a highly specialized ASIC in control that actually handles the routing. That's why Junipers are so much faster then Ciscos. Ciscos also use ASICs but just for packetpushing. The main processor also handles the main part of the work.
A good analogy is that Junipers are more like Beowolf clusters and Ciscos are Xterms connected to a Cray.
The faster the Internet grows, the more AOL-free content is created. I say strain those routers. Upgrades are inevitable anyway, I mean, we're called nerds for a reason. ;-)
>An unfortunate side effect of high intelligence >is a remarkable lack of patience for lesser intelligences.
Thats not a side effect of high intelligence, thats a side effect of arrogance. A quality, that is all too evident in people who think that they have high intellect and that is all that they have. Personally I don't see what is so wrong with the idea and feel that if your (not you, but anyone) is going to shoot something down, at least provide a reason for it.
-- Its survival of the fittest...and we got the fucking guns!!!
Cisco isn't the best/biggest due to their hardware.... software-software-software. -JPJ
Feh.
"
Utilities such as: Gas, Electric, Water, Internet Access, should be GOVERNMENT regulated and provided. "
"
YES!! more socialism! while we're at it cars, computers, televisions, steak tar tar and beer should also be provided by the government.
"
I think the argument is infrastructure should be built and maintained by the government, otherwise you'd need multiple gas supplies to your house for competition. The idea is only one set of power lines needs to be built to your house, rather than one per electricity company.
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. (Einstein)
(I'm off-topic, but I don't care.)
This Slashdot story reminds me of the restaurants nobody goes to because they are too crowded.
Most routers contain only motorola 68k processors which seems absurd for the price that routers go for. The reason for cisco's slipping stock shares may be partly due to lack of innovation. Just as Microsoft has a strong hold on the OS market, cisco has a stronghold on the router market. There are only a few competitors (Marconi being one of them) so now cisco can charge highly inflated prices for a piece of hardware that was used in a macintosh from 10 years ago that you can buy on eBay for 10 dollars. We need cheaper routers that are faster and router makers would still be able to make a killing on routers if they charged half the price.
Yeap, seen this too many times to be funny: Network managers, when you make a change to the networks you advertise or your filters, use "clear ip bgp * soft out"! Without the soft out, all your routes get withdrawn and then re-added around a minute later, crating a mini route wave through the Internet. Instead of forcefully resetting your peers, soft out will just add to the table version without withdrawing routes. You could also use "soft in" for applying filters to incoming routes also BUT watch out for memory useage with this command. Soft out doesn't have this issue.
This is fairly basic Cisco IOS stuff but I've seen network admins from 2 of the top ISPs do this on peering point routers that were advertising a lot of routes to a lot of peers.
A journey of a thousand miles starts with a brutal anal raping at airport security
Get it right! As many old Usenetters know, the proper warning is:
IMMINENT DEATH OF THE NET PREDICTED!
Anyone else remember the infamous Green Card Lottery spam and the original MAKE.MONEY.FAST post? :)
(no message, sorry)
steve
--- rapper/producer/bachelorette party stripper
- Replace HD with flash disk
- Under-clock processor to where only heatsink is needed
Not too hard, eh? And now you have the same thing as a Cisco, just a case fan or two moving. For those really worried, redundant power supplies are nice too.I can't be karma whoring - I've already hit 50!
SIG: HUP
. . .
If routing tables are indexed search times only grow at log(n) where n is the search time. Memory is cheap would a gig of memory in a device be a bad thing? A standard desktop machine currently has 128M. This will give the ability to accomodate a couple of order of magnitude more routes in the routing table easily. If we go down the road of geographically based routing governments will finally have a throat to squeeze and will be as happy as a dog with two dicks and the real power of the internet will have been destroyed. Enable security but don't weaken the architecture.
I've heard this story I don't know how many times now. I first heard it back in '95 when I was first "getting on the Internet (tm)." Back before AOL had AOL France, AOL Germany, AOL Pakistan, AOL Some other not AMERICA ONLINE country. And also before AOL had 4397298732197211927432 customers. But not only has AOL expanded their network, every other site has also!! Could it be that despite all this stupid FUD things will continue to work the way they always have? For proof, see Y2K. Thank you, and good night. [mrzer0]
You better stand back, I'm not sure how big this thing will get!
Then /. would have to switch off the lameness filter once and for all.
To avoid a complete meltdown of the Internet, President G.W. Bush has recommended that rolling blankouts begin within the next two months. During peak periods of Internet traffic, up to 100,000 sites may have their routing tables blanked for up to an hour in order to reduce the load on the system.
"I may not know much about the Internet, but I don't think you need a PhD to see what all this free music trading is doing to our nation supply of routing tables," Bush was quoted as saying. Asked if he was implying that Napster was responsible for the rolling blankouts, he replied "The RIAA says they are, so it must be true."
I agree that the redundency isn't needed, but we should take it to it's lowest common factor. In cases like this there should be only one set of wires, one set of pipes, etc. That doesn't mean that there is only one company that runs electric or gas across it. That would be like having The interstate highway system and only allowing one trucking compnay and one bus company to operaate on it and one make of car to use it.
Plus the competion on power can come not just from two electrical companies, but an electrical company and a gas company, then toss in a compnay doing alternative power, solar and wind (and maybe one day fuel cells) and you've got competion, with only one set of wires and pipes.
In a time when peoeple are looking for more and more things to be privatized, putting these service under direct governemt control is a bad idea. Leave the utility commisions and other oversite bodies in place and let private companies run the business.
feel better now?
"DeRegulation and Commercialization of basic utilities was the dumbest idea ever invented.
"Okay what did it help? Not a blithering thing, okay so some jackass in idaho saved $2.95 on his gas bill, which of course is more important then the 14 BILLION dollar debt the California utilities are suffering. "
No, the dumbest idea ever was calling the removal wholesale cost restrictions and keeping consumer charges fixed, deregulation. Lets open the backend to market fluctation and not allow the front end to respond. hmmm that's smart.
By the way, that was Cali's deregulation and had nothing to do with Idaho, Washington, Arizona, Colorado or any other state. If you'r going to deregulate, do it right an open the whole thing to the market.
"De-Regulation was an idea pushed through by greedy assholes trying to convince you it was a good idea while they were planning to run with the profits even more then when they abused the government contracts. "
Uhh huh... Price fixing is a great way to promote greed. Let's charge the customer less then it costs us to provide a power and make a HUGE profit. Then we'll be Billions of dollars of debt and richer the Bill Gates.
"Utilities such as: Gas, Electric, Water, Internet Access, should be GOVERNMENT regulated and provided. "
YES!! more socialism! while we're at it cars, computers, televisions, steak tar tar and beer should also be provided by the government.
"Oh no not that evil government???? I'm sorry but some shit has to be done by the big guys, because they're the only ones not trying to make a buck in fact they loose money constantly."
Ha they don't need to make money, they just spend it and take more from you. So lets give this stuff to people for whom cost is no major impedment, and they still buy form the lowest bidder. Making a buck can be a good thing. It means you provided a good or service for less then people were willing to pay for it.
"Nobody in Cali is building a new Nuclear Plant or Spending billions on alternative energy resources research. "
Damn Right! and that's the problem. If they want the power they've got to generate it somehow. If They don't want a nuclear plant in thier backyard, maybe they can pay the folks in Idaho a few billion dollars to have it in their's. I'm sure the guy in Idaho wouldn't mind getting free power and a check every month from the residents of Cali for that reactor a few miles from his house. OF course maybe Sacremento will realize they can get in on some of that cash down in silicon valley if they are willing to build a reactor or two an d charge a market rate to the folks in the Bay Area.
"Think about shit before you blindly go saying ..."
No comment... :)
"Also why can't we get Clinton back? I don't care who sucks his dick just that he doesn't f up my economy like bush or gore will)"
Well a constitutional Amendment for one thing. Durring who's adminstration did this start? So we see his results, but we'll make Bush or Gore guilty even before they can commit the crime, good.
This reminds me of something I read once...
Who is John Galt?
While I would prefer some sort of international standards body that could force people to do things the right way instead of half way, without some sort of enforcing power, that is difficult.
Man, I can't believe I just advocated Anything for the government...on /. no less..I better go lie down.
Someone needs to revamp the current DNS system. It's rather a pain in the ass, slow, and really wouldn't be terribly hard to make a lot more efficient...
Ryan
"All your base are belong to this file I send in order to have your advice."
Quick! Don't wast anymore time! You remember the Y2K Crises! Well, now here's your chance! Join the Computer Academy today and become a "Routing Table Update Specialist"! In just 6 short months you can have a fun, full-filling, and challenging career while driving down the salaries of people who genuinly love what they do! Don't hesitate! Without your help the internet will collapse! Blah, blah, blah! Sounds like hogwash to me.
It would be so much less burden on the transatlantic links, and all the routers between me and /. if i could get the info from whoever has just read it in my town, or even street. You could solve all the bandwidth problems by sharing it out.
Sure you could, right up until you figure in all the traffic overhead necessary to determine whether or not a more local source has cached the article, which source of the cached article is closer to your current location, whether or not the data has been tampered with, and then finally transfer it to you. OK, sure, it's let's traffic on the transatlantic cables, but it doesn't make your access any faster.
And why are we discussing bandwidth issues when the topic is routing tables?
Surely, Al Gore's original design included instructions for dealing with this eventuality.
It is probably that Gore, still smarting from the recent lost election, is feeling spiteful and will not release the information that will save us from Internet meltdown.
I suggest that we send an ambassador of good will, an individual of the highest merit and integrity (CmdrTaco?) to meet with the now secluded Gore, and plead for our salvation.
Like what certain specific sites? Like your "watch me take off my shirt and program html" site? You got into that business about five years too late. Sorry, but I can't bring myself to have sympathy for a smut site operator who complains about the rest of the net treating her unfairly.
I guess it's too bad that you can't just use your breasts to make money on the 'net without any initial investment, but even the world's oldest profession requires you to spend money to make it.
"Smart Growth" for the internet? Screw 'em!
You are correct. According to the article, it is the router-to-router and multihoming (sp?) traffic that is causing the problem.
m .html
But I have to ask the question: does router-to-router notification travel along the same pipes as e-mail and any other net traffic.
According to this research done in 1997 - 1998 spam traffic was anywhere from:
2% on pure ISP?s
10% on some corporate domains
and up to 50% on AOL
the link for this info is http://www.research.att.com/~lorrie/pubs/spam/spa
So, if reductions of the Spam traffic happen there might be an increase of communication speed between routers.
ONEPOINT
spambait e-mail
my web site artistcorner.tv hip-hop news
please help me make it better
if you see me, smile and say hello.
Thank you. I was not sure.
:)
I thought that the transmission of the routing information was the slow part. But re-reading the information I can understand a bit better that the problem is at the routers themselves and the lack of speed at the routers
ONEPOINT
spambait e-mail
my web site artistcorner.tv hip-hop news
please help me make it better
if you see me, smile and say hello.
A little bit of burping in the infinitely scalable architecture, eh?
I am for the complete Trantorization of Earth.
According to this post it's not growing fast enough...
Your pizza just the way you ought to have it.
I realize that the problem here is with the size of the routing tables. But with optical routers getting nearer and nearer to mainstream, it seems like this should give us some cushion for growth. If a packet can get through a router at the speed of light, it should give the router more time to do table lookups and that sort of thing. Not to mention the fact that processors for routers will keep getting faster. Anyone have thoughts on the role that optical routers could play in this issue?
So, what's the theorical limit? There's WHY worrY?
Google, on the other hand, encourages success from sites that are good, rather than sites that are well-financed. Being well-financed will always help, but Google ultimately places the most weight on sites that get referenced frequently, instead of sites that can afford to take out a $600 yellow page ad. That is the sort of new innovation in web organization that I think will have a big impact on how we find information in the future.
-Keslin, the naked nerd girl
-Keslin, the naked nerd girl
Immenent Death of the 'Net Predicted! Bring out your dead!
I for one welcome our new SCOviet Russian overlords to whom all our base are belong.
Oh great... back to ascii porn
"Internet dying"... "movie at eleven"... blah blah blah
1-ply is for the real men and poor carpenters of the Earth
~ jon
This is just another example of Moore's Law taking it's toll. (And why sometimes it may not be all that it's cracked up to be.)
Take comfort in your ignorance.
__________________________________________
__________________________________________
Take comfort in your ignorance.
Grandmaster Plague
You blame whoever you don't like. For me that would be:
MPAA
RIAA
Micro$oft
spammers
virus writers
"the fax machine is nothing but a waffle iron with a phone attached to it." - Grandpa Simpson
My personal opinion on this problem, is the control that the content providers have on this system is too much. Freenet seems to solve this by getting your data from the nearest source, just like mirrors are supposed to. If every home dial-up user contributes to the serving of files, then the problem is reduced. Obviously the encryption in Freenet slows it down, and this should be removed, a publisher should have to submit the content to this system, but would benefit us all if they do. For example i live in the UK, and im sure many other /. readers do. It would be so much less burden on the transatlantic links, and all the routers between me and /. if i could get the info from whoever has just read it in my town, or even street. You could solve all the bandwidth problems by sharing it out.
Yes, blaming spammers is silly. And more important than "who do we blame" is "how do we fix it?"
If the internet is really growing too fast for the routers to handle, disaster could be looming for e-commerce and the economy in general. Perhaps major world governments will have to step in to address the situation.
But what could they do? Maybe they could subsidize improvement of the internet backbone, but that might be too little too late.
Perhaps instead it would be helpful for governments to start rationing bandwidth, and soon. Bandwidth could be allotted to people and industries on the basis of need. That would help ward off an internet "meltdown," while making sure that people who really need bandwidth have access to it.
But that solution might be difficult to implement in a timely manner. Alternatively, a tax on bandwidth might be ideal. It would discourage wasteful use of bandwidth, while remaining practical to implement through existing tax collecting agencies. Those people in (say) the bottom third of income-earners could be exempted from the tax, so that we don't increase the gap between the information haves and have-nots.
from the article: To tackle these questions of how best to revamp BGP4, the IETF has launched a new effort called Prefix Taxonomy Ongoing Measurement and Inter Network Experiment (Ptomaine). From WordNet (r) 1.6 [wn]: ptomaine n 1: any of various amines (such as putrescine or cadaverine) formed by the action of putrefactive bacteria [syn: {ptomain}] 2: illness caused by poisonous or contaminated food [syn: {food poisoning}, {gastrointestinal disorder}, {ptomaine poisoning}]
--------------------------------
Berk Watkins
Yes, the people that are paid to engineer the Internet will solve the technical issue, and as always the gloomy predictions ala Metcalfe, will probably be proved wrong.
Remember when the backbones were 56 Kbps (before 1988) and it was unthinkable to some people it won't collapse? Remember the T1 backbones until 1991, when Internet was doomed to be charged by volume?
Nowadays I have 1-5 Mbps download connection to major sites. Bandwidth is no longer a big issue? Now predictions are about explosions/wild changes of route tables (to be fair, this has been started a long time ago, along with with IPv4 unconceivably too small address space).
I would argue that making your component geographic would not be good, and does not address the core issues with routing. You assume that just because two routers are geographically closer that there exists a 'regional' path between the two, but this is not always the case. It really depends on the TOPOLOGY of the network. Again, the question of how distance is defined becomes key; which is better--distance defined by physical distance, or distance defined by speed to reach the location? Another problem with physical distance (besides ignoring line speed) is that geographic distance is not a real reflection of the actual cable distance (it's never a straight line).
However, trying to keep the traffic within the same region does have merit (region being defined by the topology/network architecture, rather than pure geography), and I would agree with you that this need exists. However, there are mechanisms/theories that have been developed in attempt to address this issue. Rather than re-inventing the wheel, we should look at how these past attempts address the issue, and the problems they encounter.
Some past attempts mechanisms that I'm aware of include:
N.E.T.'s SuperWAN feature for the IDNX (TDM switch). Part of its purpose was to expand the node limitation, but it also kept circuits within a defined domain, and allowed circuits to cross domains only when necessary. A transit domain could be defined by the user to bridge two domains together that were not directly connected.
StrataCom (now Cisco) Domains (ATM switch). It also expanded the node limit. It is similar in concept to N.E.T.'s SuperWAN. I believe it is no longer supported--but I'm not current with their feature sets (I think they were moving towards PNNI).
Ascend (now Lucent) OSPF Area (ATM switch). Terminology has changed from Domains to Areas, but the basic concept for routing remains the same: connections remain within the area, unless the destination is outside the area.
PNNI Peer Groups (ATM). This is supposed to be a more scalable approach to the same concept: keep your traffic within your peer group unless the destination is somewhere outside your peer group.
One thing you will notice with all these methods is that the area must be defined by the user, and is always influenced by the topology of the network. Switches are assigned areas and are only connected to other switches of the same areas. Areas are connected to other areas by a gateway (in most cases, it is a 'special' switch designated as a gateway). But notice that routing metrics are not applied to keep traffic within the area. Metrics are used to determine 'optimal' pathing.
Adding geographic coordinates are not necessary to address the issue because it should be addressed in architecting the network. The only real contribution geographic coordinates add is as a distance metric--but this already exists (it's in place, and in use--the problem is, is it 'correctly' being used?). Lastly, allowing geographic coordinates adds an additional complexity to router configuration, opening one more door to user error and compliance.
On the subject of network performance, there are 3 major places to look to see where network performance fails:
1. Capacity. There is not enough bandwidth to carry the traffic (ie. my pipes are not big enough). Just because you have big pipes and a lot of pipes does not mean you put the pipes in the right places (a major problem for most ISP's & carriers).
2. Queue. Because your pipes aren't big enough, the traffic must sit wait in a buffer before it has its turn to be sent out over the pipe. Adding more buffer to the queue reduces your packet drops by making your queue bigger--it does not make things get out faster.
3. CPU. Your switch can't handle all the lookups or route calculations or some sort of process. Because it's so bogged, it can't process or switch the packets fast enough. What can you do here? You are limited to the switch you bought.
Most IP-based networks focus on Queue and CPU. The table-lookups and DNS issues are more of a scalability problem, rather than a traffic issue (having too many nodes in the network vs. carrying too much traffic). Most traffic congestion for IP-based networks focuses on better queuing methods (ie. get the more important traffic out first). What is lacking for a vast majority of IP-based networks is the lack of optimization for CAPACITY. Remember, queue only kicks in when capacity runs out. If networks did a good job of placing enough bandwidth in the right places, then queuing would be minimized (example: TDM switches always guarantees capacity (100%), so there is no need for a queue. ATM & Frame Relay 'share' capacity, so a queue is needed when traffic begins to compete for space).
So why don't most networks optimize their capacity? In order to plan for capacity, you need a good idea what your traffic flows are (end-to-end traffic flows. link usage is not good enough). Most network administrators have no clue what their traffic flows actually are, because they are dynamic, very hard to guess, and there are very few good tools out there that can collect this type of information. Most tools on the market simulate queuing, but the traffic generated in the simulation are just guesses (read: no guarantee they mimic real life, much less your network), and this does not address the issue of capacity. Capacity planning tools exist, but they are few, and even fewer work as promised. Cisco is currently working with one company to provide capacity planning tools to IP-based networks, which has promise because it has the ability to extract traffic and network data from the live network. Still, for some reason, most router people are focused on queuing rather than capacity in order to improve performance.
I'm not a router expert, but...
Routing uses the process of receiving a packet and checking its destination. Using a table lookup based on the destination, it finds the the neighboring router it should forward the packet to. The table is updated so that routing can find 'the shortest path.' The real question here is how 'shortest' or distance is defined.
Your method of configuring geographic location on routers is basically trying to get the router to calculate its distance to its neighbors. However, you're thinking about geographic distance rather than logical topology which is the 'road map' that routers can travel on. There are two direct problems that stem from your method:
1. Pipe size (bandwidth) is not accounted for. If there exists two paths to the destination, should I take the 'geographically' shorter path that is connected by a 56K line, or a slightly longer path that consists of several OC3's?
2. Hop count is not weighed. With two paths, the geographically shorter path may travel through 20 routers, where a longer path may hop through 5 routers--how do you determine the tradeoffs?
Most importantly, routers currently have a mechanism to address this routing issue by allowing users to define the distance between routers. I believe this is usually set to reflect bandwidth size (ie. usually people define their OC3's to be shorter than their T1's). This is generally easier for network managers to adjust their link distances than to tweak their lat/lon coordinates.
Most of the problems with congestion I've seen is due to capacity problems--where there may be two different paths to a destination, but one path is over-utilized and another is under-utilized. Currently, routers are very limited in their load-balancing techniques. I believe Cisco routers can balance up to 6 equal paths--but configuring multiple 'equal' paths is not easy for a meshed network (equal as in defined distance). Without equal paths, routers generally send their packets down the 'shortest' path, regardless of congestion. Routers are not intelligent enough to recognize congestion and calculate the 'next shortest path' (though 'next-shortest' paths are done when there is a link failure). Without this type of mechanism, if you were to get the router to use the 'path of least resistence,' it would just shift the congestion from the previous route to your newly defined route. Currently, the MPLS initiative is trying to address this capacity issue.