S03-LT: No
Rationale
The selected LTP composition includes the AOS space-link profile. AOS 732.0-B-4 sections 1.1 and 1.6 define its deployment over spacecraft-to-ground or spacecraft-to-spacecraft links; section 4.1.2.2.3 requires the SCID field and refers its assignment to SANA. CCSDS 320.0-M-7 Cor. 1 section 3.4.1 places Q-SCID assignment with SANA, with uniqueness scoped by frame version, frequency band and assignment period. Thus the selected operational space-link composition has an external identifier-allocation dependency even when BP endpoints, LTP engine mappings and cryptographic keys are locally configured. This settles S03 as No for this composition.
Assessment method
Selected operational-profile scope and normative assignment rule
Source context
AOS 732.0-B-4 and CCSDS 320.0-M-7 Cor. 1 assignment procedures
Outstanding qualification
Section 2 of the assignment procedure explicitly delegates simulation/testing and non-radiating ground simulators or assemblies to local management; section 3.4.6 also allows simulator self-assignment without RF radiation. This exception is preserved, but is not an operational spacecraft-link witness for the selected AOS column. A laboratory or terrestrial reuse of AOS bytes is not silently substituted for that deployment. The decision does not require public IP addresses or DNS, and does not apply to LTP or BPv7 in isolation. It is a documentary inference from the selected space-link scope and explicit assignment rule, not an executed deployment or an assertion that local SCID values cannot be encoded.
Public sources
- https://ccsds.org/Pubs/732x0b4.pdf
- https://ccsds.org/wp-content/uploads/gravity_forms/5-448e85c647331d9cbaf66c096458bdd5/2025/01/320x0m7c1.pdf
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round636.html
- round636-sources.json
- round195-sources.json