F16-HP: Yes
Rationale
A selected-peer HIP ACL can gate authenticated association admission before ESP user-data delivery. Revocation can replace that policy and drop every HIP association for the revoked HI; RFC 7402 section 6.7 requires dropping the associated ESP SAs.
Assessment method
Documentary native-policy composition; no cutover or isolation experiment
Source context
HIP policy and ESP teardown; DTLS/TLS external-PSK and closure specifications
Outstanding qualification
Completed-cutover witness: pause admission/delivery, remove the HI from allowed peers, discard active and pending HIP/ESP state and queued undelivered data, then reopen under the new policy. An ACL edit alone is insufficient. A controlled restart must clear installed SAs too, not merely restart a control daemon. No runtime race audit was executed.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round268-sources.json