Use /localhop component in Sync prefix to reduce duplicate NACKs
Currently, Sync Interests are multicasted at each router which can result in Interests traversing a loop; these loops cause NFD to send a Duplicate NACK in response.
If instead the Sync prefix was prefixed with the /localhop component, the Interests would only be multicasted and delivered to immediate neighbors.
#1 Updated by Junxiao Shi over 2 years ago
/localhop cannot reduce Nack-Duplicates in the case of ChronoSync Interests.
/localhop Interest forwarding as follows:
- If PIT entry has at least one InRecord from a local face, it can be forwarded to local faces and non-local faces.
- If PIT entry has all InRecords from non-local faces, it can only be forwarded to local faces.
As soon as the local NLSR has expressed a sync Interest, NFD can forward a sync Interest received from one remote router to another remote router, and cause the same amount of Nack-Duplicates.
#9 Updated by Ashlesh Gawande about 2 years ago
- Status changed from Closed to Feedback
advertise and withdraw does not work when security is turned on after this patch. Validation of received interest fails:
Name prefix update error (code: 403) Not sure if it is because of this patch.
My bad, the interest needs to be signed when security is enabled. It is working as expected.