Hi Nathalie, On 04/12, Nathalie Trenaman wrote: > Dear colleagues, > > <snip/> > > We are planning on changing our publication infrastructure and using the same > "revisions" RRDP uses for the content of the rsync repository. Rsync is an > officially supported distribution protocol for RPKI repository data, and it > is one of our highest priorities that the data published is atomic and > consistent. We plan to release the new publication infrastructure in Q2/Q3 > 2021. Part of this work will mitigate these non-repeatable-reads for clients > using rsync. > > We will update you on our progress during RIPE 82, taking place online from > 17-21 May 2021. > The above description seems to suggest that repository access via rsync is an optional extra that the RIPE NCC provides as a value add.
However, as of course you know, rsync is the only mandatory to implement access method *today* and we are not yet on an agreed path towards an RRDP-only future. It seems to me that this issue deserves the same urgency as "the publication server periodically reboots when used correctly". If that requires a workaround (of the form suggested by others) now, and then a redesign in 6 months, fine. But it is a dis-service to the Internet community as a whole to skip the "workaround now" step. Cheers, Ben
signature.asc
Description: PGP signature
