Project

General

Profile

Actions

Feature #3879

closed

ASF strategy should propagate NACK if all nexthops are NACKed

Added by Ashlesh Gawande almost 8 years ago. Updated 10 months ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Forwarding
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Tags:

Description

So other nodes would rank those faces lower.


Related issues 2 (0 open2 closed)

Related to NFD - Feature #3176: NACK in multicast strategyClosedAshlesh Gawande

Actions
Is duplicate of NFD - Feature #5311: Add nack propagation to ASFClosedAlexander Lane01/23/2024

Actions
Actions #1

Updated by Junxiao Shi almost 8 years ago

Actions #2

Updated by Nicholas Gordon about 7 years ago

Additionally, after probems on the testbed in the week of October 9, 2017, some more issues arose:

The ASF strategy reacts identically to all kinds of NACKS, currently treating them as timeouts. This causes ASF to treat that nexthop as "not very suitable" for retrieving data. However, this isn't always true. The ASF strategy should understand the differences between NACKs, and treat them accordingly.

Actions #3

Updated by Ashlesh Gawande about 5 years ago

  • Assignee changed from Ashlesh Gawande to Saurab Dulal
Actions #4

Updated by Davide Pesavento over 1 year ago

  • Tags set to ASF
  • Tracker changed from Task to Feature
  • Start date deleted (12/06/2016)
Actions #5

Updated by Davide Pesavento 10 months ago

  • Status changed from New to Duplicate
  • Assignee deleted (Saurab Dulal)
Actions #6

Updated by Davide Pesavento 10 months ago

  • Is duplicate of Feature #5311: Add nack propagation to ASF added
Actions

Also available in: Atom PDF