F26-ND: No
Rationale
The selected NFD forwarding path accepts ordinary unsigned Interests. It checks scope, hop limit and duplicate nonces, creates PIT state, then invokes the forwarding strategy without requiring sender or adjacency authorization. An unapproved requester can therefore cause onward Interest transmissions.
Assessment method
Primary normative source and selected adjacency-policy analysis; no execution
Source context
Pinned forwarding pipeline and selected Interest authentication policy
Outstanding qualification
NFD does suppress unsolicited Data and restrict response forwarding to pending downstreams. That request/response-state protection is real, but is not the transit admission required by F26: the selected Interest path itself has no authorization gate. Consumer-side Data signature validation does not supply that gate. No applies to this direct-Ethernet composition, not deployments with added access policies.
Public sources
- https://raw.githubusercontent.com/named-data/NFD/a1480a7c947dc6a48ee12c6c0637fc488c0c73a1/daemon/fw/forwarder.cpp
- https://raw.githubusercontent.com/named-data/NFD/a1480a7c947dc6a48ee12c6c0637fc488c0c73a1/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.
- round452.html
- round452-sources.json