[Nfd-dev] namespace-based strategy choice weakness

[Junxiao Shi]

Hi Susmit

a)
This question is orthogonal to my post. I'm talking about *what* goes into
the strategy choice table and how are the entries interpreted, not *where*
those entries come from.
Today it's a local configuration by admin of each router / end host.
"expressing
strategy choice through routing protocols" is a different idea under
discussion.

b)
Each strategy optimizes for a different goal, such as lower delay, higher
throughput. It does not prioritize traffic of one application over another.
If you mislabel web traffic as download traffic, you get higher throughput
but possibly more delay so navigation actions are less responsive.

Yours, Junxiao

On Mon, Jul 4, 2016 at 6:15 PM, Susmit <susmit at cs.colostate.edu> wrote:

> >
> > NFD can choose effective strategy from a marked component.
> > Instead of doing longest prefix match in the strategy choice table, a
> > strategy choice entry can indicate:
> >
> > contains "app=ndncon" => realtimeI'
> > contains "app=ndnfs" => high-throughput
>
> Two questions,
>
> a) Who is responsible for configuring strategies? Operators or users?
> Should users be responsible for finding optimal stategies in the
> network?
>
> b) How are we going to stop people from mislabeling Interests?
> Hypothetically speaking, If web search strategy is
> "normal-throughput", pages will load faster if they are labeled
> "high-throughput".
>
> Thanks.
>
> --
>
> Regards,
> Susmit
>
> ====================================
> http://www.cs.colostate.edu/~susmit
> ====================================
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160705/6d2e31c0/attachment.html>