Actions
Task #4134
closed
Check for self in ChronoSync updates
Start date:
06/15/2017
Due date:
% Done:
0%
Estimated time:
Description
Even though #4117 is not yet in the wild as a release version and it does not appear to be necessary, nevertheless Ashlesh has found an incidence in the testbed logs of routers receiving their own updates.
For the record, it is not known at this point why routers can receive their own sync updates, because:
- NFD should not send a Data back to the Face it just received it from, even if there is a breadcrumb trail leading there.
- NFD can detect if a Data is looping through use of the nonce, and should not use that Data, even if it comes from another Face.
- ChronoSync should be cancelling any pending Interests when it publishes an update, anyway.
However, it seems to be the case that routers can receive their own updates, so it is necessary to check that the updates are from ourself.
Updated by Nicholas Gordon almost 7 years ago
- Status changed from New to Closed
This patch was reverted, so we are again checking for self in ChronoSync updates.
Updated by Nicholas Gordon almost 7 years ago
- Status changed from Closed to Code review
Updated by Nicholas Gordon almost 7 years ago
- Status changed from Code review to Closed
Actions