F29-MT: No
Rationale
The selected Meshtastic message service addresses a node or channel. MeshPacket.id identifies a sender packet, and Data.request_id/reply_id correlate routing reports or responses. These fields do not bind a named content reference to supplier discovery or cache selection. The selected direct-message/channel composition contains no content-reference retrieval service.
Assessment method
Pinned firmware source and primary documentation; no runtime test
Source context
Meshtastic selected firmware 8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c
Outstanding qualification
A channel broadcast can reach many participants, and an added application could ask them for content. That added request/response convention is not part of the declared composition. Node discovery, packet correlation and payload signatures do not independently supply F29. Store-and-forward is explicitly disabled; its separate history feature is not silently added to this profile.
Public sources
- https://raw.githubusercontent.com/meshtastic/firmware/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/generated/meshtastic/mesh.pb.h
- https://raw.githubusercontent.com/meshtastic/firmware/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/modules/StoreForwardModule.cpp
- https://meshtastic.org/docs/configuration/module/store-and-forward-module/
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round480.html
- round480-sources.json