G02-SC: Yes
Rationale
Within the C01 same-AS witness, a destination retains its ISD-AS and local IPv4 address while replacing its final access. The AS ingress or its underlay delivery routers change the host route toward that address. SCION's pinned final-delivery code derives the underlay destination from the packet's host address, so incoming traffic uses the repaired internal route. The individual attachment update stays inside the destination AS; other ASes need no new host-location announcement.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
SCION AS/local-address separation, pinned final-delivery code and configured IPv4 routing
Outstanding qualification
Credit the selected composition, including configured IPv4, not SCION alone. Provision both accesses, preserve the host address and UDP endpoint, permit weak-host reception, and update affected routes without exporting host specifics. This is a real final-delivery route change, not merely choosing another unchanged ingress path. SCION explicitly leaves intra-AS routing to the underlying network. Inter-AS relocation, topology failures and changes to AS-level paths may require broader updates. No autonomous endpoint mobility, guaranteed convergence or runtime qualification is inferred.
Public sources
- https://docs.scion.org/en/latest/overview.html
- https://raw.githubusercontent.com/scionproto/scion/v0.12.0/router/dataplane.go
- https://www.rfc-editor.org/rfc/rfc1812.html#section-7.4
- https://www.rfc-editor.org/rfc/rfc1122.html#section-3.3.4.2
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round563.html
- round563-sources.json