F23-PI: Yes
Rationale
Relationship continuity is separated from volatile carrier locators and paths. Section 7 specifies authenticating a replacement path, binding it to the existing relationship/direction/generation, validating it, migrating eligible work and draining the old path. Connection aliases, service lanes, ordering, replay and item identities remain unchanged when handover continuity is claimed. This supports moving attachment while preserving the relationship, provided a replacement path is obtainable and authorized. Failure to prove continuity must fail or create a new epoch, not silently pretend continuity. Architectural credit does not demonstrate a carrier-specific mobility controller, automatic discovery at every access point or interruption-free operation.
Assessment method
Pinned relationship lifecycle specification; architectural capability, no execution
Source context
PRP Relationship Lifecycle sections 3 and 7, commit 9b515ce11cfee4fd9d9ec82a5aef9b13ecc7085b
Outstanding qualification
Move the endpoint between two attachment points with the same relationship; establish an authorized replacement path and retain ordering/replay/item state. For PRP over IP also change the UDP/IP locator. Verify remote peer continuity and no application relationship restart; measure interruption, loss and stale-path rejection. Start with make-before-break; break-before-make and simultaneous endpoint movement require separate qualification. No handover experiment performed.