[Nfd-dev] multicast strategy questions

[Dehart, John]

On Jul 11, 2018, at 12:14 PM, Dehart, John <jdd at wustl.edu<mailto:jdd at wustl.edu>> wrote:


On Jul 11, 2018, at 10:46 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

I think for ad-hoc faces you have to turn then on in the nfd.conf file.

Since the second interest came after 10 ms it is considered a re-transmission and will be forwarded.

So, it is considered a retransmission even if it arrived on a different face?


OK. I see that 5.2.1 answers my question that yes, it does not consider where it comes from when making the decision.

Thanks for the help.
John

More info under 5.2.1 "Retransmission suppression interval" in the nfd devguide:
http://named-data.gitlab.io/TR-NDN-0021-NFD-dev-guide/ndn-0021-nfd-guide.pdf
Also see 5.2.2 for Multicast Strategy interest forwarding.

Strategy parameters feature is available but strategies have not been modified yet to configure them.
https://redmine.named-data.net/issues/3868

Ashlesh
________________________________
From: Nfd-dev <nfd-dev-bounces at lists.cs.ucla.edu<mailto:nfd-dev-bounces at lists.cs.ucla.edu>> on behalf of Dehart, John <jdd at wustl.edu<mailto:jdd at wustl.edu>>
Sent: Monday, July 9, 2018 3:50:03 PM
To: <nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>>
Subject: [Nfd-dev] multicast strategy questions



All:

I have the following snippet of a packet trace that I am trying to understand. All of the packets are for the same name.

The topology for this is that there are three endpoints: 192.168.1.2, 192.168.2.2 and 192.168.3.2 that are all only connected to  a node: 192.168.21.2.
Node 192.168.21.2 is also connected to the rest of the network only through the node 192.168.25.1. The rest of the network contains other endpoints.

There is also an app running on 192.168.21.2 that is looking for this same piece of data. So the Second Nonce= 582128689 is
probably because of this app.

My question is why does 192.168.21.2 send a second Interest to 192.168.1.2    12 ms after the first one it sent?
Shouldn’t there be a PIT entry for that data name active at that point?

Similarly, why does 192.168.21.2 send an Interest back to 192.168.25.1?

I am using the multicast strategy. I know that there are some differences in how it works for ad-hoc faces.
How do I tell if my face is for some reason ad-hoc?

Thanks,
John


1531097314.703293 From: 192.168.25.1, To: 192.168.21.2, Tunnel Type: UDP, INTEREST: /ndn/broadcast/jdd/name2/name3/name4/name5/701?ndn.InterestLifetime=1500&ndn.Nonce=3488903727
1531097314.703522 From: 192.168.21.2, To: 192.168.1.2, Tunnel Type: UDP, INTEREST: /ndn/broadcast/jdd/name2/name3/name4/name5/701?ndn.InterestLifetime=1500&ndn.Nonce=3488903727
1531097314.703612 From: 192.168.21.2, To: 192.168.2.2, Tunnel Type: UDP, INTEREST: /ndn/broadcast/jdd/name2/name3/name4/name5/701?ndn.InterestLifetime=1500&ndn.Nonce=3488903727
1531097314.703694 From: 192.168.21.2, To: 192.168.3.2, Tunnel Type: UDP, INTEREST: /ndn/broadcast/jdd/name2/name3/name4/name5/701?ndn.InterestLifetime=1500&ndn.Nonce=3488903727
1531097314.714403 From: 192.168.2.2, To: 192.168.21.2, Tunnel Type: UDP, NACK: NoRoute, /ndn/broadcast/jdd/name2/name3/name4/name5/701?ndn.InterestLifetime=1500&ndn.Nonce=3488903727
1531097314.714538 From: 192.168.3.2, To: 192.168.21.2, Tunnel Type: UDP, NACK: NoRoute, /ndn/broadcast/jdd/name2/name3/name4/name5/701?ndn.InterestLifetime=1500&ndn.Nonce=3488903727

1531097314.715668 From: 192.168.21.2, To: 192.168.25.1, Tunnel Type: UDP, INTEREST: /ndn/broadcast/jdd/name2/name3/name4/name5/701?ndn.InterestLifetime=1500&ndn.Nonce=582128689
1531097314.715753 From: 192.168.21.2, To: 192.168.1.2, Tunnel Type: UDP, INTEREST: /ndn/broadcast/jdd/name2/name3/name4/name5/701?ndn.InterestLifetime=1500&ndn.Nonce=582128689
1531097314.715845 From: 192.168.21.2, To: 192.168.2.2, Tunnel Type: UDP, INTEREST: /ndn/broadcast/jdd/name2/name3/name4/name5/701?ndn.InterestLifetime=1500&ndn.Nonce=582128689
1531097314.715926 From: 192.168.21.2, To: 192.168.3.2, Tunnel Type: UDP, INTEREST: /ndn/broadcast/jdd/name2/name3/name4/name5/701?ndn.InterestLifetime=1500&ndn.Nonce=582128689
1531097314.725586 From: 192.168.1.2, To: 192.168.21.2, Tunnel Type: UDP, DATA: /ndn/broadcast/jdd/name2/name3/name4/name5/701
1531097314.725598 From: 192.168.2.2, To: 192.168.21.2, Tunnel Type: UDP, INTEREST: /ndn/broadcast/jdd/name2/name3/name4/name5/701?ndn.InterestLifetime=1500&ndn.Nonce=1523237434
1531097314.725879 From: 192.168.21.2, To: 192.168.25.1, Tunnel Type: UDP, DATA: /ndn/broadcast/jdd/name2/name3/name4/name5/701
1531097314.726178 From: 192.168.21.2, To: 192.168.2.2, Tunnel Type: UDP, DATA: /ndn/broadcast/jdd/name2/name3/name4/name5/701
1531097314.726817 From: 192.168.1.2, To: 192.168.21.2, Tunnel Type: UDP, DATA: /ndn/broadcast/jdd/name2/name3/name4/name5/701
1531097314.727217 From: 192.168.3.2, To: 192.168.21.2, Tunnel Type: UDP, INTEREST: /ndn/broadcast/jdd/name2/name3/name4/name5/701?ndn.InterestLifetime=1500&ndn.Nonce=2774503116
1531097314.727683 From: 192.168.21.2, To: 192.168.3.2, Tunnel Type: UDP, DATA: /ndn/broadcast/jdd/name2/name3/name4/name5/701

_______________________________________________
Nfd-dev mailing list
Nfd-dev at lists.cs.ucla.edu<mailto:Nfd-dev at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20180711/e513b663/attachment-0001.html>