On Sep 15, 2010, at 10:50 AM, Samuel Weiler wrote: > This is about consolidating publication points and (for some) avoiding > running an rsync server. It also reduces the number of rsync sessions needed > to retrieve the whole PRKI. Meshing structures, by which I assume you mean > putting objects in a common directory structure, is necessary to the end, but > isn't so much a goal in and of itself.
Thanks. That answers my question. > rsync setup times are not a general concern because we're expecting to reduce > the number of rsync sessions a relying party much use to fetch the whole RPKI > down to something manageable. Consolidating publication points serves > several purposes and would probably be desirable even if the rsync problem > were fixed. > > From an engineering standpoint, I think Rob, et. al. have taken the view that > rsync is a take-it-or-leave it thing, slow setup included, and moving to an > entirely different transport isn't worth the effort. I was simply trying to understand the observation, not restart the rsync vs. http discussion. However, as I recall the stated reason for staying with rsync was that http would be less efficient. That is why I am surprized to see text stating there is a problem with rsync. -andy _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
