IP Protocol Stack for Deep Space

DEEPSPACE BOF proposal

Deep space communications involve long delays (e.g., Earth to Mars is 4-20 minutes) and intermittent communications, because of orbital dynamics. The combination of long delays and intermittent communications makes the round-trip time very large and very variable. Space agencies and private sector are planning to deploy IP networks on celestial bodies, such as Moon or Mars, ground, orbits and vicinity. By having the deep space links also IP, it makes a complete end to end IP network. However, given the delays and disruptions, the upper layers such as transport and application protocols have to be profiled to support this environment. While deep space is defined by ITU as 2M km away from Earth, therefore excluding Moon, this work does include Moon deployment.

IP is specified in the current set of lunar relay procurements from US, European, and Japanese space agencies that reference the LunaNet Interoperability Specification(LNIS). IP is also mentioned in the International Communication System Interoperability Standards (ICSIS) for Lunar Gateway mission users. LNIS indicates IP for realtime network data services, and it is applicable not only within the “island” of lunar surface vicinity, but also for direct-with-Earth (DWE) links, and for relaying between proximity and DWE trunk links. The LNIS work is looking to get proper advice from IETF on how to configure IP applications and network services.

Required Details

Information for IAB/IESG

Since IETF117, this group met at each IETF and discussed using the deepspace@ietf.org mailing list. A web site (https://deepspaceip.github.io) archives all presentations and documents. During IETF120 and subsequently on the dtn and deepspace mailing lists, there was a proposal to integrate this work (deep space IP) into the dtn working group through a recharter. The conclusion was that it would be better to have a separate working group.

The dtn working group is working on the same use case but using the Bundle Protocol(BP) stack. Since the publication of RFC4838 which initiated the work on BP, the IP and associated transport stack has evolved to support disconnected devices like IoTs and new transport protocols such as QUIC. This makes a different situation than 25 years ago, and makes IP usable in deep space.

Agenda