Differences

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

--- mtrp:overview [2026/06/10 12:50] – created mosh
+++ mtrp:overview [2026/06/10 13:09] (current) – mosh
@@ Line 1: / Line 1: @@
-====== Overview ======
+====== 1. Overview ======
-MTRP is designed to let a node speak over one or more transports while presenting one routing model to higher layers.
+===== 1.1 Purpose =====
-===== High-Level Behavior =====
+This document defines the high-level operating model of MTRP.
-  * nodes discover direct neighbors
+===== 1.2 System Model =====
-  * nodes advertise reachable destinations
-  * neighbors learn route candidates
-  * send-time resolution chooses a direct or forwarded path
-  * metrics are additive across hops
-===== Design Priorities =====
+An MTRP node MAY register one or more transports. Each registered transport is treated as a path usable by the routing layer.
-  * bounded memory use
+MTRP separates:
-  * explicit tables and predictable behavior
-  * transport independence
-  * support for constrained and full-capability devices
-===== Important Distinction =====
+  * direct-neighbor knowledge
+  * learned forwarding knowledge
+  * send-time forwarding preference
-MTRP separates knowledge from choice.
+===== 1.3 Core Terms =====
-  * the forwarding table is what the node knows
+==== 1.3.1 Path ====
-  * the preferred route table is what the node chose to use during forwarding
-===== Current Non-Goals =====
+A ''path'' is a registered transport instance exposed to the routing layer.
-  * end-to-end reliability
+==== 1.3.2 Neighbor ====
-  * multicast reliability
-  * automatic topology optimization
+A ''neighbor'' is a node reachable directly on a local path.
-  * fragmentation-aware reliable delivery
+==== 1.3.3 Learned Route ====
+A ''learned route'' is a route candidate derived from an advertisement received from another node.
+==== 1.3.4 Preferred Route ====
+A ''preferred route'' is a forwarding decision selected by policy during send-time route resolution.
+===== 1.4 Architectural Separation =====
+The forwarding table represents what a node knows.
+The preferred route table represents what a node has selected to use.
+This distinction is intentional and MUST be preserved when interpreting diagnostics.
+===== 1.5 Current Boundaries =====
+The current protocol does not define:
+  * end-to-end reliable delivery semantics
+  * reliable group delivery semantics
+  * dynamic topology-map distribution
+  * complete fragmentation and reassembly behavior