https://wiki.moshnetworks.com/ 2026-07-22T04:39:25+00:00 https://wiki.moshnetworks.com/ https://wiki.moshnetworks.com/lib/exe/fetch.php?media=wiki:dokuwiki.svg text/html 2026-06-10T13:32:00+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mtrp:addressing&rev=1781098320&do=diff 4. Addressing and Claim Behavior 4.1 Purpose This document defines the current address-selection and address-claim behavior of MTRP. 4.2 Scope This document describes: * local node address selection * dynamic address claiming * conflict detection and response text/html 2026-06-10T13:11:05+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mtrp:diagnostics&rev=1781097065&do=diff Diagnostics 1. Purpose This document describes the intended interpretation of MTRP diagnostic output. 2. Summary Output The summary output SHOULD provide a concise view of current router state, including: * device identifier * local node identifier text/html 2026-06-10T12:58:11+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mtrp:faq&rev=1781096291&do=diff FAQ Why are there more active routes than neighbors? Because the forwarding table stores route candidates, not just one best route per destination. A single destination may appear multiple times with different next hops. Why is the preferred route table empty? text/html 2026-06-10T13:17:19+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mtrp:frame_format&rev=1781097439&do=diff 2. Frame Format 2.1 Purpose This document defines the on-wire frame structure currently used by MTRP. 2.2 Scope This document describes: * the serialized MTRP header * payload placement * optional CRC placement * compact and native header formats text/html 2026-06-10T13:27:30+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mtrp:messages&rev=1781098050&do=diff 3. Control Messages 3.1 Purpose This document defines the current MTRP control-message payload format and the control-plane message types presently recognized by the implementation. 3.2 Scope This document covers: * control-message payload structure text/html 2026-06-10T13:09:40+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mtrp:overview&rev=1781096980&do=diff 1. Overview 1.1 Purpose This document defines the high-level operating model of MTRP. 1.2 System Model An MTRP node MAY register one or more transports. Each registered transport is treated as a path usable by the routing layer. MTRP separates: text/html 2026-06-10T13:35:12+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mtrp:policies&rev=1781098512&do=diff 6. Routing Policies 6.1 Purpose This document defines the policy controls that influence route selection behavior. 6.2 Outbound Path Selection Outbound path selection applies to direct-neighbor candidates. 6.2.1 FIRST_VALID The implementation MUST retain the first usable candidate encountered during evaluation. text/html 2026-06-10T12:56:42+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mtrp:roadmap&rev=1781096202&do=diff Roadmap This page describes likely next steps for MTRP development. Near-Term Candidates * hop-by-hop reliable unicast ACK * reliability-aware routing refinement * better diagnostics and event reporting * improved testing around route flaps and failover text/html 2026-06-10T13:34:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mtrp:routing&rev=1781098473&do=diff 5. Routing Behavior 5.1 Purpose This document defines how MTRP learns, stores, and selects routes. 5.2 Direct Neighbor Reachability A destination that is reachable directly on a registered local path MUST be treated as a neighbor candidate. Direct-neighbor state MUST be stored in the neighbor table. text/html 2026-06-10T13:36:38+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mtrp:security&rev=1781098598&do=diff 9. Security Model 9.1 Purpose This document defines the current security posture and intended security boundaries of MTRP. 9.2 Design Intent MTRP is intended to operate across a range of node classes, from constrained devices to more capable bridge or core nodes. text/html 2026-06-10T13:33:26+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mtrp:sidebar&rev=1781098406&do=diff MTRP * MTRP Home Specification * 1. Overview * 2. Frame Format * 3. Control Messages * 4. Addressing * 5. Routing Behavior * 6. Routing Policies * 7. Internal Tables * 8. Transport Model * 9. Security Model Operations * Diagnostics * Testing * FAQ * Implementation Notes Planning * Roadmap text/html 2026-06-10T13:37:27+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mtrp:start&rev=1781098647&do=diff MTRP 1. Purpose MTRP is a lightweight multi-transport routing protocol intended for resource-constrained embedded systems and MOSH-class nodes. 2. Design Objectives MTRP is designed to: * provide a common routing layer across heterogeneous transports text/html 2026-06-10T13:35:36+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mtrp:tables&rev=1781098536&do=diff 7. Internal Tables 7.1 Purpose This document defines the major protocol tables used by MTRP. 7.2 Neighbor Table The neighbor table stores direct-neighbor state. A neighbor entry SHOULD include: * destination node identifier * egress path identifier text/html 2026-06-10T12:55:14+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mtrp:testing&rev=1781096114&do=diff Testing MTRP testing is best done in layers. Start with direct-neighbor behavior, then verify forwarding, then verify policy behavior. Basic Bring-Up Expected checks: * node claims an address * hello traffic is visible * direct neighbors appear in the neighbor summary text/html 2026-06-10T13:36:09+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.moshnetworks.com/doku.php?id=mtrp:transports&rev=1781098569&do=diff 8. Transport Model 8.1 Purpose This document defines how MTRP interacts with underlying transports. 8.2 Transport Abstraction MTRP is transport-agnostic at the routing layer. A registered transport is represented as a path. Each path provides the routing layer with the information necessary to send, receive, and characterize traffic over that transport.