Feature #3163
open
Insert to CS with forwarding hint
Added by Junxiao Shi about 9 years ago.
Updated over 7 years ago.
Description
When forwarding inserts Data to ContentStore, determine the forwarding hint(s) used to retrieve it, and pass along to CS insert procedure.
See #3161 for necessity and solution at high-level.
This issue includes:
- incoming Data pipeline: determine which forwarding hint(s) has been used to retrieve the Data, and insert Data to CS with these forwarding hint(s)
NFD Developer Guide should be updated as part of this issue.
Related issues
3 (3 open — 0 closed)
Question: What if incoming Data matches multiple PIT entries with distinct Link objects?
My answer:
If any of these PIT entries has no Link object, the Data is inserted with no Link object.
This Data can match future Interests with any (or no) Link object.
If all PIT entries have Link objects, the Data is inserted multiple times with each Link object.
This behavior is no different than Interest with each distinct Link object gets Data separately.
In addition,
PIT match procedure should be consider out-records: incoming Data can match a PIT entry only if incoming face has a corresponding out-record on the PIT entry.
Otherwise there are two harms:
(a) Eve's Data would be returned in response to Interests without Eve's Link object.
(b) Eve's Data could be inserted with no Link object, if there is another PIT entry without Link object.
- Related to Feature #3000: Design mobility with forwarding hint added
- Description updated (diff)
20150903 conference call approves note-3 idea.
Alex also suggests that these restrictions are unnecessary when Interest has implicit digest.
Updates are made to #3161 #3162.
- Subject changed from Insert to CS with Link to Insert to CS with forwarding hint
- Description updated (diff)
- Target version deleted (
v0.5)
Also available in: Atom
PDF
Updated by