F35-SC: Yes
Archived previous-definition assessment — revision 5.73. Retired in 5.82; excluded from the active matrix and counts. This historical verdict is not a current assessment.
Rationale
SCION separates infrastructure path discovery and registration from endpoint path lookup and combination. Adding a permitted inter-AS link and registering the resulting segments can make a new forwarding path available to existing SCION endpoints without changing their implementations or UDP applications.
Assessment method
Primary specification review; no runtime experiment
Source context
Official Tor and SCION documentation and pinned Meshtastic firmware
Outstanding qualification
Before/after witness: a configured additional parent-child link within the existing ISD provides another admissible path. Upgrade or configure border interfaces, control-plane topology, beaconing and segment registration; preserve endpoint ISD-AS/local addresses, daemon API and trust configuration. Existing endpoint code must already perform normal path lookup and refresh. Selection depends on policy and segment availability. This does not make legacy IP-only endpoints SCION-capable, guarantee use of every link or move active traffic seamlessly. No new data-plane extension, payload encryption or runtime validation.
Public sources
- https://docs.scion.org/en/latest/overview.html#routing
- https://docs.scion.org/en/latest/overview.html#link-types
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round524.html
- round524-sources.json