C01-CX: Yes
Rationale
RFC 8569 separates the requested content name from the network endpoint supplying it. The selected name-prefix FIB can point the unchanged name toward another producer attachment; Athena exposes route addition/deletion for a name independently of that name's value. After the old attachment fails, infrastructure configuration can direct a fresh Interest to the same named content and trusted producer key at the alternate attachment.
Assessment method
Primary specification review; no runtime experiment
Source context
NDN/NFD management and forwarding; CCNx RFC 8569 and pinned Athena FIB
Outstanding qualification
Bounded configured recovery: provision reachable IPv4/UDP forwarder links and update the affected name-prefix routes, remove stale next hops and allow PIT state to expire or retry. The consumer retains the same exact name and validation requirements; it neither substitutes the new underlay address nor follows an application redirect. This credits name-level reachability, not persistence of an address for a particular host. Static FIB administration is required; no dynamic producer discovery or mobility protocol is silently added. Use uncached content to demonstrate the alternate producer attachment. No uninterrupted-session or complete executable-composition claim.
Public sources
- https://www.rfc-editor.org/rfc/rfc8569.html#section-1.3
- 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.
- round528.html
- round528-sources.json