Differences

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

--- mtrp:tables [2026/06/10 12:52] – created mosh
+++ mtrp:tables [2026/06/10 13:35] (current) – mosh
@@ Line 1: / Line 1: @@
-====== Internal Tables ======
+====== 7. Internal Tables ======
-===== Neighbor Table =====
+===== 7.1 Purpose =====
-Tracks direct peers heard on local transports.
+This document defines the major protocol tables used by MTRP.
-Typical fields:
+===== 7.2 Neighbor Table =====
-  * node ID
-  * egress path ID
+The neighbor table stores direct-neighbor state.
-  * metric
-  * last seen time
+A neighbor entry SHOULD include:
-  * expiry
-  * transport capabilities
+  * destination node identifier
-  * security capabilities
+  * egress path identifier
+  * direct metric
+  * last-seen time
+  * expiry time
+  * capability information
+  * security information
   * reliability counters
-===== Forwarding Table =====
+===== 7.3 Forwarding Table =====
-Tracks learned route candidates.
+The forwarding table stores learned route candidates.
-Typical fields:
+A forwarding entry SHOULD include:
-  * destination node ID
-  * next hop node ID
-  * egress path ID
-  * metric
-  * sequence
-  * expiry
-  * last updated time
-Multiple entries may exist for the same destination.
+  * destination node identifier
+  * next-hop node identifier
+  * egress path identifier
+  * learned metric
+  * sequence value
+  * expiry time
+  * last-updated time
+  * route flags
-===== Preferred Route Table =====
+Multiple entries for the same destination MAY coexist if they differ by next hop, path, or both.
-Tracks forwarding choices selected by policy at send time.
+===== 7.4 Preferred Route Table =====
-Typical fields:
+The preferred route table stores selected forwarding choices.
-  * destination node ID
-  * next hop node ID
+A preferred-route entry SHOULD include:
-  * egress path ID
-  * selected time
+  * destination node identifier
+  * next-hop node identifier
+  * egress path identifier
+  * selected-at time
   * hold-down-until time
-  * in-use flag
+  * in-use state
+The preferred route table is not required to mirror the forwarding table.
+===== 7.5 Message Cache =====
-===== Message Cache =====
+The message cache stores recently seen frames for duplicate suppression.
-Tracks recently seen frames to reduce duplicate processing and rebroadcast loops.
+The cache SHOULD be bounded in size and SHOULD expire entries after a finite time window.