Actions
Feature #3879
closed
ASF strategy should propagate NACK if all nexthops are NACKed
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.
Updated by Junxiao Shi almost 8 years ago
- Related to Feature #3176: NACK in multicast strategy added
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.
Updated by Ashlesh Gawande almost 5 years ago
- Assignee changed from Ashlesh Gawande to Saurab Dulal
Updated by Davide Pesavento over 1 year ago
- Tags set to ASF
- Tracker changed from Task to Feature
- Start date deleted (
12/06/2016)
Updated by Davide Pesavento 9 months ago
- Status changed from New to Duplicate
- Assignee deleted (
Saurab Dulal)
Updated by Davide Pesavento 9 months ago
- Is duplicate of Feature #5311: Add nack propagation to ASF added
Actions