This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] Issue affecting rsync RPKI repository fetching
- Previous message (by thread): [routing-wg] Issue affecting rsync RPKI repository fetching
- Next message (by thread): [routing-wg] Issue affecting rsync RPKI repository fetching
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Tue Apr 13 15:33:04 CEST 2021
> Would it be possible to drill down into these figures a bit more? I.e. > is it possible to work out how many are pulling the TAL via rsync, but > then using rrdp to synchronise their local instances? Or that came out badly garbled. I meant how many clients were pulling the trust anchor certs via rsync due to having older TALs installed on the local RP cache, and then downloading the manifest/roas data via rrdp afterwards because the TA contains both rsync and https locator information, and the RP software was able to select rrdp instead of rsync because that was presented as an option. Nick
- Previous message (by thread): [routing-wg] Issue affecting rsync RPKI repository fetching
- Next message (by thread): [routing-wg] Issue affecting rsync RPKI repository fetching
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]