F12-RA: No
Rationale
The selected IRATI flow allocator resolves one remote application and creates a connection to it. Static redundant forwarding clones that connection PDU onto several next hops while retaining its destination address and destination CEP. At reception, RMT checks the local destination address and passes the destination CEP to EFCP, which looks up one connection instance and discards the PDU if no such instance exists. These paths converge on the same receiver; they do not establish delivery to multiple final participants.
Assessment method
Pinned flow allocation, forwarding and receiver demultiplexing source inspection
Source context
IRATI RMT and EFCP delivery path
Outstanding qualification
No for multicast in the declared IRATI composition. The selected policies provide redundant paths to one receiver, not a multicast group address, receiver connection mapping or destination-rewriting policy for a distribution tree. A shared DAF name selects one member during discovery. This does not rule out a different RINA policy or implementation supporting multicast. F09/F10 redundancy and F22 shared-reference discovery remain Yes. Pinned source analysis, not a runtime test.
Public sources
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/kernel/rmt.c
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/kernel/efcp.c
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/rinad/src/ipcp/flow-allocator.cc
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/rinad/src/ipcp/namespace-manager.cc
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round664.html
- round670.html
- round671.html