Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

'Selfish Routing' Slows the Internet

Posted by michael on Fri Feb 14, 2003 04:06 PM
from the love-thy-neighboring-router dept.
Smaz writes "Science Blog reports that a little love could speed things up on the Net. "Self-interest can deplete a common resource. It seems this also applies to the Internet and other computer networks, which are slowed by those who hurry the most. Fortunately, say computer scientists at Cornell University in Ithaca, N.Y. , there is a limit to how bad the slowdown can get. And after developing tools to measure how much the performance of a particular network suffers, they say, the way to get improved performance on the Internet is the same as the way to maintain air and water quality: altruism helps."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by Anonymous Coward on Friday February 14 2003, @04:08PM (#5305256)
    If you've got to rely on the goodwill of others to get by, you're totally screwed.
  • by Qinopio (602437) on Friday February 14 2003, @04:09PM (#5305257) Homepage
    another resource depleting mechanism known as "Slashdotting"
  • by creative_name (459764) <pauls@ou.eFORTRANdu minus language> on Friday February 14 2003, @04:15PM (#5305312)
    ...that this isn't the guys at Cornell just trying to capture more bandwidth for themselves? Seems like a good idea to me.

    Me: Don't use as much bandwidth and everyone will go faster!
    World: Hey! That seems like a good idea.
    Me: (aside) Mwuhahahaha
  • by Florian Weimer (88405) <fw@deneb.enyo.de> on Friday February 14 2003, @04:15PM (#5305316) Homepage
    Reasearch networks are particular well at this sports: For example, the German Research Network (DFN) has a strict anti-peering policy. GÉANT, a European research network, appears to accepts only links to a single research network operator in each member country.

    Of course, the most important aspect of such networks is that the bandwidth they offer is helpful in Dick Size Wars at supercomputing conferences, so it's not a terribly loss for the Internet at large.
  • by hackwrench (573697) <hackwrench@hotmail.com> on Friday February 14 2003, @04:15PM (#5305317) Homepage Journal
    Somehow the only conclusion I could draw from the article is that using the network slows it down. Right, so could somebody explain what the article is trying to say?
    • Re:I'm confused (Score:3, Interesting)

      How does this get modded insightful?

      The article is not saying that using the Internet slows it down (that much is obvious). It's saying that with different routing techniques and the same level of use, it could go faster. So, using it slows it down, but so does building a bad infrastructure for it.
      • Re:I'm confused (Score:5, Insightful)

        by zackbar (649913) on Friday February 14 2003, @04:46PM (#5305590)
        I'm confused too.

        The article states that computers test the routes, and pick the least congested route to use. Thus, it slows everything down for everyone.

        What should it do? Pick the MOST congested route?

        Either I'm just confused, the author didn't understand the situation correctly, or the whole thing is BS.
          • Re:I'm confused too! (Score:5, Informative)

            by Zork the Almighty (599344) on Friday February 14 2003, @06:08PM (#5306110) Journal
            Actually, just think about it from a larger perspective. There are many independent routers out there, and they each decide how to route their traffic simultaneously. Now, imagine that the least congested path (#1) is only slightly better than other potential paths. The problem is that _everyone makes the same decision_ and chooses this one path for their traffic. The result is congestion on the one popular path everyone chose. If that was the only effect, nobody would really care - but here's the catch : at the next time interval the same thing is likely to happen again! Everyone chooses #2 on the list, since #1 is now toast. They all crash into each other.

            At the same time, I don't see how their suggestion really helps things that much. If everyone uses the same deterministic algorithm to choose a path, this sort of mass collision is still likely to happen (although it should happen less often with more complicated algorithms). I think that overall network performance would benefit from a little randomness in the routing algorithms. I'm not a CS, so there is probably already a random component that I don't know about.
          • Re:I'm confused too! (Score:4, Interesting)

            by JWSmythe (446288) <(jwsmythe) (at) (jwsmythe.com)> on Friday February 14 2003, @09:00PM (#5306894) Homepage Journal
            Good.. I was thinking we're idiots too.. Either that, or I need to start routing all my traffic down the most conjested pipes to watch it go faster. :)

            I've worked with our provider a bit with routing. We have mirrored servers in colo's around the country. If one city is conjested, we move traffic *AWAY* from the conjestion. Usually our traffic makes a difference for everyone else. I can have 500Mb/s added or removed from any given city within an hour, without flinching. Of course, before I do something like that, I put in a call first.. "Hey, can this city take 500Mb/s right now?"

            We wrote a program to take traceroutes from all the cities to various points, and plot them all onto a big network map, with ping times and the like.. We know which cities, peerings, or lines have problems at a glance..

            http://www.voyeurweb.com/network.12.23.2002-11h.pn g [voyeurweb.com]
            Warning: This picture is *BIG*. It's of our networks in Los Angeles, New York, Tampa, between each other, and to all of the root nameservers.. It makes a rather extensive map that is 11580x2669. It won't fit on your screen. Save it, and take it into your favorite image editing software to view it..

            This map is a little old (Dec 23, 2002 at 11am), but it gives a good impression of what the networks immediately around our servers looked like, and how they interact with each other.. Shitty networks stand out in red.. I definately wouldn't want to MORE of my traffic that way. Sometimes we don't have a choice. If your ISP uses a shitty provider, we have to send it that way..

    • Re:I'm confused (Score:5, Informative)

      by Randolpho (628485) on Friday February 14 2003, @04:36PM (#5305501) Homepage Journal
      The author is not trying to say "those bastards over at network X are selfish and they're slowing us down" or anything like that. He's trying to point out that a fundamental aspect of internet routing, the concept of forwarding a packet via the fastest route to the destination, can in many cases slow down performance if the fastest route gets congested.

      Frankly, I'm surprised this is considered news; I learned it in a networking course on my way to a CS degree. I can only assume that the author is trying to push a new algorithm for congestion control and is using "selfish routing" as a marketing scheme. The thing is, I can't seem to find the suggested reprieve.

      Ahh, here it is:
      Roughgarden has a suggestion that wouldn't be expensive to implement. Before deciding which way to send information, he says, routers should consider not only which route seems the least congested, but also should take into account the effect that adding its own new messages will have on the route it has chosen. That would be, he says, "just a bit altruistic" in that some routers would end up choosing routes that were not necessarily the fastest, but the average time for all users would decrease.
      • Re:I'm confused (Score:5, Informative)

        by Zeinfeld (263942) on Friday February 14 2003, @05:54PM (#5306047) Homepage
        Frankly, I'm surprised this is considered news; I learned it in a networking course on my way to a CS degree. I can only assume that the author is trying to push a new algorithm for congestion control and is using "selfish routing" as a marketing scheme.

        Yep, if you have three available routes A, B, C with bandwidths 10, 4 and 1 the selfish router would send all trafic through route A in every case. An altruistic router would make a random choice between A, B, C such that A was chosen 2/3rds of the time and B, C were chosen in proportion 4:1 the rest of the time.

        You can then tweak further by using traffic information. If the system is unloaded then use A all the time.

        The same observation applies to the problem where traffic alternates between two routes rather than dividing itself evenly. That is elementary control theory. The problem is that the response has too high a gain factor, in effect the gain factor is infinite so instead of being shared across the routes the system is going into oscillation.

        There is an obvious solution to that problem, you measure the change in the traffic statistics and moderate your response to changes.

        This is the sort of thing the IETF should be doing. Unfortunately the IETF has been out to lunch for many years now. They have failled to respond with any urgency to most of the issues facing the net. Most of the participants seem to use it as a substitute social life rather than as a place to get things done.

  • by scotay (195240) on Friday February 14 2003, @04:17PM (#5305339)
    Eventually the system will settle to an equilibrium that mathematicians call a Nash flow, which will be, on the average, slower than the ideal.

    If nobody goes for the blond, we all get laid. Somebody go tell the routers.
    • Re:Thanks Ron Howard (Score:4, Interesting)

      by PetWolverine (638111) on Friday February 14 2003, @04:27PM (#5305429) Journal
      And just as in A Beautiful Mind Nash's friends suspected him of coming up with a plan that would allow him to get the blonde, people will suspect Cornell of coming up with this plan to get more bandwidth. Also just as in the movie (/book, which I haven't read yet) that's probably not the case...or let's hope it's not.
    • Re:Thanks Ron Howard (Score:4, Informative)

      by JoeBuck (7947) on Friday February 14 2003, @05:57PM (#5306069) Homepage

      As has been pointed out [variagate.com], the movie got the Nash equilibrium principle entirely wrong. Since a cheater can benefit by going for the blonde at the last minute, after the other guys have already committed themselves, it's not an equilibrium.

  • Another article (Score:4, Informative)

    by aengblom (123492) on Friday February 14 2003, @04:17PM (#5305341) Homepage
    Cnet's got a write up [com.com] on this too.
  • by jj_johny (626460) on Friday February 14 2003, @04:18PM (#5305349)
    Attention Science Blog - We have things called protocols and such. Please use specific terms.

    Maybe I am just a lowly CCNP but is this all just a theory paper about the problems with "routing" or were there specifics about current routing protocols that should be updated or current practices that should be changed. Please help, everyone knows that the current routing could be better but theory stuff just does not help us much.

    • by orthogonal (588627) on Friday February 14 2003, @04:29PM (#5305450) Journal
      Maybe I am just a lowly CCNP

      No, it's no longer "CCNP"; the Soviet Socialists are now calling themselves the nationlists, the Union is gone, and the country's just named Russia.

      But thanks, "Comrade". We'll open a dossier on you anyway.
    • Yes it was a very light article but if you had followed the links, well not so much links as URLs, you would have found this. http://www.cs.cornell.edu/timr/ and this http://www.cs.cornell.edu/People/eva/eva.html

      Which although I have not even starte to read it yet appears to have more than enough detail to satisfy almost anyone. Have fun I know I will. :)
    • by ninewands (105734) on Friday February 14 2003, @05:56PM (#5306064)
      It's not so much a theory piece as it is a GROSS misunderstanding, on the author's part, of the design principles behind the internet in the first place.

      The internet isn't, wasn't, never has been intended to be a high-performance network. It IS and was intended to be a high-availability network (read ... capable of suvivng a nuclear attack) ...

      One of the ways the 'net accomplishes this is by detecting damage and routing around it by trying to always use the "lowest cost" route from point A to point B. A significant factor in "lowest cost" is least time.

      By always seeking to use the fastest (or most efficient by some other measure than time) route from point A to point B, performance levels on the 'net get leveled out and really fat pipes draw lots of traffic, while "pin-holes" don't.

      For the life of me I can't understand just what the hell the author's complaint is ... it reads, to me, that he's complaining because the defined routing protocols work THE WAY THEY"RE SUPPOSED TO. Well, DUHH!

      Just my US$0.02
  • by teamhasnoi (554944) <teamhasnoi.yahoo@com> on Friday February 14 2003, @04:19PM (#5305351) Homepage Journal
    defaultuser@kaazalite.com

    'Cool! One meg left! .......huh? WTF?!!? Disconnected?! You dirty SOB!..FUUuuuuuuuccCCCKKK!'

    • Please send this article to defaultuser@kaazalite.com

      Don't worry, I read it. But I'm still not changing.

      Although I had a sad revelation last night, after saying to a friend "Yeah, hopefully when I get back from work tomorrow night those music videos will be finished." I then realized the interest of my Friday night is determined by whether or not my Utada Hikaru MTV Unplugged (JP) videos will be completed.

      I then realized I must get out more. Good thing my girlfriend gets back on Thursday...
  • by juanfe (466699) on Friday February 14 2003, @04:20PM (#5305367) Homepage
    Given the growth of walled gardens, of email attacks, of DoS, of more traffic channeled through fewer fat pipes owned by fewer public/non-profit organizations, is this still possible?
  • by captainboogerhead (228216) on Friday February 14 2003, @04:22PM (#5305379) Journal

    It seems the researchers at Pinko U finally realize that routers have always been programmed using the enlightened-self-interest model of bandwidth utilization. It's time to shut them down.

    The last thing we need is lazy, welfare dependant internet backbones sitting around all day watching The Dukes of Hazzard and drinking Lite Beer. If the altruists win this round, AOL transforms from the gated-suburb of the internet into the "Projects". Aren't we taxed enough?

  • by floppy ears (470810) on Friday February 14 2003, @04:22PM (#5305385) Homepage
    It basically says that network congestion is like congestion on highways. If everybody is trying to change lanes all the time, they might save a bit of time for themselves, but on the whole they will slow down traffic for everybody.

    In theory, this may slow down the internet by something like 50-60% at most. Nobody really knows how well the Internet conforms to the mathematical model, however. Any benefit from trying to fix the problem might be outweighed by the cost of implementing a solution.
    • by Smidge204 (605297) on Friday February 14 2003, @04:43PM (#5305564)
      It's funny you should mention how internet traffic is like highway traffic.

      There's an amusing, if not somewhat interesting, article writting up on how you can single-handedly relieve traffic congestion here:

      http://www.amasci.com/amateur/traffic/traffic1.h tm l

      It's basically the same idea: If a few people just give a little slack, everybody wins out.
      =Smidge=
  • DL managers (Score:5, Funny)

    by zephc (225327) on Friday February 14 2003, @04:23PM (#5305394)
    this is why I hate download managers, especially ones that create dozens of connections to download segments of large files.

    My flatmate does that with eDonkey on TWO of his computers and squashed our bandwidth for a week (downloading pr0n of course)
    • Re:DL managers (Score:3, Interesting)

      by bgarrett (6193)
      Download managers aren't really the problem, except when you don't have the bandwidth to sustain parallel downloading. If you have enough pipe, parallel DLs ARE faster than a single serial download.

      The problem the paper is describing is at the larger "router's eye view" scale, where multiple routes out to the rest of the network exist, and where only the fastest route is used - the other two pipelines are basically starved of packets.
      • Re:DL managers (Score:3, Insightful)

        by zephc (225327)
        my home setup
        LAN switch DSL modem ISP world

        we have sDSL all routable IPs, at about 80-100K in any direction

        i have no way to throttle anything when he is running eDonkey, downloading 5-10 movies at once with over a dozen connections between each. i dont believe eDonkey allowes any kind of throttling, unlike Kazaa.

        I lost entire messages over AIM while he was doing that shit.

        my http server is set up to allow only 5 connections max now, sincew someone a few months ago started leaching movies from me with FlashGet, killing my own overall speed.

        Sure its not related to the article, but when i saw 'selfish' and 'routing' I had to rant a bit.
  • by Jugalator (259273) on Friday February 14 2003, @04:25PM (#5305415) Journal
    I suppose this is the heart of the article, btw:

    "if routers choose the route that looks the least congested, they are doing selfish routing. As soon as that route clogs up, the routers change their strategies and choose other, previously neglected routes. Eventually the system will settle to an equilibrium that mathematicians call a Nash flow, which will be, on the average, slower than the ideal. "

    Now, hasn't there been a problem some time a long time ago in early Internet history where parts of the internet entered a state of self oscillation. I recall this was later fixed somehow to a point by revising some protocols.

    I remember it basically as the problem where lots of routers (for some reason) started sending packets to one path, it got very congested, all routers switched to another, congested, etc.

    I only have very vague memories since I took the course where I heard it some years ago. Perhaps I'm only full of bullshit. :-)
  • by guacamolefoo (577448) on Friday February 14 2003, @04:28PM (#5305437) Homepage Journal
    If the "altruistic" behavior results in a better network, then isn't there a benefit for the altruistic behavior? Doesn't it cease being altruistic if there is a benefit? Aaggh! I'm caught in another Prisoner's Dilemma with an uncertain number of moves!

    Where's my Dawkins? (That's twice today I've thought of him).

    GF.
  • by Chocolate Teapot (639869) on Friday February 14 2003, @04:29PM (#5305454) Journal
    I would have had first post but it got stuck in a jam in Toronto.
  • Somewhat interesting (Score:5, Informative)

    by rabtech (223758) <slashdot_sez@boneville . n et> on Friday February 14 2003, @04:30PM (#5305463)
    It appears that they are claiming routers pick the fastest route to push packets down, which can in turn cause that route to become congested, thus slowing it down, and then the router picks a new route, causing it to become congested and slow down, and so on.

    Supposedly, if the router picked the fastest AND least congested route, then some packets might take a little longer to get to their destination, but the overall latency of the internet would decrease.

    In theory. In reality, I don't know how much peering arrangements change the equation. You see, if you are a network provider, you have two goals with peering: dump enough traffic onto your peer points so that you are exchanging about equal amounts with your peer AND get traffic that isn't bound for your network OFF your network as quickly as possible.

    In practice, this means ISPs who peer have a large incentive to route packets coming from peer parter A directly to peer partner B, without regard for what that does to the latency of the packet, nor the congestion of the peering partners. The peered packets become more like the hot potato, bouncing around peer points until they actually arrive near the destination network. That lowers overall efficiency as well. (companies like Internap don't peer for this reason; they pay for all connection points even though they have enough traffic to get peering points for free. They cost more, but they have very low latency, packet loss, etc).

  • as long as (Score:3, Insightful)

    by geekoid (135745) <dadinportland.yahoo@com> on Friday February 14 2003, @04:34PM (#5305488) Homepage Journal
    'the internet' is faster then my connection to it, does it really matter?
  • by rrkap (634128) on Friday February 14 2003, @04:40PM (#5305541) Homepage

    This is essentially a pricing problem.

    Here's a quote from the original 1968 paper that used the term

    The tragedy of the commons develops in this way. Picture a pasture open to all. It is to be expected that each herdsman will try to keep as many cattle as possible on the commons. Such an arrangement may work reasonably satisfactorily for centuries because tribal wars, poaching, and disease keep the numbers of both man and beast well below the carrying capacity of the land. Finally, however, comes the day of reckoning, that is, the day when the long-desired goal of social stability becomes a reality. At this point, the inherent logic of the commons remorselessly generates tragedy.

    As a rational being, each herdsman seeks to maximize his gain. Explicitly or implicitly, more or less consciously, he asks, "What is the utility to me of adding one more animal to my herd?" This utility has one negative and one positive component.

    1. The positive component is a function of the increment of one animal. Since the herdsman receives all the proceeds from the sale of the additional animal, the positive utility is nearly + 1.

    2. The negative component is a function of the additional overgrazing created by one more animal. Since, however, the effects of overgrazing are shared by all the herdsmen, the negative utility for any particular decisionmaking herdsman is only a fraction of - 1.

    Adding together the component partial utilities, the rational herdsman concludes that the only sensible course for him to pursue is to add another animal to his herd. And another.... But this is the conclusion reached by each and every rational herdsman sharing a commons. Therein is the tragedy. Each man is locked into a system that compels him to increase his herd without limit -- in a world that is limited. Ruin is the destination toward which all men rush, each pursuing his own best interest in a society that believes in the freedom of the commons. Freedom in a commons brings ruin to all.

    There are two common solutions to this kind of problem. Regulate use of the common resource or sell it. Because of the structure of the internet, it is hard to fairly price bandwidth and no good regulatory scheme has developed, so I don't see any other answer than living with it.

  • by mdouglas (139166) on Friday February 14 2003, @04:46PM (#5305595) Homepage
    "Routers have many ways to decide. Sometimes they send out test packets and time them."

    it isn't RIP, OSPF, EIGRP, or BGP. i don't know ISIS, but i strongly suspect these people are talking out of their asses.
  • by Walker (96239) on Friday February 14 2003, @04:51PM (#5305622)
    In many (but certainly not all), Internet traffic is similar to automobile traffic. Packets are discrete objects, like cars, and not continuous like a river or radio signal. Analysis on automobile traffic has already discovered properties like this. There are many simulations that show if we all ensured 3 car lengths between us and the next car, we would avoid the accordion and get to work significantly faster.
  • by BusDriver (34906) <tim@muppetz.com> on Friday February 14 2003, @04:53PM (#5305637) Homepage
    This article makes no sense from a proper real world routing perspective.

    Any provider who is doing anything slightly serious will be using BGP4 routing for their EGP. It does NOT send out magic packets to find best paths. It learns routes from it's peers and will choose the best route based on a defined set of decisions. Routers do not keep a list of "neglected routes." If one route goes away, the router will simply pick the next best path.

    Read more about BGP4 from Cisco's website [cisco.com]. You will find little in common with this article and the one linked in the story.

    Good routing relies on good admins with a well defined routing policy. There is no such thing as a "selfish" router.

    Tim
    • by BeBoxer (14448) on Friday February 14 2003, @10:00PM (#5307077)
      if I could.

      I think whoever wrote this article is far removed from the real world. They are finding theoretical problems with the routing protocols we would like to be running. As you pointed out, pretty much the entire backbone is using BGP4 to make routing decisions. And BGP4 doesn't really have any measure of how congested links are, nor how long the latency is. The basic measure of BGP4 is how many different providers (called AS's or Autonomous Systems) a packet might have to traverse.

      Hmmm, the router says, is the best route thru C&W->AT&T->Bob's_ISP or just Level3->Bob's_ISP? I'll pick the two hop route. Sure, we all do some manual tuning, where the engineer says "I know the L3->Bob link is slow, so I'll make it look like L3->L3->Bob", but BGP4 is fundamentally a really stupid protocol. In theory. In practice, it works fine almost all of the time.

      The most telling quote from the article is this:


      They also found that doubling the capacity of the system would provide the same benefits as a managed system.


      No shit Sherlock. I could've told you that five years ago. Why do you think QoS is still facing an uphill struggle? It's far cheaper and easier to just keep cranking up the bandwidth than to replace BGP4 with something smarter, or to deploy QoS protocols Internet wide.

      Don't get me wrong, I think they are doing great research. It's good to try and figure out what might go wrong with next-gen protocols before the get deployed. But I don't think they are talking about problems on todays Internet.
  • by urbazewski (554143) on Friday February 14 2003, @04:55PM (#5305663) Homepage Journal
    This is not the main point of the article but:

    The Tragedy of the Commons , often cited by environmentalists, describes 14th-century Britain, where each household tried to gain wealth by putting as many animals as possible on the common village pasture. Overgrazing ruined the pasture, and village after village collapsed.

    The "tragedy of the commons" that Hardin's article is devoted to is increasing world population. What evidence is there for overgrazing in England before as opposed to during and after the forced transition to private ownership? Most cultures with a common land tradition also have a set of rules for governing land use that avoids such tragedies, for example, irrigation systems in Bali where the farmer who gets the water last controls the water flow. Ones that didn't solve the problem of overuse of resources are conspicuous by their non-existence (Easter Island, some settlements in the Southwest US, some populations on islands in the South Pacific ).

    The 'tragedy of the commons' is one of the most misunderstood and overused metaphors of our times. The idea that a system with resources held in common is necessarily unworkable is false --- what is needed is institutions that effectively manage common resources, and such institutions have emerged repeatedly and continue to exist. Often it is when these cultures come into contact with market-oriented societies that the traditional systems are undermined and collapsed. Often what happens is not "the tragedy of the commons" but "the tragedy of failed privatization" in which a traditional management system is destroyed without establishing a viable alternative.

    How does this relate to the internet? It's a cautionary tale --- be very very careful when introducing monetary incentives into a system that has previously relied on cooperation and cultural norms.

    blog-O-rama [annmariabell.com]

  • by Salamander (33735) <jeff@NOsPAm.pl.atyp.us> on Friday February 14 2003, @04:58PM (#5305684) Homepage Journal

    The problem is not that service providers pick the route that gets the packet to its destination quickest; it's that they pick the route that gets the packet off their network the fastest. Those two are not the same thing at all. Think about it geographically. Let's say I'm a square network and I receive a packet at the northern end of my western border destined for somewhere to my northeast. I know that the quickest way to get it to its destination is to move it east across my own network and deliver it to my eastern neighbor. However, I also know that if I pass it on to my northern neighbor it will still get there without coming to me again, and my northern neighbor is closer. So, if I'm a selfish bastard, what do I do? I ship it northward, minimizing the time that it spends on my own network but increasing the total time before it reaches its destination. If everyone does this same sort of "hot potato" routing, total load on the network increases for everyone. In fact, my northern neighbor might very well be doing the same for packets lying to our southwest. We'd both be better off if we'd "play nice" but since we're both trying to be selfish we both lose.

    Yes, folks, it's an instance of the prisoners' [brynmawr.edu] dilemma [vub.ac.be] and these researchers are not the first [gildertech.com] to notice the fact [zdnet.com.au].

      • If that packet is going north or northwest anyway, send it north!

        I didn't say it was going northwest; it was going northeast, and the shortest route would have been "straight across my network". That's all besides the fact that real networks don't have such simple geometry, so line algorithms are utterly irrelevant.

        The fact is, most cases are going to be handled as efficiently as they would have been in a more "friendly" environment.

        If only. The whole point is that it's not handled that way. Did you look up from your graphics-algorithm textbook to read what I actually wrote?

  • by acomj (20611) on Friday February 14 2003, @05:04PM (#5305730) Homepage
    This is a classic example of the prisoners dilema problem.

    Basically if everyone acts unselfishly they do better. But from each individuals perspective they do better when they act selfish, so it all falls apart. Its interesting stuff and the prisoners dilema game algorithms are interesting.

    Prisoners Dilema [drexel.edu]

    Play the dilema game online [plocp.com]

  • by Billly Gates (198444) on Friday February 14 2003, @06:10PM (#5306123) Homepage Journal
    Ipv6 supports better Qos so if the fastest route is congested the router can more easily find out and select an alternative route.

    Internet2 has an extremely fast backbone and is based on Ipv6. This will help greatly since the backbone of the current internet can be quite congested at times. Lets hope its implemented soon as the current problem will likely go away.
  • Ok, this has to be the most convoluted article I've ever read.. They're effectively saying, don't use the best route, pick another, because your extra traffic may break the best route.

    We diagramed a sample network here in the office, to try and explain what we just read to ourselves.. We picked 5 cities (New York, Chicago, Los Angeles, Dallas, and Miami), and drew direct routes between Miami, LA, and NY to each other. Chicago gets routes to NY and LA. Dallas gets routes to everything but Chicago.

    We then contemplated what a packet from LA to NY would be looking at.

    On our mythical network, we have the following ping times.

    LA -> NY 20ms
    LA -> Chicago -> NY 25ms
    LA -> Dallas -> NY 40ms
    LA -> Miami -> NY 60ms

    So, we shoudn't be selfish, and take the LA->NY route? We should direct our traffic LA->Dallas->NY ? If this route is already slow or conjested, what good does that do? Now instead of using a perfectly good route, we're killing a conjected one.

    If LA->NY is the best/fastest at the time, use it. If/when that becomes more conjested, it will no longer be the best choice, and the new best choice will be chosen..

    Not everyone is going to be using YOUR best choice all the time.. Very doubtful that Miami will be routing to LA to go to NY. If they do, it's because Miami->LA is already overloaded. But as it usually works, For Miami->NY, there is already a second best choice (Miami->Dallas->NY).

    No matter how we look at it, this doesn't make any sense.. Here's a sample of the lines for our example.

    LA->NY OC192
    LA->Chicago OC48
    Chicago->NY OC48
    LA->Dallas OC48
    Dallas->NY OC24

    So, we'll leave the LA->NY route empty, and keep dumping our load onto the lesser routes?

    I do like the idea though, to keep the best choice (LA->NY) open for myself.. Everyone else chooses the second best route.. Go ahead and flood those OC48's, I'll use the OC192 that no one else uses.. :)

  • by obnoximoron (572734) on Friday February 14 2003, @06:22PM (#5306184)
    of the main paper : http://www.cs.cornell.edu/timr/papers/indep_full.p df and others.

    1. Their basic idea is to model decentralized routing as a Nash game and then worst-case compare the performance of this game with the best achievable by ANY algorithm, decentralized or not. This sort of comparison is common in the field of competitive analysis .

    2. Assuming a hop latency to increase linearly with additional traffic on it, selfish routing causes the average packet latency to increase by no more than 4/3 of that caused by ideal optimal routing. This worst-case figure had been earlier called "the Price of Anarchy" by Papadimitriou, a famous researcher in algorithmic complexity who every CS student loves to hate :P

    3. Similar Prices of Anarchy have been derived by them for when the hop latency increases nonlinearly with the additional traffic on it.

    4. The worst case is always achievable with a simple network of 2 nodes connected by parallel links. This is the exactly the example used in networking courses and textbooks to illustrate the oscillation problem caused by selfish routing. This paper says that using this simple network as example is justified since the worst case can be always be analysed with it.

    5. Instead of optimizing routing to try reach the minimum possible average latency, you can keep the routing selfish but double each link capacity and achieve the same result.
  • by earthforce_1 (454968) <(moc.oohay) (ta) (1_ecrofhtrae)> on Friday February 14 2003, @08:40PM (#5306827) Journal
    Is unfortunate proof that altruism breaks down on a large scale. This is the fundamental flaw of socialism - humans evolved from simian ancestors, who basically lived in small tribal groups. We are altruistic up to a maximum of about 75 or so individuals, then it breaks down.

    I have seen videotape of a psychology experiment, where an individual feigned a serious medical problem and keeled over in the middle of the street. When the test subject tried this on a busy urban thoroughfare, large passing crowds actually stepped over the guy. But in a small village, shopkeepers rushed out onto the street to try and help him.

    There was a famous murder case in NYC where over 100 neighbours heard a woman begging for help as she was having her life snuffed out over a sadistic killer over a period of time. Nobody reported it or tried to intervene, they all assumed somebody else would do something about it. This resulted in the passage of a law, which as I recall was the subject of the final Seinfeld episode.