mtrp:frame_format
This is an old revision of the document!
Table of Contents
Frame Format
MTRP frames consist of:
- protocol header
- payload
- transport metadata used locally during processing
Header Responsibilities
The header carries protocol-visible information such as:
- version
- flags
- network ID
- origin node ID
- destination node ID
- previous hop node ID
- message ID
- TTL
Compact Operation
On constrained transports, MTRP may use a compact on-wire representation.
Compact mode is intended to preserve core routing behavior while reducing header cost on limited links such as NRF24-class paths.
Important Note
Transport metadata used internally for routing decisions is not the same as the serialized on-wire header.
Examples of local metadata include:
- ingress path ID
- ingress path metric
- resolved egress path ID
- resolved next hop
/var/www/wiki.moshnetworks.com/data/attic/mtrp/frame_format.1781096006.txt.gz · Last modified: by mosh