[Nfd-dev] strategy specific parameters

[Junxiao Shi]

Hi Klaus

20150413 conference call discussed this proposal.

This proposal is a subset of #2000 composable strategy building blocks
<http://redmine.named-data.net/issues/2000>.
With #2000, an operator can not only pass parameters to a strategy, but
also create new strategies. Both can happen at runtime.
Passing parameters is just a special case of creating new strategies: take
an existing strategy, and give it new parameters.


I believe having strategy parameters is a good direction toward #2000.
I agree with Alex that parameters should be carried in the Name after the
version component, at the management protocol
<http://redmine.named-data.net/projects/nfd/wiki/StrategyChoice> level.
At command line tool level, however, I prefer to accept ccndc syntax as
well: operator can either specify parameters as part of the strategy Name,
or in separate command line options.


I disagree with the use case that broadcast strategy generates new Nonces
for outgoing Interests, because it can cause persistent Interest loop in #1953
scenario <http://redmine.named-data.net/issues/1953>.

Yours, Junxiao

On Sun, Apr 12, 2015 at 6:23 AM, Klaus Schneider <
klaus.schneider at uni-bamberg.de> wrote:

> Hi everyone,
>
> I think it would be a good idea to have (optional) parameters for a
> forwarding strategy in order to make the design more flexible.
>
> The CCNx prototype supports this:
>
>  ccndc setstrategy <prefix> <strategy> [<parameters> [<lifetime>]]
>>
>
> Unfortunately, there is currently no such option in NFD:
>
>  nfdc set-strategy <namespace> <strategy-name>
>>
>
>
> If you think this is reasonable, I can help with the implementation. I am
> also not sure if this is the right place for such feature requests or if I
> should put them up as a redmine ticket?
>
> Thanks,
> Klaus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20150413/2410b736/attachment.html>