Hi All,
It is worth noting that there is no accomdation for Bundle Protocol based
networks in the TIPTOP formulation; indeed, for some period, and perhaps
still, any network architecture including a BP based element has been
essentially banned from discussion in the TIPTOP WG.
For those unfamiliar, BP is standardized by both the IETF (RFC 9171) and
the CCSDS. Further, Bundle based store and forward capabilities, among
others, are specified in the LNIS (Lunar Network Interoperability
Specification) which is essentially the governing document for Artemis
interoperability. BP should be considered a complete, discreet network
stack which can operate as an overlay across a great many network types,
including Internet. but is specifically designed to overcome high latency
and disrupted environments, such as one would encounter in Solar System
wide networking.
A method inclusive of BP networks for deep space use and IP networks for
planetary surfaces (where latency does not impact efficacy) has been well
discussed and developed inside the IPNSIG (Interplanetary Chapter of
ISOC). In this model, off world IP networks are termed "internets" as
opposed to the Internet, which describes the existing global network out
to GEO. Transit between the Internet and internets happens
at an application layer using Application Layer Gateways to perfect
multi-world interoperability for generally IP based services; no direct IP
connectivity should be implied. All together, this architecture allows
robust local IP service on any world, and interoperability between IP
networks on other worlds via an intermediary BP network.
This model has demonstrated multi-planet interoperable DNS, as well as
SMTP as an example service which is functional using Application Layer
Gateways. It is notable that, under this model, off-world IP network
addresses are not intended to be routable between one another, nor to the
Internet, given the intervening BP networks, and the requirements for
successful operation in high latency/disrupted path conditions. Put
simply, the rules for networked application development are far different
in such challenged environments, and would lead to fundamental breakage of
dynamic IP routing. To overcome this, some pun intended, I view off world
IP network addresses as "martians" when considering managing routing
filters.
It is important that any addressing convention arrived at for off-world
networks considers all the viable methods of deploying IP services on
other worlds, and perfecting interoperability between same. We must see
the forest _and_ the trees to arrive at a viable solution.
Sincerely,
Scott Johnson
On Fri, 20 Feb 2026, Tony Li wrote:
Hi Fernando,
On Feb 20, 2026, at 7:43 AM, Fernando Frediani - fhfrediani at gmail.com
<[email protected]> wrote:
I am following this and not beleiving this is serious. Forgive me if not but it
looks like April's fools day
This is quite serious. Space agencies are already using IP for space missions.
That only looks to expand. Today they are using random IPv4 allocations from
their own prefixes. They foresee many additional missions and collaboration
between agencies to provide communications backup. If nothing changes, this
will become another swamp.
Folks are welcome to attend the TIPTOP WG meeting and meet the folks working on
this.
Cheers,
Tony
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.
