[Nfd-dev] Interest lifetime limit

[Junxiao Shi]

20140114 meeting discussed InterestLifetime upper bound. Van's idea is:

* Protocol should not set an upper bound on InterestLifetime.
* Setting a *practical* upper bound is a policy issue, configurable by
operator.

My proposal of using 32768ms as the default upper bound is completely
unrelated to "2 octets". Its reason is:

* Most applications don't need any special lifetime.
* NFD Notification mechanism is more efficient if longer lifetime can be
used. Push applications also desire a long lifetime.
* Forwarder cannot afford long lifetime because PIT entries consume memory.
* Trade-off between the need of push application and the forwarder state
cost leads to 32768ms default upper bound.

Yours, Junxiao

On Mar 20, 2014 9:52 PM, "Giovanni Pau" <gpau at cs.ucla.edu> wrote:
>
> Junxiao,
>
> sorry i can't get it, if we have 64bits, then why we need to bound it to
a 16bit value? I agree is better to measure in ms rather than sec, but yet
i do not understand the need to bound. I agree with jeff on the long timed
interests, in our case such as an interest for a road-hazard in the
direction of traveling.
>
> Thanks
> g.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20140320/4cd93ce1/attachment.html>