D04-IP: No
Rationale
Plain IPv4/IPv6 supplies interface addressing, not independently controlled per-user communication identities. RFC 4291 sections 2 and 2.1 define IPv6 addresses as interface identifiers; adding addresses to a shared Linux interface is network administration. An ordinary process using an existing address, including the delegated raw sockets tested for D01, has not created its own protocol identity. The selected IP column excludes application authentication and IPsec, so keys added by TLS, JWT or an overlay cannot be credited here.
Assessment method
Initial evidence inventory
Source context
IP addressing architecture and Linux capability boundary
Outstanding qualification
This No is about the selected plain-IP capability, not a claim that every address change needs a human administrator. SLAAC/DHCP, delegated namespaces and virtual interfaces can automate or isolate address administration; they do not supply this selected stack with a user-controlled identity independent of interface addressing. D01-IP remains Yes with its existing setup and loopback qualifications.
Public sources
- https://www.rfc-editor.org/rfc/rfc4291.html#section-2.1
- https://man7.org/linux/man-pages/man7/capabilities.7.html
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round234-raw-ip-result.json