F32-RA: No
Rationale
The selected link-state/Dijkstra policy computes forwarding from the known connectivity graph. Its routing inputs do not represent future contact intervals and usable transfer volumes, and its computation does not account for item feasibility over such intervals. QoS flow allocation and programmed access handovers do not add contact-plan route computation.
Assessment method
Pinned forwarding, queue-lifecycle and routing-source inspection with selected-policy documentation
Source context
IRATI RMT, DTP and link-state routing source; normal-DIF configuration
Outstanding qualification
No for the selected routing policy. Alternative time-dependent routing could be implemented as another policy, but is not part of this column. This does not deny QoS-aware flow allocation or current-topology route repair. No execution or capacity benchmark.
Public sources
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/rinad/src/ipcp/plugins/default/routing-ps.cc
- https://raw.githubusercontent.com/wiki/IRATI/stack/configurations/tutorial1/system1/default.dif
- https://raw.githubusercontent.com/wiki/IRATI/stack/Flow-Allocation.md
- https://arxiv.org/abs/2510.27325
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round659.html