Participant Relationship Protocol

Back to matrix

F28-ND: Yes

Rationale

NDN Interests expose ForwardingHint to the consumer. In the selected NFD 24.07 implementation, Strategy::lookupFib uses the delegation names in that hint instead of the content name while outside the producer region. With provisioned routes for distinct delegation regions, the endpoint can select which region the forwarded Interest is directed toward, without changing the requested content name.

Assessment method

Primary specification and pinned code review; no runtime experiment

Source context

NDN v0.3 and pinned NFD 24.07 forwarding-hint implementation

Outstanding qualification

Bounded native-feature witness: one known delegation name per Interest, usable local FIB routes toward that region and consistent producer-region configuration. The selected multicast strategy also calls lookupFib, so the hint selects its forwarding entry but may still fan out across multiple next hops. The hint is removed on entering the producer region. Cache hits can satisfy the Interest earlier, and default routes can reduce path discrimination; the positive applies to forwarding of an unsatisfied Interest where delegation-specific routes exist. It does not enforce an exact hop list, cryptographic path compliance or universal cache bypass. This F28 configuration is separate from the G01 flooding witness, which deliberately uses no hints; its qualifications remain unchanged. No new protocol layer or runtime validation is claimed.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.