NFD » ndn-cxx

• Sends two interests: one to the indicated face in LSA data and one to the network. In NLSR we know there is no route via network that's why we want to use the face id

This is specific in NLSR and does not happen elsewhere.

• Sends immediate retransmissions upon Nack (there is a todo in the code to "Retry for some amount of time")

This should be fulfilled in existing fetcher. It does not warrant creating a new fetcher.

• The number of retransmissions are not tied to a particular certificate but are for the certificate fetcher overall

I don't understand the problem. If it's indeed a problem, this should be fixed in the existing fetcher.

This is specific in NLSR and does not happen elsewhere.

Maybe could happen in sync, where we would want to send the certificate interest to the sync data arrival face.
We should provide a choice to not send to the network with default being send.

This should be fulfilled in existing fetcher. It does not warrant creating a new fetcher

Alright, makes sense.

I don't understand the problem. If it's indeed a problem, this should be fixed in the existing fetcher.

Okay, seems like this is my misunderstanding. In the latest change on gerrit I am using a variable local to the certificate fetcher for maximum delay to try out for. I guess I need to add a variable to the certificate request, similar to m_nRetriesLeft. It is a public variable that is supposed to be set by the application. Which I think can only be done by having a custom validator and updating the value in validate function's check policy callback. Is there an easier way to set m_nRetriesLeft?