SIDR working group, I humbly submit a proposal for your consideration. It is for an rsync replacement that for now I am calling the 'RPKI Repository Distribution Protocol (RRDP)'. It is intended to replace the use of rsync by the RPKI validators or at least re-open some previous discussion on possible replacements.
The primary benefit is that RRDP is a combination of a very limited Distributed Version Control System (DVCS) with a transport agnostic communication protocol. This means that repository changes can be snapshotted and retrieved as an atomic change. This solves the problem of in progress transfers when a new repository generation is kicked off. It also means that different protocols (HTTP/SSL/TLS/etc.) can be used for the actual transport. Finally, it can work with the existing rsync URIs and it can work alongside rsync at the same time. Should the protocol be considered for real adoption this should help to ease in gradual adoption. A brief paper that describes the protocol can be found at http://www.cobenian.com/documentation/rrdp.pdf. This is very much a first draft, but I would appreciate any feedback/comments you have and any interest you might have in trying to use this protocol with a real validator. I am all ears to suggestions for improvements. I would especially love to make it more aware of the contents of RPKI manifests. The beginning of a reference implementation can be found at http://www.github.com/cobenian/rrdp. This is not feature complete and certainly not compliant with the specification at the moment, but it should be in the very near future (a few days to a few weeks). Regards, Bryan (703) 828.5180 [email protected]
_______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
