F22-RA: Yes
Rationale
IRATI application registration can advertise a shared DAF name while retaining separate DAP names. The namespace manager stores the particular DAP name as the instance of that DAF entry, allowing multiple participants to register the same shared reference. getDFTNextHop resolves a DAF-only request to a matching nonlocal entry and fills in its individual instance before flow allocation. No common private identity or exclusive owner of the DAF name is required by this registration path.
Assessment method
Pinned registration, directory-resolution and flow-allocation source inspection
Source context
IRATI DAF/DAP registration and shared-name lookup
Outstanding qualification
Yes for shared-reference candidate discovery among admitted participants within a DIF. The default resolver returns one candidate at a time and does not guarantee enumeration, fairness or simultaneous delivery. Distinct names identify participants but do not prove legitimate group membership or authenticate final applications. DIF admission and local registration permissions remain prerequisites; this is not an open global namespace or a denial of administrative control over the DIF. Source inspection, not an interoperability or runtime result.
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
- https://github.com/IRATI/stack/wiki/Software-architecture-overview
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round670.html