G02-CX: Yes
Rationale
A producer retains its content-name prefix and signing key while moving between provisioned attachments inside a routing region. The ingress forwarder used by outside consumers replaces the prefix's old next-hop link with the new one; affected internal forwarders are adjusted as needed. Other regions keep a covering name-prefix route toward that ingress. CCNx longest-prefix forwarding and Athena FIB add/delete operations support this configured witness without a network-wide producer-location announcement.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
RFC 8569 hierarchical forwarding and pinned Athena FIB route operations
Outstanding qualification
This is the C01 named-content boundary with an actual changed route to the producer, not recovery solely from cached content. Provision usable IPv4/UDP links and administer the affected FIB entries; remove obsolete next hops and allow stale PIT state to expire before retrying. Keep the covering prefix route valid and verify the returned object. No automatic producer discovery, arbitrary inter-region movement or routing-protocol extension is assumed. No uninterrupted delivery, global-capacity or runtime result is credited.
Public sources
- https://www.rfc-editor.org/rfc/rfc8569.html#section-2.4.4
- https://raw.githubusercontent.com/PARC/Athena/f89da532c8690af88dfb81e708007022833625ca/ccnx/forwarder/athena/athena_FIB.c
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round567.html
- round567-sources.json