Feature #4903
open
ASF strategy should try alternative paths (if available) if a NACK is received
Added by Saurab Dulal about 5 years ago.
Updated 3 months ago.
Description
Currently, ASF considers NACK as a timeout. It should instead try an alternative path if NACK is received.
- 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.
- Assignee set to Saurab Dulal
- 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
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.
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.
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.
- Tags set to ASF
- Start date deleted (
04/01/2019)
- 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)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by