G02-ND: Yes
Rationale
The selected NFD stack supports operator-configured name-prefix routes over its Ethernet faces. When a producer changes attachment within a prepared region, the ingress and affected regional forwarders can replace the prefix's next-hop face while outside forwarders retain a covering route toward that region. Consumers keep the same content name and validation key. The producer route used for incoming Interests changes without distributing that individual attachment update to all forwarders.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
NFD 24.07 native RIB route management and bounded regional forwarding
Outstanding qualification
Provision both Ethernet attachments and authorize route management and producer registration. Remove obsolete next hops, control inherited covering routes with the appropriate capture/inheritance flags, wait for RIB-to-FIB completion, and allow stale PIT state to expire before retrying uncached content. This uses native local FIB configuration; it does not infer scoped recovery from the separate G01 root-prefix flooding witness. No NLSR, global directory, IP underlay, automatic producer discovery or arbitrary inter-region mobility is added. No runtime experiment.
Public sources
- https://docs.named-data.net/NFD/24.07/manpages/nfdc-route.html
- https://raw.githubusercontent.com/named-data/NFD/a1480a7c947dc6a48ee12c6c0637fc488c0c73a1/docs/manpages/nfdc-route.rst
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round568.html
- round568-sources.json