Project

General

Profile

Actions

Task #1312

closed

Task #1308: Strategy choice and dispatch

nfdc: strategy-choice

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

Status:
Closed
Priority:
Normal
Category:
Tools
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
3.00 h

Description

Implement NFD Strategy Choice protocol client.

Also delete fib/set-strategy command.


Related issues 2 (0 open2 closed)

Related to NFD - Task #1311: Strategy Choice managementClosed

Actions
Follows NFD - Task #1310: Strategy Choice protocolClosedJunxiao Shi03/01/2014

Actions
Actions #1

Updated by Junxiao Shi over 10 years ago

  • Due date deleted (03/02/2014)
  • Start date deleted (03/02/2014)
Actions #2

Updated by Hila Ben Abraham over 10 years ago

Why is it 'related' to #1311 and not 'blocked' by #1311?

Actions #3

Updated by Junxiao Shi over 10 years ago

#1312 is the consumer, #1311 is the producer.
Development for both can start when protocol (#1310) is completed.

In 1970s, it's common to write programs for a machine that is not yet manufactured.
Both machine and programs follow the documentation, so they will work once the machine is released.

Similarly, both producer and consumer follow StrategyChoice protocol, and they will work.

For task #1312 and #1311, end-to-end testing is possible only when both tasks have some code.

Individually testing #1312 is still possible: don't run NFD, but use netcat to listen on the NFD's socket.
netcat would capture what nfdc writes into the socket, and the written octets can be inspected to determine whether consumer conforms to the protocol.

Actions #4

Updated by Hila Ben Abraham over 10 years ago

  • Status changed from New to In Progress
Actions #5

Updated by Hila Ben Abraham over 10 years ago

  • % Done changed from 0 to 100

I'm about to submit 2 commits: one for nfd (including nfdc changes) and one for ndn_cpp_dev (including the StrategyChoiceManagementOptions).

Should I also delete strategy field from FibManagementOptions?

Actions #6

Updated by Alex Afanasyev over 10 years ago

Ehm... I thought we agreed to unify "options" data structure? At least in here we could just reuse the existing FibMangementOptions...

Actions #7

Updated by Junxiao Shi over 10 years ago

Alex Afanasyev wrote:

Ehm... I thought we agreed to unify "options" data structure? At least in here we could just reuse the existing FibMangementOptions...

I plan not only to unify Options, but also combine all management protocols into one. I'll send the proposal sometime.

Actions #8

Updated by Alex Afanasyev over 10 years ago

Got it. But what should we do for this one? Reuse FibManagementOptions, create new options as per-spec, or wait till spec update?

Actions #9

Updated by Junxiao Shi over 10 years ago

We should create new one for now. FibManagementOptions and StrategyChoiceOptions have different TLV-TYPE numbers, so FibManagementOptions cannot be reused.

Spec update will not happen very soon.

Actions #10

Updated by Alex Afanasyev over 10 years ago

Ok. Hila, go ahead with the push. I would not modify anything with FibManagementOptions, since we are going to change it in the future anyways.

Actions #11

Updated by Hila Ben Abraham over 10 years ago

  • Status changed from In Progress to Closed
Actions

Also available in: Atom PDF