Project

General

Profile

Actions
Copy link

Task #1622

closed

Special FaceId for ContentStore

Added by Junxiao Shi over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Junxiao Shi
Category:
Forwarding
Target version:
v0.3
Start date:
Due date:
% Done:

100%

Estimated time:

Description

When a Data is returned from ContentStore, IncomingFaceId should be set to a special value.

Related issues 1 (0 open — 1 closed)

Related to NFD - Task #1620: NullFace and reserved FaceIdClosedJunxiao Shi

Actions
Actions
Copy link
 #1

Updated by Junxiao Shi over 10 years ago

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.
Actions
Copy link
 #2

Updated by Junxiao Shi over 10 years ago

  • Related to Task #1620: NullFace and reserved FaceId added
Actions
Copy link
 #3

Updated by Junxiao Shi over 10 years ago

  • 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

Actions
Copy link
 #4

Updated by Junxiao Shi over 10 years ago

  • Status changed from Code review to Closed
Actions
Copy link

Also available in: Atom PDF