Differences

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

--- mtrp:transports [2026/06/10 12:55] – created mosh
+++ mtrp:transports [2026/06/10 13:36] (current) – mosh
@@ Line 1: / Line 1: @@
-====== Transports ======
+====== 8. Transport Model ======
-MTRP is transport-agnostic at the routing layer. A transport is registered as a path and contributes local capabilities and metric behavior.
+===== 8.1 Purpose =====
-===== Path Model =====
+This document defines how MTRP interacts with underlying transports.
-Each registered transport becomes a path.
+===== 8.2 Transport Abstraction =====
-A path provides:
+MTRP is transport-agnostic at the routing layer.
-  * a transport implementation
+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.
+===== 8.3 Path Properties =====
+A path SHOULD provide:
+  * transport instance binding
   * transport mode
   * maximum frame length
   * maximum payload length
-  * metric
+  * path metric
-  * current state
+  * transport state
-===== Full and Constrained Modes =====
+===== 8.4 Multiple Paths =====
-MTRP supports the idea of transport-level capability differences.
+A node MAY register multiple paths simultaneously.
-Examples:
+The routing layer MAY use those paths independently or comparatively during send-time route resolution.
-  * full-capability paths
+===== 8.5 Transport Modes =====
-  * constrained paths with compact headers
-  * bridge nodes using both constrained and full transports
-===== Current Examples =====
+Transport modes allow the routing layer to distinguish between different operational capabilities.
+Examples include:
+  * full-capability operation
+  * constrained operation
+  * inactive or unavailable operation
+A node role and a transport role are distinct concepts.
+A node MAY participate as a fully capable router while one of its registered transports operates under constrained rules.
+===== 8.6 Metric Contribution =====
+Each path contributes a local metric.
+When routes are relayed, the effective metric of the learned route SHOULD reflect additive hop cost.
+===== 8.7 Transport Diversity =====
+The transport abstraction is intended to support heterogeneous links.
 Examples of intended or existing transport families include:
@@ Line 33: / Line 57: @@
   * ESP-NOW v2
   * NRF24-class links
-  * serial
+  * serial transports
-  * future Wi-Fi or Bluetooth-capable links
+  * future Wi-Fi or Bluetooth-capable transports
-===== Important Design Point =====
-Node role and transport role are separate concerns.
-A node may be fully capable overall while one of its paths is constrained.
+===== 8.8 Current Boundaries =====
-===== Metric Use =====
+The transport model does not yet fully define:
-Each path contributes a local metric. Multi-hop learned routes accumulate metric cost as advertisements are relayed.
+  * cross-transport fragmentation behavior
+  * transport-specific reliability semantics
+  * transport-aware end-to-end acknowledgment behavior
+  * formal bridge-policy coordination