Project

General

Profile

Actions
Copy link

Task #1131

closed

mock implementation of basic forwarding procedure

Added by Junxiao Shi almost 11 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Junxiao Shi
Category:
Forwarding
Target version:
Mock
Start date:
Due date:
01/30/2014
% Done:

100%

Estimated time:
15.00 h

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

Download all files
forwarding-pipelines_20140127.pptx (67.9 KB) forwarding-pipelines_20140127.pptx Junxiao Shi, 01/27/2014 07:11 PM
forwarding-pipelines_20140128.pptx (64.2 KB) forwarding-pipelines_20140128.pptx Junxiao Shi, 01/28/2014 11:19 PM
forwarding-pipelines_20140129.pptx (64 KB) forwarding-pipelines_20140129.pptx Junxiao Shi, 01/29/2014 11:50 PM
forwarding-pipelines_20140130.pptx (64.2 KB) forwarding-pipelines_20140130.pptx Junxiao Shi, 01/30/2014 09:57 PM

Related issues 2 (0 open — 2 closed)

Blocked by NFD - Task #1136: best route forwarding strategyClosedJunxiao Shi01/24/201401/25/2014

Actions
Precedes NFD - Task #1140: mock forwarder integrationClosedJunxiao Shi01/31/201401/31/2014

Actions
Actions
Copy link
 #1

Updated by Junxiao Shi almost 11 years ago

  • Description updated (diff)
  • Assignee set to Junxiao Shi
Actions
Copy link
 #2

Updated by Junxiao Shi almost 11 years ago

  • Due date changed from 02/01/2014 to 01/25/2014
  • Start date deleted (01/31/2014)
Actions
Copy link
 #3

Updated by Alex Afanasyev almost 11 years ago

  • Target version set to Mock
Actions
Copy link
 #4

Updated by Junxiao Shi almost 11 years ago

  • Due date changed from 01/25/2014 to 01/29/2014
Actions
Copy link
 #5

Updated by Junxiao Shi almost 11 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #6

Updated by Junxiao Shi almost 11 years ago

I need design review on the forwarding steps.

Actions
Copy link
 #7

Updated by Junxiao Shi almost 11 years ago

The design document is reviewed during 20140128 conference call, and updated.

Actions
Copy link
 #8

Updated by Junxiao Shi almost 11 years ago

  • Due date changed from 01/29/2014 to 01/30/2014
  • Category set to Forwarding
  • % Done changed from 0 to 30
Actions
Copy link
 #9

Updated by Junxiao Shi almost 11 years ago

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

Updated by Junxiao Shi almost 11 years ago

forwarding-pipelines_20140130.pptx is the actual implemented pipeline.

Actions
Copy link
 #11

Updated by Junxiao Shi almost 11 years ago

  • Status changed from Code review to Closed
Actions
Copy link

Also available in: Atom PDF