Stanford Researchers Discover the 'Anternet'
stoilis writes "A collaboration between Deborah Gordon, a Stanford ant biologist, and Balaji Prabhakar, a computer scientist, has revealed that the behavior of harvester ants, as they forage for food, mirrors the protocols that control traffic on the Internet. From the article: 'Prabhakar wrote an ant algorithm to predict foraging behavior depending on the amount of food – i.e., bandwidth – available. Gordon's experiments manipulate the rate of forager return. Working with Stanford student Katie Dektar, they found that the TCP-influenced algorithm almost exactly matched the ant behavior found in Gordon's experiments.
"Ants have discovered an algorithm that we know well, and they've been doing it for millions of years," Prabhakar said.' The abstract is published in the Aug. 23 issue of PLoS Computational Biology."
ummm.... I do believe there were some seminal works during the pre-BT days regarding ant routing -- http://mute-net.sourceforge.net/howAnts.shtml.
while that has more to do with routing than congestion avoidance, I would hope that your average network engineer knows that ants have the EEs beaten cold.
Formic post!
If Slashdot were chemistry it would look like this:Cadaverine
the TCP-influenced algorithm almost exactly matched the ant behavior
How close?
They talking about a full implementation of RFC 5681 with all 4 schemes and all the bells and whistles, or just some trendy popular science stuff with "well, there seems to be ACKs".
http://tools.ietf.org/html/rfc5681 (not a rickroll, I promise)
I suppose a RFC 5681 loss recovery mechanism would be something like what happens when you step on an ant. ssthresh TCP setting is like how many ants fit thru the hole at once when you agitate the colony with a stick? We could probably have a lot of fun doing "official slashdot ant analogies" instead of the more common "official slashdot car analogies"
"Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
"Ants have discovered an algorithm that we know well, and they've been doing it for millions of years," Prabhakar said.
Does anybody else see the problem with this statement?
I think it would have been better said "We have discovered an algorithm that ant know well."
21st Century Renaissance Man
I suppose an anteater is used to stop ant torrents. Or would that be a DOS attack?
And yet again, Sir Terry Pratchett is making me speechless with his insights. Now, it's almost like something is taking its pleasure in making a real-life citations from his books.
Absence of proof != proof of absence.
Ants may have discovered TCP; but they are ignorant of the secret of aggressive litigation...
...but the anternet is still a really buggy network
They may have invented TCP/IP, but not "on a computer". So I call this prior art invalid.
If Pandora's box is destined to be opened, *I* want to be the one to open it.
I honestly didn't see a lot of substance here.
Instead of saying ants use TCP, I would say ants and TCP both use common sense.
When I apply for jobs, I contact friends in my network. If someone gets back to me faster, I reply back faster and send my resume to them quickly. Does that mean I am following TCP/IP?
PLoS Computational Biology does not have issues, it publishes continually as an online-only journal. People will also notice when clicking on the link to the abstract that they can view the full article for free, from anywhere, no paywall restrictions of any sort.
Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
Sounds very impractical. I mean, even if you could get enough ants to carry the standard station wagon full of tapes, they're still not going to attain highway speeds.
which does seem to be a far cry from TCP. While common lore (and the modern buffer bloated internet) has it that high RTT means little available bandwidth (and it sure does play havoc with the bandwidth product - giving rise to that lore fairly) - the design calls for packet drop rather than delay to indicate a link being overloaded. And while the source slows down - it does not actually throttles; it just awaits the ack - it wont slow down the next packets. It is just that the window won't grow further. So makes one think of the observations in RFC-2488.