F35-RT: Yes
Archived previous-definition assessment — revision 5.73. Retired in 5.82; excluded from the active matrix and counts. This historical verdict is not a current assessment.
Rationale
Reticulum 1.5.5 exposes enable_transport on an intermediate instance. Enabling it adds forwarding for other peers, path-request handling and announce propagation. A node attached to two serial segments can thereby connect destinations previously confined to their respective segments, while the existing endpoint stacks and Link applications remain unchanged.
Assessment method
Primary specification review; no runtime experiment
Source context
Reticulum 1.5.5 and NFD 24.07 documentation and pinned code
Outstanding qualification
Before/after witness: a two-interface intermediate node changes from non-transport to transport-enabled operation. Both serial interfaces, compatible IFAC credentials, announce propagation and resource limits must be configured; endpoint Link.identify policies remain in force. Endpoints still perform normal discovery and link establishment with their existing software. This is routed Reticulum connectivity, not a transparent layer-2 bridge, endpoint software installation, automatic hardware provisioning or a global-scale result. Retain the selected no-IP and private-tmpfs operation. No runtime execution.
Public sources
- https://reticulum.network/manual/networks.html
- https://raw.githubusercontent.com/markqvist/Reticulum/1.5.5/RNS/Reticulum.py
- https://raw.githubusercontent.com/markqvist/Reticulum/1.5.5/RNS/Transport.py
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round521.html
- round521-sources.json