Task #1131
closed
mock implementation of basic forwarding procedure
Added by Junxiao Shi almost 11 years ago.
Updated almost 11 years ago.
Description
Implement essential steps of basic forwarding procedure.
Strategy is fixed to best route #1136.
It's not determined per namespace.
There is no performance requirement on this mock implementation.
Unit testing is not required for this task.
Files
- Description updated (diff)
- Assignee set to Junxiao Shi
- Due date changed from 02/01/2014 to 01/25/2014
- Start date deleted (
01/31/2014)
- Target version set to Mock
- Due date changed from 01/25/2014 to 01/29/2014
- Status changed from New to In Progress
I need design review on the forwarding steps.
The design document is reviewed during 20140128 conference call, and updated.
- Due date changed from 01/29/2014 to 01/30/2014
- Category set to Forwarding
- % Done changed from 0 to 30
"forwarding-pipelines_20140129.pptx" is design update after 20140129 conference call.
Remaining problems:
- incoming Interest pipeline, CS match branch: if an Interest from face 1 matches Data packet A at CS, A should go to face 1.
At this time, ccnd would look up PIT to find other Interests pending on face 1 that could be satisfied by A, and consume these Interests.
When will this ever happen?
- incoming Interest pipeline, CS match branch: InRecord should be deleted
- incoming Data pipeline: an incoming Data packet is forwarded to each pending downstream at most once.
Is there any other scenario that can cause the same Data packet going into the same face twice? If so, deduplication is needed in outgoing Data pipeline.
forwarding-pipelines_20140130.pptx is the actual implemented pipeline.
- Status changed from Code review to Closed
Also available in: Atom
PDF
Updated by 
Updated by