F23-CG: Yes

Rationale

A bounded planned-mobility witness qualifies under the existing F23 criterion, consistently with F23-BP. A mobile bundle endpoint keeps its EID, final-peer BPSec keys and pending bundle store while leaving access node A and later attaching to access node B. Both contacts, their native link bindings and the onward path to the same destination are provisioned before movement. SABR sections 2.2-2.3 represent changing adjacency with timed contacts between stable node numbers and compute routes from those plans, without requiring the mobile participant to originate infrastructure prefixes or modify the infrastructure during the move. RFC 9171 sections 5.4 and 5.4.1 permit retaining pending forwarding and resuming it when forwarding becomes possible. The original pending application data is delivered without application resubmission. The new contact establishes the selected TCPCLv4/TLS 1.3 connection using provisioned numeric peers and the retained NODE-ID credentials. A new convergence-layer session does not replace the BP endpoint or pending bundle identity.

Assessment method

Bounded selected-profile architectural inference and cross-column consistency; no execution

Source context

RFC 9171 retention; SABR timed node contacts; selected native convergence-layer specifications

Outstanding qualification

This is a documentary constructive inference for scheduled movement and retained bundle delivery, not arbitrary-access discovery, seamless stream migration, lossless handover or an executed integrated-stack test. Require live persistent BP state, adequate storage, a retain-not-fail policy, bundle lifetime beyond the next contact, usable preprovisioned native links and correct schedules/clocks. An expired or deleted bundle is not recovered by this witness. No critical-bundle replication, custody extension or SAGA/IPND discovery is needed. The earlier demand for a live discovery adapter was too broad for this planned-contact role; its integration gaps remain relevant to unplanned mobility and E03, but do not block this architectural F23 Yes. No profile, criterion or external routing authority is added. TCPCL reconnection and any partial-transfer restart remain below the application. No claim that a TCP connection survives changing IP attachment.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.

round367-sources.json
round367-witness.json