Bug #4066
closed
Multicast strategy retransmission suppression does not take face into account
Added by Ashlesh Gawande over 7 years ago.
Updated almost 7 years ago.
Description
An application (ex: sync protocol) may send an interest I1 at time t1 and receive an interest I2 at time t2 from the same face within a short period of time (t2 - t1 < 10 ms).
By current implementation of retransmission suppression with respect to pitEntry's latest outRecord time, I2 will be suppressed.
This issue will implement a per upstream retransmission suppression as suggested in note1 and use it in multicast strategy (Not sure if other strategies need it).
Files
In multicast logic we should suppress only if all the faces already have an interest sent out.
This is insufficient. In topology below, if both B and C express an Interest within a short period, A would receive the Interest twice, which is unnecessary overhead.
A
|
B-R-C
The suppression timer should be enforced per upstream rather than per PIT entry. The Interest should be forwarded to an upstream peer if no Interest has been forwarded to it within last "suppression period".
- Status changed from New to In Progress
- Assignee set to Ashlesh Gawande
- Target version set to v0.6
Updated description for clarity.
- % Done changed from 0 to 90
Will try to update NFD dev guide soon.
Also, is this functionality desired in other strategies like best route strategy or per pit entry suppression is good enough?
- % Done changed from 90 to 100
- Status changed from In Progress to Closed
- Related to Feature #5140: Add per upstream suppression to ASF strategy added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 