Feature #3879
closed
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.
- Assignee changed from Ashlesh Gawande to Saurab Dulal
- Tags set to ASF
- Tracker changed from Task to Feature
- Start date deleted (
12/06/2016)
- Status changed from New to Duplicate
- Assignee deleted (
Saurab Dulal)
Also available in: Atom
PDF