[ndnSIM] [EXT] Interest loop problem in VNDN (v2v scenario)
zohanoor67 at gmail.com
Tue Jan 12 01:01:02 PST 2021
It helped a lot.
On Tue, Jan 12, 2021 at 2:25 AM Junxiao Shi <shijunxiao at email.arizona.edu>
> Hi Sonia
> Dead Nonce List (DNL) is designed to prevent persistent Interest
> loops, especially when the duration of the loop is longer than the PIT
> entry lifetime (usually the InterestLifetime).
> DNL does not stop a producer/cache from responding to the same Interest
> multiple times, as long as a persistent loop is not occurring.
> Have a look at Named Data Networking in Local Area Networks
> http://hdl.handle.net/10150/625652 section 3.3 for how loop prevention
> works and what's the role of DNL.
> See also the original bug report
> https://redmine.named-data.net/issues/1953 .
> DNL works only if the Content Store is enabled and has reasonably large
> See dead-nonce-list_20141004.pptx (attachment of the above bug report)
> page 11 for the reason.
> Yours, Junxiao
> On Mon, Jan 11, 2021 at 2:41 AM Sonia via ndnSIM <ndnsim at lists.cs.ucla.edu>
>> *External Email*
>> I have two concerns.
>> 1: In my v2v scenario, the producer receives X number of the same
>> Interest packet via multipath communication. The producer replies X time
>> with Data. What I understand is that it should reply only 1 time
>> considering the duplicate PIT and DeadNonce list check in Incoming interest
>> 2: In my v2v ad-hoc scenario, the first 3 packets receive correctly.
>> however, Interest for the next chunk of data starts looping in the network.
>> This does not happen with contenstore enable. Only happens when I disable
>> the content store. Moreover, this Interest also receives hundred and
>> thousand of times to producer and each time the producer responds with data
>> which never reaches the consumer.
>> Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ndnSIM