User Tools

Site Tools


mtrp:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
mtrp:start [2026/06/10 13:06] – created moshmtrp:start [2026/06/10 13:37] (current) – [4.1 Specification] mosh
Line 1: Line 1:
 ====== MTRP ====== ====== MTRP ======
  
-MTRP is a lightweight multi-transport routing protocol for MOSH-class embedded nodes.+===== 1Purpose =====
  
-===== Goals =====+MTRP is a lightweight multi-transport routing protocol intended for resource-constrained embedded systems and MOSH-class nodes.
  
-  * Support small embedded nodes with limited RAM and flash. +===== 2Design Objectives =====
-  * Allow multiple transport backends under one routing layer. +
-  * Prefer simple, explainable behavior over hidden complexity. +
-  * Scale from direct-neighbor messaging to multi-hop forwarding.+
  
-===== Current Scope =====+MTRP is designed to:
  
-MTRP currently includes:+  * provide a common routing layer across heterogeneous transports 
 +  * support direct-neighbor and multi-hop forwarding behavior 
 +  * operate within constrained RAM and flash budgets 
 +  * favor explicit and inspectable state over opaque internal behavior 
 + 
 +===== 3. Scope ===== 
 + 
 +The current documented scope of MTRP includes:
  
   * neighbor discovery   * neighbor discovery
-  * learned route advertisement+  * route advertisement and learning
   * forwarding table maintenance   * forwarding table maintenance
-  * route-selection policy behavior +  * route selection policy 
-  * preferred-route tracking at send time +  * send-time preferred-route selection 
-  * compact-header support for constrained transports+  * support for compact operation on constrained transports
  
-===== Core Concepts =====+===== 4. Document Index =====
  
-  * ''Neighbor table'': direct peers heard on a local transport +==== 4.1 Specification ====
-  * ''Forwarding table'': learned route candidates for destinations +
-  * ''Preferred route table'': route choices actually selected during forwarding +
-  * ''Path'': a registered transport instance +
-  * ''Metric'': lower is better+
  
-===== Documentation =====+  * [[mtrp:overview|1. Overview]] 
 +  * [[mtrp:frame_format|2. Frame Format]] 
 +  * [[mtrp:messages|3. Control Messages]] 
 +  * [[mtrp:addressing|4. Addressing]] 
 +  * [[mtrp:routing|5. Routing Behavior]] 
 +  * [[mtrp:policies|6. Routing Policies]] 
 +  * [[mtrp:tables|7. Internal Tables]] 
 +  * [[mtrp:transports|8. Transport Model]] 
 +  * [[mtrp:security|9. Security Model]] 
 + 
 +==== 4.2 Operations ====
  
-  * [[mtrp:overview|Protocol Overview]] 
-  * [[mtrp:frame_format|Frame Format]] 
-  * [[mtrp:routing|Routing Behavior]] 
-  * [[mtrp:policies|Routing Policies]] 
-  * [[mtrp:tables|Internal Tables]] 
   * [[mtrp:diagnostics|Diagnostics]]   * [[mtrp:diagnostics|Diagnostics]]
-  * [[mtrp:transports|Transport Support]] 
-  * [[mtrp:security|Security]] 
   * [[mtrp:testing|Testing]]   * [[mtrp:testing|Testing]]
-  * [[mtrp:roadmap|Roadmap]] 
   * [[mtrp:faq|FAQ]]   * [[mtrp:faq|FAQ]]
- +  * [[mtrp:notes|Implementation Notes]] 
-[[mtrp:sidebar|sidebar]]+  [[mtrp:roadmap|Roadmap]]
/var/www/wiki.moshnetworks.com/data/attic/mtrp/start.1781096771.txt.gz · Last modified: by mosh

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki