G02-BP: Yes
Rationale
A destination keeps its singleton EID and initiates a fresh authenticated TCPCL session to a known relay after changing IP attachment. With the existing C01 forwarding policy, the relay associates that EID/node with the new live session and delivers queued bundles through it. Session and delivery state change at the relay outside the access region; upstream EID routes remain directed there. This does not require distributing the destination's new IP address throughout the bundle network.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
BPv7 forwarding and TCPCLv4 active-only sessions with authenticated node identity
Outstanding qualification
Provision the relay, EID/node association, NODE-ID validation, endpoint registration and session-selection policy. Both access prefixes must already be routed and allow the new connection. Active-only polling is an RFC 9174 policy; BP does not automatically supply location discovery or this routing configuration. Relay failure, expired bundles, storage limits and unavailable connectivity can prevent delivery. Other topologies may require wider updates. No old TCP-session continuity, unrestricted relay relocation, global-capacity or integrated runtime qualification is credited.
Public sources
- https://www.rfc-editor.org/rfc/rfc9174.html#section-3.5
- https://www.rfc-editor.org/rfc/rfc9174.html#section-4.6
- https://www.rfc-editor.org/rfc/rfc9171.html#section-5.4
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round560.html
- round560-sources.json