We are glad to share that the IPNSIG Architecture and Governance Working Group (AWG) held a workshop on Routing in Delay and Disruption Tolerant Networking over four days, from August 22 to 25, 2022. The goal of the workshop was to look at the various routing approaches and to produce a recommendation toward realizing a common interplanetary network architecture.
During the workshop, the group looked into the following routing approaches:
- Routing in European Space Agency (ESA) Bundle Protocol (BP) Implementation, presented by Felix Flentge
- Schedule-Aware Bundle Routing (SABR), also known as Contact Graph Routing (CGR), presented by Scott Burleigh
- REDMARS Routing, presented by Marius Feldmann and Felix Walter
- Spacetime Routing, presented by Brian Barritt
- Shortest-Path Tree Routing for Space Networks (SPSN), presented by Olivier de Jonckere)
- Opportunistic forwarding approaches – constrained flooding
PROPHeT, Spray and Wait, presented by Juan Fraire
Opportunistic CGR, presented by Scott Burleigh
Inter-Regional Forwarding, presented by Scott Burleigh
As a result, AWG has produced the following recommendation:
The IPNSIG, as an organization under the Internet Society, advocates the concept of establishing a common, interoperable, autonomous and scalable routing framework within the Solar System Internet. We believe this is crucial to achieving a resilient and sustainable communication environment in space.
We express our willingness to facilitate and expect interested communities to further pursue the refinement and advancement of a technical solution in support of this goal.
We underline four important aspects for the future of Routing in Solar System Internet:
The overall goal is to populate forwarding tables or routing tables (where appropriate) without human intervention and depart from the Earth-centric management scheme
To enable Autonomy we need a common and standardized way of the following:
The population of a Forwarding and (where routes are computed) Routing Table
- Function enabling the bundle protocol agent to access a forwarding table API that answers the question: “where should I send this bundle and with what CLA/address?”, similar to ARP lookup Interoperability
- Define a common to every Node set of functions
Inter-regional routing should be based on a common standard
- Intra-regional routing could be heterogeneous, adopting methods that suit the needs of a specific environment or a mission
- Inter- and Intra-region routing should be interoperable
Architecture needs to be structured in some way (Hierarchy)
Node IDs, Addressing Schemes, and segmenting concepts need to be further explored to accommodate the scale of the SSI
You can find the summary report here and our recommendations report here.