Task #1942: NextHopFaceId test scenario - NFD - NDN project issue tracking system

Actions

Copy link

Task #1942

closed

NextHopFaceId test scenario

Added by Junxiao Shi over 9 years ago. Updated over 7 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Eric Newberry

Category:

Integration Tests

Target version:

v0.6

Start date:

Due date:

% Done:

100%

Estimated time:

6.00 h

Description

Develop an IntegrationTests scenario to test NDNLPv2 NextHopFaceId field.

Topology:

B--A--C

Procedure:

start NFD on A,B,C
on A, create a route for prefix ndn:/P toward B and C, where the cost toward B is lower than the cost toward C
on B, start traffic generator producer on ndn:/P prefix, serving payload "BBBBBBBB"
on C, start traffic generator producer on ndn:/P prefix, serving payload "CCCCCCCC"
on A, execute a consumer to enable NextHopFaceId feature and then express an Interest for ndn:/P/1 without NextHopFaceId tag, expect Data with payload "BBBBBBBB"
on A, execute a consumer to enable NextHopFaceId feature and then express an Interest for ndn:/P/2 tagged NextHopFaceId=faceB, expect Data with payload "BBBBBBBB"
on A, execute a consumer to enable NextHopFaceId feature and then express an Interest for ndn:/P/3 tagged NextHopFaceId=faceC, expect Data with payload "CCCCCCCC"
on A, execute a consumer to enable NextHopFaceId feature and then express an Interest for ndn:/P/4 tagged NextHopFaceId=null-face, expect either a timeout or a Nack
on A, execute a consumer to disable NextHopFaceId feature and then express an Interest for ndn:/P/5 tagged NextHopFaceId=faceC, expect either a timeout or Data with payload "BBBBBBBB"

Files

Download all files

20161211184844.tgz (702 KB) 20161211184844.tgz	integ 3433,3	Junxiao Shi, 12/11/2016 12:47 PM
20161211230354.tgz (739 KB) 20161211230354.tgz	integ 3433,5	Junxiao Shi, 12/12/2016 01:37 PM

Related issues 2 (0 open — 2 closed)

Actions

Copy link

Updated by Junxiao Shi over 9 years ago

Description updated (diff)
Assignee set to Junxiao Shi

I'll write the design.

After that, this Task needs reassigned for implementation.

Actions

Copy link

Updated by Junxiao Shi over 8 years ago

Description updated (diff)
Assignee deleted (~~Junxiao Shi~~)
Target version changed from v0.3 to v0.5

Actions

Copy link

Updated by Eric Newberry about 8 years ago

Assignee set to Eric Newberry

Actions

Copy link

Updated by Eric Newberry about 8 years ago

Status changed from New to In Progress

Actions

Copy link

Updated by Eric Newberry about 8 years ago

I believe this task may require modifications to ndn-traffic-generator to allow the client to attach local fields to the Interests. Otherwise, I can't think of a way to tag NextHopFaceId.

Actions

Copy link

Updated by Junxiao Shi about 8 years ago

I agree with note-5.

Actions

Copy link

Updated by Eric Newberry about 8 years ago

Should I create a new issue to reference on the ndn-traffic-generator Github page for the patch?

Actions

Copy link

Updated by Junxiao Shi about 8 years ago

Answer to note-7:

You MAY do that.

Actions

Copy link

Updated by Eric Newberry almost 8 years ago

I'm still working on this task, but further progress has been delayed until I complete #3074.

Actions

Copy link

#10

Updated by Eric Newberry almost 8 years ago

I believe this task will also require Nack processing in ndn-traffic-generator. I'll work on a patch for that.

Actions

Copy link

#11

Updated by Eric Newberry almost 8 years ago

It seems that the local fields must be enabled on each connection through a separate management Interest sent before the Interest containing (or not containing) NextHopFaceId. Therefore, ndnping, ndnpeek, and ndn-traffic-generator don't seem to fit this use case.

My current plan is to write a simple consumer in either C++ (compiling it with the integration test suite) or Python (requiring the addition of PyNDN to the integration testing environment). Any thoughts on this or any other suggestions?

Actions

Copy link

#12