Back to matrix

F20-RT: No

Rationale

The selected Reticulum Link profile uses transit link_table entries keyed by Link ID. Transport creates these entries while forwarding Link requests, stores ingress/egress interfaces and hop/proof state, and uses them for subsequent Link traffic until expiry. This is end-to-end Link-specific forwarding state, distinct from shared destination routes and adjacency state.

Assessment method

Documentary/code analysis

Source context

Primary routing specification / pinned transport code

Public sources