[ndnSIM] Delay PIT and CS deletion

[Gustavo Gonzalez]

Thanks for the answer Spyridon,

I have been trying to run the code after having modified the time but I got
an error (./src/ndnSIM/NFD/daemon/table/pit-face-record.cpp:45:33: error:
conversion from ‘double’ to non-scalar type ‘boost::chrono::milliseconds
{aka boost::chrono::duration<long long int, boost::ratio<1ll, 1000ll> >}’
requested) I just made equal the lifetime value to 250. Probably I am doing
it wrong and that's why the mistake. Could that just be changed by an
integer value in order to be modified the PIT duration?

Another question that I wanted to make is about the total length of the ndn
packet on the wire. The publisher sets the payload size but how much this
could be increased? If it is go large, then fragmentation of the data
message takes place before to be put on the wire?

Thanks in advance.


On Tue, Aug 18, 2015 at 5:32 PM, Spyridon (Spyros) Mastorakis <
spiros.mastorakis at gmail.com> wrote:

> Hi Gustavo,
>
> > Hello Spyridon,
> >
> > First of all thanks for the answer.
> >
> > I was wondering if the deletion of an entry in the PIT could be modified
> for another value different than the lifetime of the last interest
> received. I was thinking on a delay of 250ms because I am trying to
> simulate a satellite connection but I realize that a same content is issued
> two times because of the propagation delay (500ms) and it shouldn't be like
> this because the content will be forwarded but due to the large waiting
> time for the content then a new interest requesting the same content is
> issued.
>
> In order to set the expiration time of a PIT entry to a value other than
> the Interest lifetime, you will need to modify this code:
>
>
> https://github.com/NDN-Routing/ndnSIM/blob/master/NFD/daemon/table/pit-face-record.cpp#L45
>
>
> > Another question is if it is possible to have two same contents on the
> channel at approximately 4s of difference between both of them even when
> the first content was delivered succesfully. Is this behaviour because of
> the expiration of the interest lifetime that the consumer issues again an
> interest requesting the same content?
>
> This is most probably because of the timeouts on the application side. You
> will need to modify the way that the consumer application retransmits the
> Interests.
>
> --
> Spyridon (Spyros) Mastorakis
> Personal Website: http://cs.ucla.edu/~mastorakis/
> Internet Research Laboratory
> PhD Computer Science
> UCLA
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20150820/8d0a93dc/attachment.html>