[Nfd-dev] Client Control Strategy using Best Route Strategy v1

[Junxiao Shi]

Hi Vince

client-control strategy is designed to be used on the consumer side only,
because NextHopFaceId can be specified only from local apps. When an
Interest from a non-local face is processed by client-control strategy, the
behavior is undefined. It's an implementation choice to inherit from
best-route v1, the simplest possible strategy.
If inheriting from best-route v4 works better in your experiment, you may
do so.

I don't intend to make any changes on client-control strategy. Eventually
it will be deprecated as part of #2000, and NextHopFaceId should always be
honored regardless of strategy (see NDNLPv2 spec "implementation note").

Yours, Junxiao

On Wed, Jan 13, 2016 at 4:27 PM, Vince Lehman (vslehman) <
vslehman at memphis.edu> wrote:

> Hi Junxiao,
>
> I noticed that the Client Control Strategy is using Best Route Strategy
> version 1 instead of version 2. Is there any reason for this?
>
> I am experiencing an issue with the Client Control Strategy when a local
> app sends an Interest with a NextHopFaceId tag set to the Content Store’s
> FaceID (254). No match is found in the Content Store, and the Interest is
> left pending. When a remote Interest arrives for the same name while the
> previous Interest is pending, the Interest is dropped by the Best Route
> Strategy. When I have ClientControlStrategy inherit from
> BestRouteStrategy2, this issue seems to be resolved.
>
> I’ve attached some slides which illustrate the issue I am experiencing.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160113/074cabb9/attachment.html>