Bug #4725
closedDefault freshness of Data packets
0%
Description
By default Producer
application sets the freshness of all generated Data packets to ZERO. Althgouh in the application layer zero is interpreted to infinity, this causes unexpected behavior at NFD layer, in CS replacement policy.
By running a simple scenario in ndnSIM (where there is one consumer, one producer, and one node in the middle), and enabling the log component for Priority Fifo Cache replacement policy we can see an output like below:
As is shown, replacement policy moves Data packets from FIFO queue to STALE queue, immediately, because it does not understand the meaning of zero freshness.
Accordingly, we can fix this problem by changing the default value of Data packets. But the question would be what should be the default freshness.
The second solution would be changing the NFD layer.
Files
Updated by Alex Afanasyev over 5 years ago
This is a bug in the implementation then. It should be interpreted as not fresh and it should get to the "stale" queue (and your picture confirms that).
Which part of it is an undefined behavior?
Updated by Chavoosh Ghasemi over 5 years ago
Based on the discussion on Sep 5, 2018, Zero freshness means "non-fresh" Data packet, based on which the mentioned behavior (i.e. moving Data packets to stale queue) makes sense.
(Please look at https://redmine.named-data.net/issues/4728)