mtrp:transports
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| mtrp:transports [2026/06/10 13:12] – mosh | mtrp:transports [2026/06/10 13:36] (current) – mosh | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| - | ===== 6.1 Purpose ===== | + | ===== 8.1 Purpose ===== |
| This document defines how MTRP interacts with underlying transports. | This document defines how MTRP interacts with underlying transports. | ||
| - | ===== 6.2 Transport Abstraction ===== | + | ===== 8.2 Transport Abstraction ===== |
| MTRP is transport-agnostic at the routing layer. | MTRP is transport-agnostic at the routing layer. | ||
| Line 11: | Line 11: | ||
| 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. | 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. | ||
| - | ===== 6.3 Path Properties ===== | + | ===== 8.3 Path Properties ===== |
| A path SHOULD provide: | A path SHOULD provide: | ||
| Line 22: | Line 22: | ||
| * transport state | * transport state | ||
| - | ===== 6.4 Multiple Paths ===== | + | ===== 8.4 Multiple Paths ===== |
| A node MAY register multiple paths simultaneously. | A node MAY register multiple paths simultaneously. | ||
| Line 28: | Line 28: | ||
| The routing layer MAY use those paths independently or comparatively during send-time route resolution. | The routing layer MAY use those paths independently or comparatively during send-time route resolution. | ||
| - | ===== 6.5 Transport Modes ===== | + | ===== 8.5 Transport Modes ===== |
| Transport modes allow the routing layer to distinguish between different operational capabilities. | Transport modes allow the routing layer to distinguish between different operational capabilities. | ||
| Line 42: | Line 42: | ||
| A node MAY participate as a fully capable router while one of its registered transports operates under constrained rules. | A node MAY participate as a fully capable router while one of its registered transports operates under constrained rules. | ||
| - | ===== 6.6 Metric Contribution ===== | + | ===== 8.6 Metric Contribution ===== |
| Each path contributes a local metric. | Each path contributes a local metric. | ||
| Line 48: | Line 48: | ||
| When routes are relayed, the effective metric of the learned route SHOULD reflect additive hop cost. | When routes are relayed, the effective metric of the learned route SHOULD reflect additive hop cost. | ||
| - | ===== 6.7 Transport Diversity ===== | + | ===== 8.7 Transport Diversity ===== |
| The transport abstraction is intended to support heterogeneous links. | The transport abstraction is intended to support heterogeneous links. | ||
| Line 60: | Line 60: | ||
| * future Wi-Fi or Bluetooth-capable transports | * future Wi-Fi or Bluetooth-capable transports | ||
| - | ===== 6.8 Current Boundaries ===== | + | ===== 8.8 Current Boundaries ===== |
| The transport model does not yet fully define: | The transport model does not yet fully define: | ||
/var/www/wiki.moshnetworks.com/data/attic/mtrp/transports.1781097158.txt.gz · Last modified: by mosh