F38-RT: Yes
Rationale
Each Reticulum interface can independently configure its announce bandwidth cap. Interface.process_announce_queue enforces spacing from packet size, interface bitrate and that cap, selects lower-hop announcements first and discards stale queued entries. Local operators therefore enforce different resource policies on connected transport scopes.
Assessment method
Versioned native source and official API review
Source context
Reticulum 1.5.5 and selected Meshtastic firmware source
Outstanding qualification
Witness is native announcement traffic on serial transport interfaces, not arbitrary per-application data reservations. Configuration must reflect the interface bitrate. Independent per-interface enforcement satisfies the criterion without requiring recursive RINA scopes or a network-wide uniform budget.
Public sources
- https://github.com/markqvist/Reticulum/blob/1.5.5/RNS/Interfaces/Interface.py
- https://github.com/markqvist/Reticulum/blob/1.5.5/RNS/Resource.py
- https://reticulum.network/manual/reference.html
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round686.html