D04-IL: Yes
Rationale
With eNIDs enabled on an administratively provisioned ILNP host, a client application obtains a fresh NID for each new socket flow through the ordinary resolution/socket/connect interface. NIDs are allocated to sockets and retired after use, rather than requiring the user to edit shared interface addresses or routes for each communication identity. The 2026 DNS-enabled FreeBSD demonstration shows successive nc TCP connections with distinct NIDs.
Assessment method
Documentary capability inference from per-socket allocation and ordinary application API
Source context
Haywood and Bhatti (2025), sections 3.2 and 3.4; FreeBSD 14.3 demonstration (2026)
Outstanding qualification
Bounded client capability after privileged installation and eNID-policy provisioning. The OS generates and manages the values; this does not mean user-selected arbitrary NIDs, portable cryptographic keys, durable server identities or immunity to privileged host administrators. DAD and kernel pool/cache updates remain necessary but are not per-identity administrative interface reconfiguration. No two-user isolation or non-root execution test was performed; the conclusion is documentary plausibility, not runtime certification.