F08-HP: No
Rationale
The selected HIP/ESP profile carries application UDP, which has no end-to-end transport connection. RFC 8046 preserves host-identity bindings and permits locator changes without replacing the HIP/ESP context, but that network-level continuity does not create a transport connection. This applies the same connection-specific boundary used for the selected IP, Yggdrasil and cjdns UDP compositions.
Assessment method
Documentary profile-boundary and source-path analysis; no execution
Source context
Primary RFCs and pinned PARC upstream source
Outstanding qualification
This is not a denial of HIP mobility: F23-HP remains Yes. A connected UDP socket is a local API association, not an additional wire-level connection. ESP SAs and HIP associations are below the selected application transport; DTLS in RI supplies a protected transport association and is a different composition. Adding TCP or broadening F08 to communication-context continuity would require a separate profile or criterion change. No runtime failure is alleged.
Public sources
- https://www.rfc-editor.org/rfc/rfc8046.html#section-1
- https://www.rfc-editor.org/rfc/rfc768.html
- https://www.rfc-editor.org/rfc/rfc7402.html
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round274-sources.json