F28-RT: No
Rationale
The selected Reticulum 1.5.5 Link composition addresses a destination and relies on Transport path state populated by announces and path requests. Requesting discovery on an interface, inspecting hop information or choosing local access does not specify or exclude downstream transport nodes. No endpoint-controlled source-route or intermediary-selection mechanism is selected.
Assessment method
Primary specification and pinned code review; no runtime experiment
Source context
Reticulum Transport path selection and CCNx forwarding semantics
Outstanding qualification
The request_path interface parameter restricts where a discovery request is sent; it is not an enforced path description. Forwarders continue to use their own next-hop state. This does not deny route discovery, route replacement or the ability to inspect some path information. A separately implemented overlay or administrative topology constraint would be additional functionality, not the selected native endpoint service.
Public sources
- https://reticulum.network/manual/reference.html
- 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.
- round514.html
- round514-sources.json