Post #2805495
2026-03-01 17:21 UTC
@py2toz@mastodon.radio Hmm, I am not sure I follow here.
Are you talking about the link layer (L2) protocols for the various transports that IP (L3) sits on top? There are of course a lot of them (starting with SLIP, through Ethernet and ending with complex Wifi and BT protocols).
But surely Reticulum (L3) must have that as well. And this list even says so and shows how to implement your own https://markqvist.github.io/Reticulum/manual/whatis.html#interface-types-and-devices
Data (L4) you transfer on top are link agnostic (per the ISO/OSI model).
Replies (1)
-
@marsik@witter.cz 2026-03-01 17:31
@py2toz@mastodon.radio If the argument is that Reticulum actually implements all of the pieces in a single package, then yes, you are correct. However many of those transports depend on the existing protocols anyway, so I honestly do not see the value in this specific aspect of Reticulum. Using standardized and well known link protocols is easy. It is the routing where the main difference lies. And the crypto of course.