F14-RA: No
Rationale
The selected RINA composition separates application names from DIF-scoped addresses, but resolves those names to their serving IPCP addresses. The namespace manager distributes directory entries to neighboring members; flow allocation uses that mapping and carries local and remote addresses. In the routed lower DIF, these addresses identify the attachment of the endpoint-host IPCPs. Recursive scope and encryption restrict visibility to particular members, but the selected composition does not conceal endpoint network location from those routing members.
Assessment method
Pinned namespace distribution and flow-address source inspection
Source context
IRATI directory and flow allocation
Outstanding qualification
No for an explicit endpoint-location-hiding mechanism in this selected composition. The observer is an admitted member of the routed DIF carrying the endpoint-host flow, not an arbitrary outside listener or necessarily the first physical access point. Location means network attachment within that scope, not GPS, a street address or civil identity. Stable names, mobility and encrypted payloads remain supported; this verdict does not deny scope isolation or claim every RINA design must expose the same information.
Public sources
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/rinad/src/ipcp/namespace-manager.cc
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/rinad/src/ipcp/flow-allocator.cc
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round667.html
- round672.html