C01-ND: Yes
Rationale
NDN requests name data rather than a producer attachment. In the already selected connected-tree witness, root-prefix Multicast forwarding explores provisioned Ethernet branches. After the original producer attachment is lost, the same producer can serve the unchanged content name and signing key through another provisioned tree attachment with a local prefix registration. Re-expressed Interests can reach that new attachment without changing the consumer's destination name.
Assessment method
Primary specification review; no runtime experiment
Source context
NDN/NFD management and forwarding; CCNx RFC 8569 and pinned Athena FIB
Outstanding qualification
The stable destination is a content name, not a live host identifier. Keep the remaining tree connected, preconfigure usable faces and root-prefix next hops, and authorize the producer registration at the new attachment. Interest lifetime/hop limits must cover the route. For a direct producer-recovery witness use an uncached named object and allow stale PIT entries/suppression to clear before retrying. Matching cached Data is otherwise legitimate but is not the sole evidence here. No NLSR, global directory, automatic attachment provisioning, PIT migration or seamless producer mobility is added. Existing trust-anchor validation remains; no runtime or capacity result.
Public sources
- https://docs.named-data.net/NFD/24.07/manpages/nfdc-route.html
- https://raw.githubusercontent.com/named-data/NFD/a1480a7c947dc6a48ee12c6c0637fc488c0c73a1/daemon/fw/multicast-strategy.cpp
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round528.html
- round528-sources.json