F39-ND: Yes
Rationale
A producer registers a name prefix and receives matching Interests through its application face; the consumer expresses an Interest by name and receives Data through the same API. NFD prefix routing selects a local Unix-socket producer face or a remote Ethernet path. The consumer does not name the producer host or change its IPC interface.
Assessment method
Primary application API, forwarding documentation and pinned source; bounded architectural witness
Source context
NDN prefix registration and CCNx named forwarding
Outstanding qualification
Bounded request/reply IPC with a single producer for the chosen prefix and a cache miss. Use a globally scoped prefix such as /example/testApp, not the special /localhost scope. The official examples contain a /localhost prose label but the shown code uses /example and appends a version. MustBeFresh alone does not ensure contact with a live producer. No guarantee of arbitrary process addressing, fresh execution, exactly-once effects, duplex sessions, zero-copy or runtime conformance is claimed.
Public sources
- https://docs.named-data.net/ndn-cxx/current/examples.html
- https://docs.named-data.net/NFD/current/manpages/nfdc-route.html
- https://docs.named-data.net/NDN-packet-spec/current/interest.html
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round695.html