C06-ND: No
Rationale
No under the revised C06 criterion. NDN Interests expose Name and, on network links, Nonce; their combination identifies an Interest for loop detection. In the selected NFD 24.07 multicast strategy, the ordinary initial Interest is passed to outgoing forwarding without replacing these fields with hop-local aliases. The outgoing pipeline sends that Interest and Data retains its Name. Consequently a cache-miss, unaggregated exchange has a common visible request selector across segments, allowing the consumer and responding producer attachments to be associated when their edge segments are observed. Direct Ethernet addresses identify each segment, not a global endpoint pair, but this does not remove the persistent Name/Nonce selector. No authenticated consumer identity is needed for this bounded association.
Assessment method
Primary packet definitions and pinned forwarding trace; bounded architectural counterexample, no runtime experiment
Source context
NDN packet v0.3, NFD 24.07, CCNx RFCs 8569 and 8609
Outstanding qualification
The bounded counterexample is an ordinary unaggregated request for a distinctive exact content name, absent from intermediate caches, answered by a live producer. An observer reads forwarding fields on the consumer-facing and producer-facing segments and matches that request and response across them. This uses visible protocol selectors, not payload fingerprints, timing, volume, diagnostic logs or access to every router mapping. It demonstrates a permitted case without association concealment; it does not claim that every repeated popular-name request can be uniquely linked. Content names are not inherently host or civil identities. Caching, aggregation, multiple publishers and replay can prevent attributing a response to the original signer or producer; those benefits do not make the selected composition conceal all such associations. A cache-hit exchange must be evaluated against the serving cache, not falsely attributed to the original publisher. No new anonymity wrapper or application profile is selected. NDNLP link-local tokens, sequence fields and local face IDs do not conceal the enclosed Name/Nonce. Nonce regeneration on other forwarding or retransmission paths is not denied. A signature identifies a signing key, not necessarily the current responding host.
Public sources
- https://docs.named-data.net/NDN-packet-spec/current/interest.html
- https://github.com/named-data/NFD/blob/NFD-24.07/daemon/fw/multicast-strategy.cpp
- https://github.com/named-data/NFD/blob/NFD-24.07/daemon/fw/forwarder.cpp
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round608.html
- round608-sources.json