Project

General

Profile

Actions

Task #5027

closed

Avoid sending NACK to multicast Faces

Added by Teng Liang over 4 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
High
Assignee:
-
Category:
Forwarding
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

NACK is not supposed to be sent to multicast Faces, because Data may be served by others. However, the current NFD does not avoid sending NACK to multicast Faces. This task is to add a check on Face before sending NACK.

Actions #1

Updated by Teng Liang over 4 years ago

  • Subject changed from NACK handling: avoid sending NACK to multicast Faces to Avoid sending NACK to multicast Faces
Actions #2

Updated by Davide Pesavento over 4 years ago

  • Description updated (diff)
  • Start date deleted (10/13/2019)
Actions #3

Updated by Davide Pesavento over 4 years ago

Can you clarify under what circumstances you saw this happen? The forwarder already ignores attempts to send a Nack to non-point-to-point faces and drops the packet:
https://github.com/named-data/NFD/blob/4bd4f71f608413405209876728277ac1a48df7b0/daemon/fw/forwarder.cpp#L477

Actions #4

Updated by Teng Liang over 4 years ago

Two producers and one consumer on the same LAN, the consumer has a multicast Face that can reach both producers. We tested self-learning and best-route (with route manually configured to the multicast Face). Both strategies will receive no-route NACK at consumer, after one of the producer's app is killed. We tested ndnping and ndncatchunks. Ashiq and Ju did the tests and observed the results. I will double check with them.

Actions #5

Updated by Teng Liang over 4 years ago

  • Status changed from New to Closed

Issue closed because of wrong testing.

Actions #6

Updated by Davide Pesavento over 4 years ago

  • Status changed from Closed to Rejected
  • Target version deleted (v0.7)
Actions

Also available in: Atom PDF