F09-ND: Yes
Rationale
A bounded witness uses one segmented content retrieval with two known segment-name prefixes mapped to distinct Ethernet next hops. The consumer pipelines Interests for the different segments; BestRoute selects the lowest-cost eligible next hop separately for each PIT entry, so distinct useful Data can return concurrently over the two branches. This uses existing static prefix routes, not an added multipath strategy or multiple transport sessions. It requires provisioned routes and concurrent requests: a single prefix with one preferred route does not automatically stripe traffic, and a single Interest is not proactively duplicated. F10 remains No for stock BestRoute.
Assessment method
Constructive static-route and pinned strategy analysis; no runtime execution
Source context
NFD 24.07 BestRoute and prefix route management
Outstanding qualification
Serve two segments of one named object over disjoint Ethernet branches. Install more-specific segment routes and pipeline both Interests before either response. Capture overlapping useful Data, verify signatures and repeat with a single-prefix control. No throughput or scheduler benchmark performed.
Public sources
- https://raw.githubusercontent.com/named-data/NFD/NFD-24.07/daemon/fw/best-route-strategy.cpp
- https://docs.named-data.net/NFD/24.07/manpages/nfdc-route.html
- https://raw.githubusercontent.com/named-data/NFD/NFD-24.07/daemon/table/pit.cpp
- https://raw.githubusercontent.com/named-data/NFD/NFD-24.07/daemon/fw/forwarder.cpp