F28-CJ: No
Rationale
The cjdns column explicitly selects the ordinary IPv6 application path without custom route-label overrides. In the pinned SessionManager, a missing label is filled from the selected session path. The ordinary endpoint service therefore relies on internal path selection rather than an application-supplied intermediary constraint.
Assessment method
Primary specification and pinned code review; no runtime experiment
Source context
QUIC migration, libp2p Circuit Relay and cjdns route labels
Outstanding qualification
cjdns has real source-route labels: SessionManager can preserve a supplied label and SwitchCore processes it. The No is limited to the explicitly selected application interface, not the absence of source routing in cjdns. A qualified route-label injection interface could be assessed separately, including how the endpoint obtains valid labels and how failures are handled. No underlay-hop visibility or runtime path-enforcement result is inferred.
Public sources
- https://raw.githubusercontent.com/cjdelisle/cjdns/f5902acab6dd2f1a68bf6e4c89e352ed71f93698/net/SessionManager.c
- https://raw.githubusercontent.com/cjdelisle/cjdns/f5902acab6dd2f1a68bf6e4c89e352ed71f93698/switch/SwitchCore.c
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round515.html
- round515-sources.json