F36-MT: No
Rationale
Meshtastic packet priority is a local-device field, not transmitted over the air. The selected firmware uses it to order or replace queued packets; want_ack enables reliability behavior. Neither mechanism carries an application capacity/delay request to transit nodes for resource admission or allocation.
Assessment method
Pinned firmware schema, queue and router source review
Source context
Meshtastic firmware 8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c
Outstanding qualification
Selected standalone LoRa composition only. Local queue acceptance, acknowledgments, retransmission and duty-cycle errors do not form an end-to-end QoS service contract. No custom reservation application or external network service is selected.
Public sources
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/generated/meshtastic/mesh.pb.h
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/Router.cpp
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/MeshPacketQueue.cpp
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/generated/meshtastic/mesh.pb.h
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round687.html