F39-CX: Yes
Rationale
A CCNx Interest names the requested producer service data independently of its host. With the prefix bound to one producer and no cached match, Athena resolves the name through its FIB and sends to the selected local or remote UDP link; the response follows pending-Interest state. The application retains the same named request/reply exchange.
Assessment method
Primary application API, forwarding documentation and pinned source; bounded architectural witness
Source context
NDN prefix registration and CCNx named forwarding
Outstanding qualification
Architectural and pinned-source witness, not an executed application deployment. Athena _processInterest checks the cache then uses athenaFIB_Lookup and the transport adapter; its UDP module distinguishes local links. The configured prefix denotes one producer service in this witness. A cached Content Object alone does not establish live IPC, and no generic RPC, arbitrary duplex stream, exactly-once semantics, zero-copy or producer-process authentication is inferred.
Public sources
- https://www.rfc-editor.org/rfc/rfc8569.html#section-3
- https://github.com/PARC/Athena/blob/f89da532c8690af88dfb81e708007022833625ca/ccnx/forwarder/athena/athena.c
- https://github.com/PARC/Athena/blob/f89da532c8690af88dfb81e708007022833625ca/ccnx/forwarder/athena/athena_FIB.c
- https://github.com/PARC/Athena/blob/f89da532c8690af88dfb81e708007022833625ca/ccnx/forwarder/athena/athena_TransportLinkModuleUDP.c
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round695.html