[Nfd-dev] Interest lifetime limit

[Giovanni Pau]

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. 
==========================
It had long since come to my attention that people of accomplishment rarely sat back and let things happen to them. They went out and happened to things. 

- Leonardo da Vinci 
==========================




On Mar 20, 2014, at 9:41 PM, Junxiao Shi <shijunxiao at email.arizona.edu> wrote:

> Both InterestLifetime and FreshnessPeriod are nonNegativeInteger which could be up to 8 octets. They are measured in milliseconds.
> 
> Yours, Junxiao
> On Mar 20, 2014 9:38 PM, "Burke, Jeff" <jburke at remap.ucla.edu> wrote:
> >
> >
> > I don't know that we have enough evidence for how this might be used to
> > restrict it to ~32 seconds maximum. This isn't even 10x the default value
> > and doesn't approach what came up in the unresolved "long-lived interest"
> > discussion. On the other hand, millisecond resolution (or decisecond
> > resolution, at least) seems like it might also be useful in some cases.
> >
> > Is there a strong reason for this to be 2 bytes?  Could we have a 4-byte
> > long in ms instead, and have the maximum value correspond to a "hold it as
> > long as you're willing" behavior?
> >
> > Is FreshnessPeriod also 2 bytes?   This seems similarly limiting.  This
> > wouldn't handle our canonical NYTimes front page example.
> >
> > Jeff
> >
> >
> > On 3/20/14, 9:26 PM, "Giovanni Pau" <gpau at cs.ucla.edu> wrote:
> >
> > >I would not bound it in this way is not better to express it as a 2 byte
> > >in seconds so we have the flexibility for future applications?
> > >
>