Task #1622
closed
Special FaceId for ContentStore
Added by Junxiao Shi over 10 years ago.
Updated over 10 years ago.
Description
When a Data is returned from ContentStore, IncomingFaceId should be set to a special value.
20140517 conference call raises a few questions:
- We can reserve a special FaceId to indicate "Data comes from ContentStore", so that every outgoing Data packet can contain IncomingFaceId field.
- If Data Name starts with
ndn:/localhop, can such Data be sent to a remote face? (a previous decision was to treat it as coming from local, so it can travel one hop)
- In a corporate router, the origin of Data is useful for policy decision. However, original IncomingFaceId on a Data returned from ContentStore is not always useful because face may disappear and invalidate the FaceId.
- Related to Task #1620: NullFace and reserved FaceId added
- Subject changed from Cs::get unset IncomingFaceId to Special FaceId for ContentStore
- Description updated (diff)
- Category changed from Tables to Forwarding
- Status changed from New to Code review
- Assignee set to Junxiao Shi
- Target version set to v0.3
- % Done changed from 0 to 100
Completed together with #1620
- Status changed from Code review to Closed
Also available in: Atom
PDF
Updated by