F09-HP: No
Rationale
The selected RFC 8046 mobility procedure changes the locator used by the existing host communication. It does not supply concurrent useful-data scheduling over multiple paths; host multihoming procedures are assigned to RFC 8047, which is not selected.
Assessment method
Selected-profile documentary review; no mobility experiment
Source context
HIP host mobility and DTLS 1.3 primary specifications
Outstanding qualification
A LOCATOR_SET can list addresses without providing a selected multipath data scheduler. Address verification traffic and make-before-break overlap do not establish concurrent payload paths.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round261-sources.json