DTN-Bone
In the spirit of the mbone and the 6bone, we are using the term "dtnbone" to denote our effort to establish a worldwide collection of nodes running DTN bundle agents and applications. These nodes cannot take the place of internal test beds in various research organizations; rather, they augment these internal environments in areas such as remote management and control of nodes, interoperability, application deployment and testing, as well as operations across administrative boundaries.
This page lists nodes that various organizations are making available for interconnection via the Internet. That is of course only the first step. Node operators need to set up their local environments so bundles can be transferred, and the nodes have to run some sort of application beyond the bundle forwarding engine. Look at
GRC Always On DTN Network Instructions for using the GRC multi-hop, DTNbone with network management capabilities and disconnection.
Ohio University Always On DTN Network Instructions for using the Ohio University multi-hop, DTNbone with network management capabilities and disconnection.
Network Management Meeting Notes, slides, & agenda from January 8, 2010 DTN Network Management Meeting at Ohio University.
Disconnectathon This interoperability test took place on July 29 and 30, 2009. The information on these pages remains relevant for future tests; many of the network configurations will remain on the DTNbone.
Results were presented at the dtnrg research group meeting in Stockholm. (Download the slides)
Applications for notes on deployed applications, and
Use Cases for notes on successful interconnection efforts.
Security Test Keys contains test keys can certificates that can be used for interoperability testing.
Technical Details
So far, nodes represent the following implementations:
DTN2 - the bundle reference implementation
ION - the JPL implementation of the Bundle Protocol and LTP
LTPlib - the LTP implementation developed at Trinity College.
- Spindle3 - The BBN Technologies implementation of the Bundle Protocol, based on the PIRANA BPA
IBR-DTN - The IBR implementation of the Bundle Protocol for Embedded Systems, Standard Linux and Android smartphones
Setting Bundle Lifetimes:
- In theory bundle lifetimes are set by the application.
- For DTNPING, the default is 30 seconds. So, if your DTN network is not synchronized to within 30 seconds you may need to do so, or extend the lifetime of the DTNPING bundles.
- The following table list some of the current implementations default bundle lifetimes and why.
Organization |
Implementation |
Mission/Target |
Lifetime |
Rational |
JPL |
ION |
DINET |
7 Days |
So that bundles may remain queued for future transmissions if needed. |
Helsinki University of Technology |
DTN2 |
"SCAMPI Router" |
Selectable in API with 12 hour default |
Arbitrary |
Helsinki University of Technology |
DTN2 |
"MiningDTN" |
Selectable in API with 24 hour default |
All data will be delivered within 24h lifetime from observed mobility patterns. |
Viagenie |
Postellation |
Embedded Systems |
1 Week |
Arbitrary |
Folly Consulting Ltd. |
DTN2 |
N4C and SAIL |
A couple of Days or more |
Delivery was dependent on a daily (but not guaranteed) helicopter flight schedule and/or contacts between individuals that could not be guaranteed to within a few days. |
Folly Consulting Ltd. |
DTN2 |
Information Centric Networking (ICN) |
Days to weeks or more. |
Depending on the validity/usefulness of the data. |
BBN |
Spindle |
IP over DTN |
15 minutes or 2 hours |
Uses 2 available code points. One code point is used to indicate if the application is DTN tolerant or not. The second is used for expedited forwarding (15 minutes) or standard forwarding (2 hours). Having only 2 available code point limits the choices. |
Interconnection of different implementations:
- ION/LTP and LTP-T will interoperate via UDP
ION and DTN2 currently only interoperate via UDP
- Some researchers have patched ION to change its s-TCP CL to TCP
- Ohio University is implementing TCP as an additional CL into ION, monitor the ion-users and dtnbone lists for announcements
- Spindle3 interoperates with compliant UDP and TCP implementations
- IBR-DTN is interoperable with compliant TCP CL and UDP CL implementations. DTN2 and ION have been successfully tested
Node Naming:
dtn: name space supported by ION, DTN2 and IBR-DTN
- node names should be listed inside the node details
- this wiki can serve as a useful reference to names used, but name collisions are not likely
ipn: name space used by ION for CBHE operations (the name space used to trigger CBHE may change)
- CBHE requires the use of a flat space of node numbers
- node numbers need to be coordinated, for now we are using the wiki to do this:
[wiki:/CbheNodes CBHE Node Numbers]
- IBR-DTN has support for CBHE with ipn: addresses. May or may not be interoperable with ION
Get Involved
The dtnbone effort is organized by Hans Kruse at Ohio University, Athens, Ohio, United States. E-mail me with any questions or with information for this page.
Join the dtnbone mailing list; this is a low-volume list used to coordinate activities between node operators.
- Edit this page to add your information if you feel comfortable doing so. The ["Home"] page has instructions for requesting edit access.
Nodes
The table below uses the following conventions for Bundle Protocol (BP) Convergence Layers (CLs):
TCP - BP over TCP as described in [https://datatracker.ietf.org/drafts/draft-irtf-dtnrg-tcp-clayer/].
- The assigned port if 4556/tcp
- s-TCP - BP over TCP as implemented in ION.
- Also uses 4556/tcp, may be moved in future implementations.
- UDP - BP transport over UDP sending one bundle per UDP packet.
- The assigned port is 4556/UDP
- LTP - BP transport over LTP which in turn usually transmits its frames in single UDP packets (indicated by UDP in the LTP column below).
- Ports 1113/udp and 1113/tcp have been assigned by IANA
The UDP convergence layers are being discussed via [https://datatracker.ietf.org/drafts/draft-irtf-dtnrg-udp-clayer/]
Listed below are the nodes that are generally available for interconnection via DTN. Note: more often than not some coordination between nodes is required (e.g., editing of local configuration files) before a connection can be established. Look [#Other here] for information on specific DTN application services. Below the table of nodes you will find additional information where available.
Organization |
Implementation |
OS |
IP Address |
Bundle CL |
LTP CL |
More Detail |
Contact |
Ohio University |
ION |
Linux |
iongateway.dtnbone.ocp.ohiou.edu |
s-TCP, TCP, UDP |
UDP |
[#OU Ohio U.] |
|
Ohio University |
ION, DTN2 |
Linux |
quest.its.ohiou.edu |
s-TCP, TCP, UDP |
UDP |
[#OU Ohio U.] |
|
Comnet, TKK |
DTN2 2.6 |
n/a |
shrek.netlab.hut.fi |
TCP |
n/a |
[#CTKK Comnet] |
|
EU N4C project |
DTN2 |
n/a |
130.240.97.204 |
TCP |
n/a |
||
Trinity College Dublin |
DTN2, LTPlib |
n/a |
basil.dsg.cs.tcd.ie |
TCP,UDP |
UDP |
[#TCD Trinity CD] |
|
NASA Glenn Research Center |
DTN2 |
n/a |
192.55.90.165 |
TCP,UDP |
n/a |
[#GRC NASA-GRC] |
|
NASA Glenn Research Center |
ION |
n/a |
192.55.90.165 |
sTCP |
[#GRC NASA-GRC] |
||
Viagénie |
DTN2 |
n/a |
reeves.viagenie.ca |
TCP, UDP |
n/a |
[#VG Viagénie] |
|
Shawnee State University |
DTN2 |
Linux |
shawneeursamajor.org |
TCP, UDP |
pending (UDP) |
[#SSU Shawnee State] |
|
BBN Technologies |
Spindle3 |
n/a |
192.1.100.125 Offline |
TCP,UDP |
n/a |
[#BBN BBN Technologies] |
|
BBN Technologies |
Spindle3 |
n/a |
192.1.100.126 Offline |
TCP,UDP |
n/a |
[#BBN BBN Technologies] |
|
BBN Technologies |
Spindle3 |
n/a |
192.1.100.127 Offline |
TCP,UDP |
n/a |
[#BBN BBN Technologies] |
|
IBR, TU Braunschweig |
IBR-DTN |
OpenWRT/Linux |
dtnbucket.ibr.cs.tu-bs.de |
TCP,UDP |
n/a |
[#IBR IBR, TU Braunschweig] |
|
IBR, TU Braunschweig |
IBR-DTN |
OpenWRT/Linux |
project38.ibr.cs.tu-bs.de |
TCP |
n/a |
[#IBR IBR, TU Braunschweig] |
|
Node Details
Ohio University
- Geographic Location: Athens, OH 39.3253 -82.1051
Contact Information: MailTo(kruse AT ohiou DOT edu)
- Node DNS name or IP address: iongateway.dtnbone.ocp.ohiou.edu
- ION 1.2
- CL: TCP, LTP via UDP
- Ports
- 1113/udp ltp-deepspace
- 4556/tcp dtn-bundle-tcp (ION TCP)
- CBHE (ipn:) node number: 200
- Node DNS name or IP address: quest.its.ohiou.edu
- ION nightly build
- DTN2 available
- CL: UDP, sTCP, TCP, LTP via UDP
- Ports
- 1113/udp ltp-deepspace
- 4556/udp dtn-bundle-udp
- 4556/tcp dtn-bundle-tcp (ION TCP)
- CBHE (ipn:) node number: 102
- Active registrations:
- Other details
Shawnee State University
- Geographic Location: Portsmouth, OH 38.7312 -82.9943
Contact Information: Dovel Myers MailTo(dmyers AT shawnee DOT edu)
Node DNS name or IP address: shawneeursamajor.org -> 173.53.197.68
Implementation: DTN2 -> 2.7.0
- CL: TCP, UDP
- Port: 4556
- EID: dtn://earth.dtn
- Testbed Gateway For:
- dtn://earth_sat.dtn
- dtn://moon.dtn
- dtn://moon_sat.dtn
- dtn://mars.dtn
- dtn://mars_sat.dtn
- dtn://jupiter.dtn
- dtn://jupiter_sat.dtn
- Other Information
[http://shawneeursamajor.org/ Testbed Home]
[http://shawneeursamajor.org/about.html Testbed Layout]
[http://shawneeursamajor.org/gatewaysetup.html Using our Earth Gateway]
Comnet, TKK
- Geographic location: Espoo, Finland 24.283208, 60.18949
Contact information: Teemu Karkkainen MailTo(teemuk AT netlab DOT tkk DOT fi)
- Node DNS name or IP address: shrek.netlab.hut.fi
- CL: DTN2 TCP (Internet Draft version) on Standard ports
- Applications
- DTN camera: dtn://camera.dtnbone.comnet.tkk.fi/camera (Will reply to any bundle it receives with a jpeg picture in the payload).
- Active registrations:
- dtn://dtnbone.comnet.tkk.fi
- dtn://dtnbone.comnet.tkk.fi/ping
Trinity College Dublin
- Geographic Location: Dublin, Ireland @53.344505, -6.258967
Contact Information: MailTo(stephen DOT farrell AT cs DOT tcd DOT ie, Stephen Farrell), MailTo(alex DOT mcmahon AT cs DOT tcd DOT ie, Alex McMahon)
- Node DNS name or IP address: basil.dsg.cs.tcd.ie
DTN2 & LTP-T
- CL: UDP, LTP via UDP
- Ports
- 1113/udp ltp-deepspace
- 4556/udp dtn-bundle-udp
- Active registrations:
- dtn://basil.dsg.cs.tcd.ie.dtn
- dtn://basil.dsg.cs.tcd.ie.dtn/ping
NASA Glenn Research Center
- Geographic Location: Cleveland, Ohio, United States.
Contact Information: MailTo(jishac AT nasa DOT gov, Joseph Ishac)
- Node: 192.55.90.165
- DTN2 ver 2.6
- Port 5017; CL: TCP, UDP
- dtn://unit017.dtn/
- ION ver 1.0r203
- Port 4556; CL: "s-TCP"
- ipn:17.1 (not queued) or ipn:17.2 (queued)
- DTN2 ver 2.6
Viagénie
- Geographic location: Québec City, Canada
Contact information: Marc Blanchet MailTo(marc DOT blanchet AT viagenie DOT ca) or Simon Perreault MailTo(simon DOT perreault AT viagenie DOT ca)
- Node DNS name or IP address: reeves.viagenie.ca
- DTN2
- UDP, TCP (Internet Draft version, standard port numbers)
Applications: DTN News Service (see http://reeves.viagenie.ca)
- Active registrations:
- dtn://reeves.viagenie.ca.dtn
- dtn://reeves.viagenie.ca.dtn/ping
BBN Technologies
- Geographic Location: Cambridge, MA, United States.
Contact Information: MailTo(dellard AT bbn DOT com, Daniel Ellard)
- Node name bbn-dtnbone-01.ir.bbn.com, IP 192.1.100.125
Online intermittently
- Spindle3 BPA (development version)
- Port 4556; CL: TCP, UDP
- dtn://bbn-dtnbone-01/
- Node name bbn-dtnbone-02.ir.bbn.com, IP 192.1.100.126
Online intermittently
- Spindle3 BPA (development version)
- Port 4556; CL: TCP, UDP
- dtn://bbn-dtnbone-02/
- Node name bbn-dtnbone-03.ir.bbn.com, IP 192.1.100.127
Online intermittently
- Spindle3 BPA (development version)
- Port 4556; CL: TCP, UDP
- dtn://bbn-dtnbone-03/
IBR, TU Braunschweig
- Geographic Location: Brunswiek, Germany, OH: 52.27321, 10.52521
Contact Information: MailTo(morgenro AT ibr DOT cs DOT tu-bs DOT de, Johannes Morgenroth) , MailTo(schildt AT ibr DOT cs DOT tu-bs DOT de, Sebastian Schildt)
- DTNBUCKET
Hardware: Buffalo Linkstation Pro
- Implementation: IBR-DTN 0.8
- EID: dtn://dtnbucket.ibr.cs.tu-bs.de
- DHT: dtnbucket.ibr.cs.tu-bs.de
- DNS: dtn://dtnbucket.ibr.cs.tu-bs.de
- IP: 134.169.35.178
- Routing: No
- CL: TCP, UDP
- 4556/tcp
- 4556/udp
- sbase
Hardware: Ubiquiti RouterStation Pro
- Implementation: IBR-DTN 0.9dev
- EID: dtn://sbase.dtn
- DHT: sbase.dtn
- DNS: project38.ibr.cs.tu-bs.de
- IP: 134.169.35.168
- Routing: IBR-DTN PRoPHET
- CL: TCP
- 4556/tcp
Specific Applications
News via DTN: [http://reeves.viagenie.ca/]
- DTN camera: dtn://camera.dtnbone.comnet.tkk.fi/camera (Will reply to any bundle it receives with a jpeg picture in the payload).
- IBR-DTN webcams: dtn://dtnbucket.ibr.cs.tu-bs.de/webcam01 and dtn://dtnbucket.ibr.cs.tu-bs.de/webcam02 (Will reply to any bundle it receives with a jpeg picture in the payload).