D03-LT: No
Rationale
The selected column is BPv7/BPSec over LTP, Encapsulation and operational AOS space links, not LTP over an ordinary IP interface. AOS 732.0-B-4 sections 1.1 and 1.6 define spacecraft/ground and spacecraft/spacecraft links; section 2.4 assumes lower-layer transfer services. An endpoint participating directly in that operational space link requires suitable space-link communications hardware. An ordinary Ethernet or Wi-Fi NIC alone does not supply that link. Under D03, this mandatory carrier constraint makes the selected composition No, using the same rule applied to the selected LoRa and IEEE 802.15.4 compositions.
Assessment method
Selected-carrier hardware inference; no runtime execution
Source context
AOS B-4 scope and lower-layer assumptions; CCSDS protocol overview; NASA SDR example
Outstanding qualification
This is a scope-based documentary inference for the selected operational AOS binding, consistent with S03-LT. AOS section 1.2 leaves implementation methods and products unspecified: no particular radio, FPGA, accelerator or secure element is claimed mandatory. LTP and AOS frame processing can run in software on commodity CPUs. A simulator, ground-only byte transport, remote radio gateway or LTP-over-UDP configuration is not substituted for the selected direct space-link endpoint. The NASA SDR example uses earlier AOS B-2 and illustrates hardware/software separation only; it is not a complete B-4/BPv7/BPSec interoperability witness. No new hardware or runtime test was executed.
Public sources
- https://ccsds.org/Pubs/732x0b4.pdf
- https://ccsds.org/Pubs/130x0g2s.pdf
- https://software.nasa.gov/software/LEW-19723-1
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round638.html
- round636.html