© 2009 The MITRE Corporation. All rights reserved. Joint DTN / SOIS Meeting April 22, 2009 Colorado Springs, CO

© 2009 The MITRE Corporation. All rights reserved. Page 2 Agenda ■Current state of DTN –DTN Picture –RFCs –Implementations ■ DTN2 ■ ION –NASA DTN-for-2010 program ■Current State of SOIS

© 2009 The MITRE Corporation. All rights reserved. DTN as an Overlay Network Page 3 Application DTN TCP IPv6 Ethernet UTP DTN TCP IPv6 ATM DS-1 IPv6 Ethernet UTP Prox-1 NetworkTerrestrial Wired Network LTP Encap TC/TM Application DTN Prox-1 DTN Gateway Long-Haul Space Link DTN LTP Encap TC/TMProx-1 DTN Gateway Application DTN Transport Network Link Physical IP Router ATM DS-1 Encap

© 2009 The MITRE Corporation. All rights reserved. DTN as an Overlay Network Page 4 Application DTN TCP IPv6 Ethernet UTP DTN TCP IPv6 ATM DS-1 IPv6 Ethernet UTP Onboard NetworkTerrestrial Wired Network LTP Encap TC/TM Application DTN Spacewire DTN Gateway Long-Haul Space Link DTN LTP Encap TC/TMSpacewire DTN Gateway Application DTN Transport Network Link Physical IP Router ATM DS-1 ■Convergence Layers: the “glue” that interfaces DTN to lower- layer protocols such as TCP, UDP, Ethernet, BlueTooth –Convergence layers just move data from DTN node to DTN node –Routing happens at the DTN layer (choosing the next DTN layer router)

© 2009 The MITRE Corporation. All rights reserved. ■Requests for Comments –Architecture (RFC4838) –Protocol Specification (RFC5050) ■ Review of the above by JAXA ■DTN Implementations –DTN2 Reference Implementation –Interplanetary Overlay Network (ION) Implementation ■DTN interfaces to the rest of the system –Applications (API) –Lower layers ■ DTN has a notion of ‘Convergence Layers’ for transporting DTN bundles across underlying technologies (TCP, UDP, LTP) –Storage ■ DTN really wants to commit data that cannot be forwarded to persistent storage DTN Info Page 5

© 2009 The MITRE Corporation. All rights reserved. DTN Protocols

© 2009 The MITRE Corporation. All rights reserved. Bundles Built up out of Blocks Page 7 Primary Bundle Block Payload Block Other Block (s) Address information (source, dest, …), treatment flags, QoS marking, creation time, lifetime Other capabilities, e.g. security, extended QoS markings, metadata describing the payload, at-most-one-of-this-kind The application-layer payload

© 2009 The MITRE Corporation. All rights reserved. Primary Bundle Block Page 8

© 2009 The MITRE Corporation. All rights reserved |Status Report| RESERVED|COS| General | Bundle is a fragment Application data unit is an administrative record Bundle must not be fragmented Custody transfer is requested Destination endpoint is a singleton Acknowledgement by application is requested Reserved for future use. The bits in positions 8 and 7 constitute a two-bit priority field : 00 = bulk 01 = normal 10 = expedited 11 is reserved for future use reserved for future use Request reporting of bundle reception Request reporting of custody acceptance Request reporting of bundle forwarding Request reporting of bundle delivery Request reporting of bundle deletion. Bundle Status Control Flags Page 9 Can be used to track the progress of a bundle in the network Signals can be generated but not forwarded (if no route exists) – pull accounting information only if there’s a network error

© 2009 The MITRE Corporation. All rights reserved. Primary Bundle Block: Address Information Page 10 Common strings stored in dictionary with offsets in header. Report-to not necessarily the same as the source. Current custodian marked in header

© 2009 The MITRE Corporation. All rights reserved. Primary Bundle Block: Creation Time and Time To Live Page 11 Timestamps and time-to-live allow bundles to be purged from the network when no longer needed.

© 2009 The MITRE Corporation. All rights reserved. ■The combination of (sending EID, Creation Timestamp, and Creation Timestamp Sequence Number) uniquely identifies a bundle ■Loose time synchronization among nodes is required to support the time-to-live notion –Loose, like, to within 10s of seconds, e.g. ■Some notion of using a countdown time instead of (creation, lifetime) About Time Page 12

© 2009 The MITRE Corporation. All rights reserved |Block type | Block processing ctrl flags (SDNV)| | Block length (SDNV) | / Block body data (variable) / | Flags | Block Processing Control Flags Bit Layout 0 - Block must be replicated in every fragment. 1 - Transmit status report if block can't be processed. 2 - Delete bundle if block can't be processed. 3 - Last block. 4 - Discard block if it can't be processed. 5 - Block was forwarded without being processed. 6 - Block contains an EID-reference field. Extension Blocks Page 13

© 2009 The MITRE Corporation. All rights reserved. NASA DTN-for-2010 Program Page 14

© 2009 The MITRE Corporation. All rights reserved. Deep Impact Network Experiment (DINET) Page 15

© 2009 The MITRE Corporation. All rights reserved. DTN Experimentation Network GRC EVA ION JSC Rover ION GSFC W. Sands ION GSFC L. Relay ION JSC Altair ION MSFC MCC / POCC DTN2/[TCP|UDP] JPL Data Consumer DTN2/[TCP/UDP] APL Data Consumer ION 250ms: 128kbps [>100Mbps] 100ms : 72/k/192k BP / UDP 20ms: 10Mbps BP / UDP BP LTP UDP BP LTP UDP JPL Athlete DTN2 BP / UDP BP / TCP 0:0 20ms : 10Mbps BP LTP UDP BP UDP EIDs: dtn://eva/* EIDs: dtn://athlete/* EIDs: dtn://rover/*EIDs: dtn://altair/*EIDs: dtn://relay/* EIDs: dtn://whitesands/*EIDs: dtn://msfc/* EIDs: dtn://aplsci/* EIDs: dtn://jplsci/*

© 2009 The MITRE Corporation. All rights reserved. ■Network Management ■Time Synchronization ■Routing Protocol Mechanisms Page 17

© 2009 The MITRE Corporation. All rights reserved. DTN Research Group Page 18

© 2009 The MITRE Corporation. All rights reserved. Naming Semantics Page 19