At 10:56 PM -0700 9/7/10, Terry Manderson wrote:
...

Although I think I would be reluctant to add another object, for the same
complexity reasons that exist in the manifest instance and I'm not sure that
it will avoid the issues about concurrent modifications as the RP's fetch
may run longer than the creation/destruction/validity of the object as well
as any update to the repository. This also makes me think about the depth 0,
1, or infinity issues of directory and subdirectories.

I don't understand you reference here. A lock on a directory need not affect access to sub-directories. The rekey design that Geoff developed (and that I now co-author) restricts changes to a directory for rekey, to that directory. And the 1-day (minimum) staging period allows a reasonable interval to fetch the new CA cert (and the subordinate CRL and manifest) before objects at the next level are replaced.

...
It sounds like system hackery, but I feel more comfortable in looking
towards recommendations about how the directory structure is laid down,
given that rsync is file based and not block based, and after a repository
is constructed then new file-lists and transfers (for a client) can be
directed at the latest repository version. Existing rsync processes would
need to stay within the state of the repository as it was when they were
started.

I don't think we should make too many assumptions about the directory structure, other than what is mandated by the overall system design. For example, while a lot of these files will be in repository instances operated by RIRs, I've heard folks suggest that big ISPs may operate their own repositories, containing their objects and objects for their customers. Also, if one tries to parallelize repository access, to avoid potential DoS concerns, then one may have a list of URIs to visit, and they may not be visited in a purely top-down fashion. So I think we should focus on per-directory consistency.

Steve
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to