Participant Relationship Protocol

Back to matrix

D01-HP: Pending

Rationale

RFC 6538 sections 2.1-2.2 documents kernel-integrated and userspace HIP implementations. Its userspace approach still diverts and reinjects packets, for example through TAP plus routing or filtering rules; userspace is not evidence of unprivileged execution. The HIPL manual explicitly requires root for its experimental Android hipd port, a historical implementation-specific limitation. RFC 7402 sections 3.2 and 3.4 and Appendix A describe alternative ESP integration choices rather than prescribing an OS privilege model. Pinned OpenHIP hipv2_new_crypto source uses TUNSETIFF and raw ESP sockets in src/linux/hip_linux_umh.c. These are concrete privileged networking setup paths, but they do not alone establish the credentials retained after setup. The separate 2024 developer report documents a root-run CORE test environment; emulator privileges are not a measurement of daemon privileges.

Assessment method

Pinned candidate source trace and developer report; no execution

Source context

IETF HIP experiment report, ESP integration specification and HIPL author manual; retained source hashes

Outstanding qualification

First identify a build matching the selected ECDSA profile; then trace retained credentials, delegated descriptors, SA and mobility updates. The 2024 report identifies ECDSA as nonworking in its own OpenSSL 3 branch. Do not transfer either that defect or the older branch privilege model to every HIP implementation.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.