F35-ND: Yes
Archived previous-definition assessment — revision 5.73. Retired in 5.82; excluded from the active matrix and counts. This historical verdict is not a current assessment.
Rationale
NFD 24.07 allows an administrator to change the forwarding strategy for a name prefix at an intermediate forwarder. A bounded deployment replaces BestRoute's initial single-next-hop forwarding with native Multicast forwarding to eligible next hops. This adds multi-branch Interest forwarding while existing consumers and producers retain their packet format, implementations and applications.
Assessment method
Primary specification review; no runtime experiment
Source context
Reticulum 1.5.5 and NFD 24.07 documentation and pinned code
Outstanding qualification
Provision two usable direct-Ethernet next hops for the prefix and select the installed Multicast strategy at the intermediate NFD. An unsatisfied fresh Interest demonstrates the change; cache hits, scope restrictions and retransmission suppression can prevent particular transmissions. Administration is required at the forwarder, not an endpoint software upgrade. Existing Data validation and pending-Interest handling remain unchanged. This native configuration is separate from the G01 tree witness and the F09 segmented-retrieval witness; their verdicts and limitations are unchanged. No guaranteed duplicate delivery, throughput gain, arbitrary application multicast service or runtime result.
Public sources
- https://docs.named-data.net/NFD/24.07/manpages/nfdc-strategy.html
- https://raw.githubusercontent.com/named-data/NFD/a1480a7c947dc6a48ee12c6c0637fc488c0c73a1/daemon/fw/multicast-strategy.cpp
- https://raw.githubusercontent.com/named-data/NFD/a1480a7c947dc6a48ee12c6c0637fc488c0c73a1/daemon/fw/best-route-strategy.cpp
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round521.html
- round521-sources.json