F09-RA: Yes
Rationale
The newly explicit redundant-path mode carries the same communication concurrently through distinct next hops. Each branch transports a useful copy toward the same receiving IPCP, unlike sequential mobility failover or per-flow ECMP. The earlier No assessed the default single-path mode and is superseded by this declared composition change.
Assessment method
Pinned source call-chain inspection with explicit native policy selection; no execution
Source context
IRATI static routing, forwarding-table generator, default PFF and RMT
Outstanding qualification
This credits simultaneous redundant transport, not throughput aggregation or striping. Distinct next hops alone do not guarantee disjoint failure domains; provision the downstream paths accordingly. DTCP-enabled DTP rejects sequence numbers at or below its receive-window edge, but complete duplicate/reordering behavior, startup races and failure recovery have not been exercised here.
Public sources
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/rinad/src/ipcp/plugins/default/static-routing-ps.cc
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/rinad/src/ipcp/plugins/default/resource-allocator-ps.cc
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/kernel/pff-ps-default.c
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/kernel/rmt.c
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/kernel/dtp.c
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round664.html