F09-LT: Yes
Rationale
Documentary plausibility: ION critical-bundle forwarding clones the same originating bundle toward distinct eligible route-entry neighbours before loss, and ltpclo services each configured outduct through ltp_send to its destination engine. Non-best-effort output uses LTP_ALL_RED. With overlapping contacts and independently serviceable LTP/Encapsulation/AOS links, these mechanisms plausibly allow useful copies of one communication to progress on concurrent paths; no stop-and-wait requirement between the separate outducts has been identified. Requiring a complete physical-link capture exceeded the requested capability-level evidence standard.
Assessment method
Documentary plausibility; explicit configuration-dependent architectural inference
Source context
Pinned ION critical-bundle forwarding and per-outduct LTP task
Outstanding qualification
Conditional architectural inference, not an observed simultaneous transmission. Requires independently serviceable physical links, overlapping contacts and report-return opportunities for all-red LTP. A shared single serializer/radio can remove concurrency and is not the qualifying configuration. Existing sources demonstrate cloning and separate submission; the complete Encapsulation/AOS integration and on-wire timing have not been tested. No throughput gain, physical path disjointness, deployment readiness or performance guarantee is claimed.
Public sources
- https://github.com/nasa-jpl/ION-DTN/blob/154a4cc7354b26661169f8d8b75a4002cd509a9f/bpv7/ltp/ltpclo.c
- https://github.com/nasa-jpl/ION-DTN/blob/154a4cc7354b26661169f8d8b75a4002cd509a9f/bpv7/ipn/ipnfw.c
- https://github.com/nasa-jpl/ION-DTN/blob/154a4cc7354b26661169f8d8b75a4002cd509a9f/bpv7/doc/pod5/bprc.pod
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round193-sources.json
- round198-sources.json
- round302-sources.json