Project

General

Profile

Actions

Feature #4903

open

ASF strategy should try alternative paths (if available) if a NACK is received

Added by Saurab Dulal over 5 years ago. Updated 10 months ago.

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

0%

Estimated time:
Tags:

Description

Currently, ASF considers NACK as a timeout. It should instead try an alternative path if NACK is received.


Related issues 1 (0 open1 closed)

Related to NFD - Feature #5311: Add nack propagation to ASFClosedAlexander Lane01/23/2024

Actions
Actions #1

Updated by Saurab Dulal over 5 years ago

  • Subject changed from ASF strategy should try alternative paths (if available) if a NACK is received. to ASF strategy should try an alternative path/s (if available) if a NACK is received.
Actions #2

Updated by Saurab Dulal over 5 years ago

  • Assignee set to Saurab Dulal
Actions #3

Updated by Davide Pesavento over 5 years ago

  • Tracker changed from Task to Feature
  • Subject changed from ASF strategy should try an alternative path/s (if available) if a NACK is received. to ASF strategy should try an alternative path/s (if available) if a NACK is received
  • Category set to Forwarding
Actions #4

Updated by Ernest McCracken over 5 years ago

I have implemented this though untested.

Some things to note:

  • You don't want to retransmit indefinitely. There needs to a max retries.
  • Don't retransmit NACK'd probes.
Actions #5

Updated by Saurab Dulal over 5 years ago

Ernest McCracken wrote:

I have implemented this though untested.

Some things to note:

  • You don't want to retransmit indefinitely. There needs to a max retries.
  • Don't retransmit NACK'd probes.

Do you have your code somewhere?

Also, I have some question regarding max retries and NACK'd probes. I will ask you over the meeting and will post it here afterward.

Actions #6

Updated by Ernest McCracken over 5 years ago

Strange I did not get notified of your response.

We do have code but I will have to make sure it can be shown.

Also we modified our design of this. We removed the hop by hop retry on NACK because more thought needs to be had on consequences of intermediate hops doing retransmission.

Instead for now when the client retransmits an interest we ignore NACK's faces.

Actions #7

Updated by Davide Pesavento over 1 year ago

  • Tags set to ASF
  • Start date deleted (04/01/2019)
Actions #8

Updated by Davide Pesavento 10 months ago

  • Subject changed from ASF strategy should try an alternative path/s (if available) if a NACK is received to ASF strategy should try alternative paths (if available) if a NACK is received
  • Assignee deleted (Saurab Dulal)
Actions #9

Updated by Davide Pesavento 10 months ago

Actions

Also available in: Atom PDF