F15-ND: No
Rationale
In the selected NFD 24.07 forwarding path, a well-formed Interest with a fresh name/nonce passes hop-limit, localhost-scope and duplicate checks and reaches PIT insertion before content-store lookup and strategy handling. The pinned Pit::findOrInsert creates a name-tree/PIT entry without an admission proof or a configured aggregate allocation quota on that path. Data signature verification at the consumer does not protect this request-state boundary. The selected composition therefore lacks the F15 combination of admission/early rejection with bounded pre-admission state or work.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
NFD PIT allocation ordering and RFC 8966 base-Babel neighbor admission
Outstanding qualification
The No concerns the declared direct-Ethernet NFD composition and its normal-interest processing, not every NDN research defense or alternative implementation. Duplicate suppression, scope validation, packet-size constraints, timers and finite hardware are useful but do not bound the aggregate creation of distinct pending requests before downstream strategy decisions. The selected multicast strategy is not a pre-PIT authorization gate. No signed-consumer policy, resource-admission extension or external firewall is added. This source trace does not measure attack throughput, prove a successful service outage or claim that every arriving Interest is forwarded. Network-capacity authorization remains F26. No runtime experiment.
Public sources
- https://raw.githubusercontent.com/named-data/NFD/a1480a7c947dc6a48ee12c6c0637fc488c0c73a1/daemon/fw/forwarder.cpp
- https://raw.githubusercontent.com/named-data/NFD/a1480a7c947dc6a48ee12c6c0637fc488c0c73a1/daemon/table/pit.cpp
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round538.html
- round538-sources.json