Selected Results from the REDMARS2 Project: Recursive Delay-Tolerant Networking using Bundle-in-Bundle Encapsulation

TL;DR

The paper investigates transferring Recursive Internetwork Architecture concepts to Delay- and Disruption-Tolerant Networking to address scalability and separation of concerns in challenged networks. It proposes a recursive DTN stack based on Bundle-in-Bundle Encapsulation (BIBE) to create scope-based overlays that isolate routing and topology information per layer. The authors present a reference implementation using µD3TN and report field-test validation with ESA assets, including a Solar System Internet–like UAV-satellite scenario. Findings show BIBE can bridge heterogeneous DTN underlays, enabling scalable, recursive, and interoperable DTN architectures with practical applicability.

Abstract

This whitepaper presents parts of the results of the REDMARS2 project conducted in 2021-2022, exploring the integration of Recursive Internetwork Architecture (RINA) concepts into Delay- and Disruption-Tolerant Networking (DTN) protocols. Using Bundle-in-Bundle Encapsulation (BIBE), we implemented scope-based separation mechanisms resulting in scalable DTNs. A key contribution of this work is the demonstration of practical BIBE-based use cases, including a realistic Solar System Internet communication scenario involving unmanned aerial vehicles (UAVs) and satellite relays. The evaluation, supported by field tests in collaboration with the European Space Agency (ESA), confirmed the viability of BIBE as a foundation for scalable, recursive, and interoperable DTN architectures.

Figures (7)

• Figure 1: A simple scenario with 3 nodes and 2 scopes. In addition, the encapsulation of the initially created Bundle during transition to a lower scope and the decapsulation during transition to a higher scope are illustrated.
• Figure 2: An example scenario with 5 nodes, where there is an overlay scope and two underlying scopes on the lower layer, which do not share any topological or routing information. Accordingly, there are three independent sets of topology information.
• Figure 3: Illustration of BIBE Bundle forwarding via a node that is a member of multiple scopes. Note that the Bundle is not returned to the same µD3TN instance that forwarded the Bundle to Scope 1.
• Figure 4: Schematic representation of the individual nodes in the evaluation scenario and the path that Bundles take from the source to the destination node.
• Figure 5: Visualization of the experimental setup, including the services and functionalities localized on the drones, as well as the monitoring. The remote controllers were only connected to the drones for safety backup and were not used for control during the field test.