NASA DTN Protocol: How Interplanetary Internet Works
First time accepted submitter GinaSmith888 writes "This is a deep dive in the BP protocol Vint Cerf developed that is the heart of NASA's Delay-Tolerant Networking, better known as DTN. From the article: 'The big difference between BP and IP is that, while IP assumes a more or less smooth pathway for packets going from start to end point, BP allows for disconnections, glitches and other problems you see commonly in deep space, Younes said. Basically, a BP network — the one that will the Interplanetary Internet possible — moves data packets in bursts from node to node, so that it can check when the next node is available or up.'"
The main problem is the long delay at light speed.
TLDR X.25 with big buffers
"Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
This is something for private industry to figure out. Why are our tax dollars being wasted on stuff like this when in reality, we have no mechanism to get men past the Moon for the next 20-30 years? Shouldn't we spend tax dollars on stuff that is useful, such as not being beholden to our #1 creditor, China?
We don't need Internet connectivity near Saturn, we need to fix a deficit problem right here on Earth.
:( :( :(
: ) I've often fantasized about the internet in space and what could make it work. It's very cool to hear that it's already thought of and implemented!? Amazing! I think the next step is to dispatch satellites one per planet so a full network can be fleshed out. Can you imagine how crazy a full traceroute would look like? I'd love to see it! I really would. I feel like a kid again. My packets can finally go into space.
I thought something like this already existed. And it worked pretty well at the time.
http://en.wikipedia.org/wiki/UUCP
Awe hell, at first I thought this was NASA's implementation of the DNT (Do Not Track) header -- It almost made sense: Some objects in space might not want to be tracked; Spy satellites for instance.
Damn Lexdysia...
The only problem with the BP protocol is the data mining rigs that burst and spread raw SQL queries all over the coast of Amazon.com and then wonder why people are pissed that they can't buy or sell from that site until its cleaned up!
...with the tech lower in the piece"
Except, they never do.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
Reminds me of the problems the old FidoNet had to deal with - nodes not being available, or only available for short times, poor quality connections, low speed, etc. It worked remarkably well for all of those conditions I thought :)
Don't judge me based on my high slashdot user id!
While on the subject, when are we going to establish repeater stations around the solar system so that space probes don't need massive transceivers and line-of-sight to communicate with the Earth?
Isn't IP already delay tolerant? I remember in the IPoAC trial for obvious reasons there were huge delays, but it still worked.
Actually it sounds more like fidonet. Store and forward networking just like early infrastructure that let email from dial up bbs nodes eventually reach a destination.
in any way related in eternAity...Romeo serve5 to reinforce
And now the question is: when will Linux support it?
I am not really here right now.
The problem is most any terrestrial network protocol expects a minimal signal-response delay between nodes, whereas even a perfectly functioning terabit/s Earth-Mars link would still have between a 6 and 40 minute delay due to the speed of light.
--- Most topics have many sides worth arguing, allow me to take one opposite you.
Better figure out how to access "subspace" if you want to play Halo 27 with your friends on Titan. Or maybe quantum entanglement could accomplish the same thing?
If you could reason with religious people, there would be no religious people
ION is probably the most popular open source implementation of DTN, and was developed on Linux machines..
Have gnu, will travel.
I've no doubt they'll succeed with this, but if they are going to do remote robot control they are going to have to develop a very 'interesting' command structure. I can see it now... Go Forward... Stop... Oops!
It sounds like a UUCP implemented at layer3.
I want to delete my account but Slashdot doesn't allow it.
Gaming must really suck, how are astronauts going to play online!? Well at least they can Download their Steam library..
I fucking hate that saying.
Sarah Palin is our revenge for you assholes acting like we don't exist.
it was called BITNET
http://en.m.wikipedia.org/wiki/BITNET
Does anyone have more information about the Lego Mindstorms robot that was used in this experiment? I'd like to use it as an inspiration with the kids.
The Curiosity Rover Made With Lego Mindstorms is pretty cool, but the fact that it uses "7 NXT Bricks, 13 NXT Motors, 2 Power Function Motors" makes it out of reach of the average home.
DTN is a store-n-forward protocol.
Conceptually kinda sorta like email in that regard.
The BP side of the equation brings the concept of bundling more information together in one unit (unlike IP, which tends to break info into smaller units , eg fragmentation).
The plan being to bundle together all the information required for The Application to do the next thing.
Imagine sending all the html-and-javascripts-and-css for a webpage in one (huge) packet. Your browser would have enough to render the page and start requesting the images (etc). If you were using a text-only browser, you'd have everything you needed - just waiting for the next user-input.
Visit CryptoGnome in his home.
This sounds just like FIDO used for inter-BBS and early internet email. Nodes would queue messages until the next hop was available. Why isn't the plan to use pairs on intangled particles to instantly pass information without regard for the speed of light or distance between end-points?
...something amateur ("ham") radio operators have been using since the 1980's...
-allen
KC2KLC
I am not a number - I am a free man!
Forget all this talk of UUCP, Fido and normal packet protocols, the closest current similarity is sending binaries over usenet.
The most important part is the delay time, when you 'launch' a usenet message you won't receive anything at all from the remote end for a very long time. It will probably be long enough for you to transmit the entire message and then some.
The medium also has some limitations ...
For usenet the binary files are packaged up into one archive them split into messages. Usually something isn't considered to be received until the entire archive has been received intact. It used to be that the receiving end would request repeats of messages that didn't get through. This takes a long time and wasn't simple to automate because of the multiple receiver nature of usenet. Nowadays more messages are added using the 'parchive' protocol the idea being that the extra messages are 'universal substitutes'. Say the transmitter needs to send out an archive of 1000 messages, furthermore it's likely that 4%-9% of messages will be lost, then adding 100 extra PAR messages will (normally) mean that the archive will get there intact first try. No retransmission request needed.
I expect 'bp' is very similar.
The UUCP analogy is wrong anyway. The point is that even in UUCP days, we connected two modems, which transmitted data with X, Y or Z protocol. And that protocol was even more sensitive to propagation delays, because acks had to be sent much more frequently. Try set up UUCP to a mars probe, and you'll see that the layer 2 protocols will probably break down pretty badly. That's why DTN is really important and an entirely different kind of beast.
cpghost at Cordula's Web.
Some idiot slows it all down again with SpaceBook....
"Basically, a BP network — the one that will the Interplanetary Internet possible — moves data packets in bursts from node to node, so that it can check when the next node is available or up."
Err... didn't this used to be called FidoNet?
Hire a Linux system administrator, systems engineer,
...in 3, 2, 1
Legitimate Bufferbloat?
Remember modem connections and 'feeds' for news and email? When most links were offline most of the time? Yep, networking before 'up all the time' connections were available to most of the world.
I had a Linux (and before that a Mark Williams 'Coherent' UNIX like) computer that ran UUCP, and did dial on-demand connections. I had it download email and subscribed usenet 'news feeds' nightly from a local university that had 'free' connections for members of the local UNIX computer users group.
It worked. It was solid once I got all the config's right.
Not long ago I saw some articles on the wide area network wireless internet in Africa uses these techniques even today to get connectivity 'out there' without having to have 'up all the time' servers in remote communities.
Usenet newsgroup and email server software are still there and available if anyone wants to use them. Actually, I should look into that for my local use too!
I would like to see the new BP protocol implemented and distributed with Linux. It could be great for implementing 'automotive node' networks (put a BP node in your car, and it could communicate whenever it found a un-secured WIFI connection as you drive down the road!
Dreaming... Life goes on.
... "When you pry the source from my cold dead hands."