F21-HP: Yes
Rationale
The HIP native socket contract exposes the peer HIT with received data: RFC 6317 section 4.1.1 specifies sockaddr_hip returns for recvfrom, and section 4.3 specifies peer-HIT queries. With HIP-only admission and the selected pinned HI/HIT authentication, the receiving application can identify the authenticated host without another login exchange.
Assessment method
Documentary API and source-path review; no execution
Source context
HIP API RFC and pinned CICN implementation source
Outstanding qualification
Use a specific local HIT or HIP_HIT_ANY, not HIP_ENDPOINT_ANY, which permits unprotected IP fallback. Compare each received peer HIT against the pinned HIPv2 identity; a resolver result or wildcard is not authentication. Keep the API binding to the protected delivery context and discard stale association metadata. RFC 6317 predates HIPv2: preserve its identity-delivery contract while using current HIPv2 HIT generation/prefix, not its historical ORCHID constants. This is a documentary API composition, not a tested final-RFC implementation or a new wire layer.
Public sources
- https://datatracker.ietf.org/doc/html/rfc6317#section-4.1.1
- https://www.rfc-editor.org/rfc/rfc7401.html#section-3
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round272-sources.json