Bug #4066: Multicast strategy retransmission suppression does not take face into account - NFD - NDN project issue tracking system

Actions

Copy link

Bug #4066

closed

Multicast strategy retransmission suppression does not take face into account

Added by Ashlesh Gawande almost 7 years ago. Updated about 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Ashlesh Gawande

Category:

Forwarding

Target version:

v0.6

Start date:

04/26/2017

Due date:

% Done:

100%

Estimated time:

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

per_pit_entry_suppression_problem.jpg (106 KB) per_pit_entry_suppression_problem.jpg

Ashlesh Gawande, 07/25/2017 03:00 PM

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Junxiao Shi almost 7 years ago

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".

Actions

Copy link