Bug #4066
Updated by Ashlesh Gawande over 7 years ago
An application (ex: In PSync protocol, two nodes might send each other almost simultaneous sync protocol) may send an interests (on multicast prefix) as shown in attached figure. Sync interests have the same name. If c's sync interest I1 at time t1 arrives on d just after d has sent a sync interest, c's sync interest is suppressed by multicast strategy and receive an never delivered to d (In the case where c's sync interest I2 arrives at time t2 from the same face within d just before d sends a short period of time (t2 - t1 < 10 ms). sync interest, then d's sync interest would be suppressed). By current implementation A solution might be to add random delays before sending sync interest but that slows the sync and does not work 100% of retransmission suppression with respect to pitEntry's latest outRecord time, I2 will be suppressed. the time. This issue will implement a per upstream retransmission suppression as suggested in [note1](https://redmine.named-data.net/issues/4066#note-1) and use it in In multicast strategy (Not sure logic we should suppress only if other strategies need it). all the faces already have an interest sent out.