Hi [disclaimer, I am no longer involved in RIPE NCC implementation, but I am now involved in NLnet Labs implementation]
On 10 Oct 2018, at 10:05, nusenu <nusenu-lists@riseup.net> wrote:
Jay Borkenhagen:
Probably a better behavior for rpki-validator-3 to take to avoid needlessly filling up logs, etc., with failed attempts would be to back off when re-trying unreachable repos. If a normally-reachable repo suddenly goes quiet, re-try a few times as normal, but then gradually increase the time until the next attempt, up to some maximum interval -- possibly several hours.
yes, this sounds reasonable.
Imho retries are cheap, but it is better to bother the logs, and operator, only if there are state changes. Related, the trust anchors overview pages also shows the current state of repository availability to operators: https://rpki-validator.ripe.net/trust-anchors But, there seems to be a bug in the validator when viewing the page for the APNIC TA. Tim