https://wiki.moshnetworks.com/ 2026-07-22T06:25:32+00:00 https://wiki.moshnetworks.com/ https://wiki.moshnetworks.com/lib/exe/fetch.php?media=wiki:dokuwiki.svg text/html 2026-05-02T03:29:41+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mosh:protocol:layers:transport:addressing&rev=1777692581&do=diff Addressing Addressing defines how frames are directed within a MOSH network. It includes: Network ID and Node ID semantics Unicast, broadcast, and reserved address handling Source and destination interpretation Cross-network considerations (for bridges) text/html 2026-05-02T03:31:27+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mosh:protocol:layers:transport:duplicate_detection&rev=1777692687&do=diff Duplicate Detection Duplicate detection prevents reprocessing of frames that have already been handled. Responsibilities include: Tracking recently seen (source, message_id) pairs Rejecting duplicate frames Supporting idempotent message handling text/html 2026-05-12T02:11:30+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mosh:protocol:layers:transport:fragmentation&rev=1778551890&do=diff Fragmentation MOSH fragmentation allows a logical message payload to be larger than a single on-wire frame. Why Fragmentation Exists The MOSH protocol standard limits the maximum encoded frame size to 1470 bytes. That full frame includes: * 13-byte fixed header text/html 2026-05-15T04:27:50+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mosh:protocol:layers:transport:framing&rev=1778819270&do=diff Framing Overview Framing defines how raw byte streams are structured into discrete MOSH frames. Responsibilities include: Start-of-frame detection (SOF) Field layout and byte ordering Payload length encoding CRC calculation and validation Frame boundary recovery in noisy streams text/html 2026-05-02T03:32:41+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mosh:protocol:layers:transport:medium_adapter&rev=1777692761&do=diff Medium Adapter The Medium Adapter provides the interface between the MOSH transport layer and the physical transport mechanism. Examples include: UART / Serial ESP-NOW nRF24L01 TCP/UDP (for bridges) Responsibilities include: Sending raw byte buffers Receiving raw byte buffers Handling transport-specific constraints (MTU, timing, buffering) text/html 2026-05-02T03:30:59+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mosh:protocol:layers:transport:reliability&rev=1777692659&do=diff Reliability / Delivery This component defines how MOSH ensures (or does not ensure) delivery of frames. Delivery modes may include: Best-effort (no guarantees) Acknowledged delivery (ACK-based) Retry with timeout policies Responsibilities include: text/html 2026-05-02T03:31:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mosh:protocol:layers:transport:ttl_hop_handling&rev=1777692717&do=diff TTL / Hop Handling TTL (Time-To-Live) limits how far a frame can propagate through the network. Responsibilities include: Decrementing TTL on each hop Dropping frames when TTL reaches zero Determining whether local processing occurs before or after TTL checks