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] RFO for RIPE NCC RPKI outage 16 February 2022
- Previous message (by thread): [routing-wg] RFO for RIPE NCC RPKI outage 16 February 2022
- Next message (by thread): [routing-wg] RFO for RIPE NCC RPKI outage 16 February 2022
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at fastly.com
Wed Feb 16 19:10:27 CET 2022
On Wed, 16 Feb 2022 at 19:07, Randy Bush <randy at psg.com> wrote: > thanks for the post mortem, ties. > > sra commented to me that, an rp doing protocol fall-over from rrdp to > rsync, or vice versa, has to do the full download as the data structure > is so different. i.e. load spike Perhaps it doesn’t need to be a full load: “rsync —compare-dest” (against a previously downloaded and validated set of signed objects) offers a path towards optimising the protocol fall-over. Kind regards, Job > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/routing-wg/attachments/20220216/a74be867/attachment.html>
- Previous message (by thread): [routing-wg] RFO for RIPE NCC RPKI outage 16 February 2022
- Next message (by thread): [routing-wg] RFO for RIPE NCC RPKI outage 16 February 2022
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]