Bug #5012
closed
ChronoSync treats NACK as timeout
Added by Ashlesh Gawande about 5 years ago.
Updated about 5 years ago.
Description
Can react early on say, NoRoute NACK, and synchronize quicker by sending another sync interest.
Is more helpful in the case when sync interest lifetime is long.
- Status changed from New to Resolved
- Status changed from Resolved to In Progress
It is still beneficial to react on NoRoute NACK with respect to sync times. Sync interest lifetime maybe long and lead to slow sync.
Reacting to NACK may be removed after #4931 is implemented and multicast can be configured to retain PIT, not send NACK, and retransmit interest on FIB creation. But probably should keep it in case the NACK does come.
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF
Updated by