D01-LT: Pending
Rationale
The identified HDTN encapsulation boundary uses Boost.Asio AF_UNIX local sockets on POSIX and duplex named pipes on Windows. On POSIX the creator removes the configured existing socket path and binds a local acceptor; path ownership/access must be provisioned. This component does not itself establish the privilege requirements of the AOS provider, its device driver or continuing helpers. The demo shell script contains no sudo, but that is not a credential/capability execution receipt.
Assessment method
Source review and evidence reconciliation; no new runtime execution
Source context
Pinned HDTN source and retained executed QUIC evidence
Outstanding qualification
Bind an actual AOS virtual-channel packet-service provider and its Encapsulation interface, then map BPv7/BPSec and SABR metadata to the selected all-red LTP composition. The shipped demonstration enters via STCP and leaves via LTP/Encapsulation local sockets; it does not qualify the selected no-IP complete path. The EncapRepeater only forwards encapsulation packets between local streams and is not an AOS frame/channel implementation. Do not infer universal absence of another implementation. Pin OS, provider/device permissions and all helpers, then execute routine communication after permanent privilege drop. A local stream alone is not the complete endpoint.
Public sources
- https://github.com/nasa/HDTN/blob/7fbe90cdbe3c8c737efaacb5985f881f95fc7d2a/common/ltp/src/LtpEncapLocalStreamEngine.cpp
- https://github.com/nasa/HDTN/blob/7fbe90cdbe3c8c737efaacb5985f881f95fc7d2a/common/util/include/EncapAsyncDuplexLocalStream.h
- https://github.com/nasa/HDTN/blob/7fbe90cdbe3c8c737efaacb5985f881f95fc7d2a/tests/test_scripts_linux/test_stcp_to_ltpencap_fast_cutthrough.sh
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round287.html
- round287-sources.json