On 3/22/13 11:40 PM, Christopher Morrow wrote:
> On Fri, Mar 22, 2013 at 9:33 PM, Oleg Muravskiy <[email protected]> wrote:
<snip> hoping not to cut important parts
>>
>> Although in a hosted model it's possible to run just one CA and one
>> publication point for all hosted clients, in practice no one from RIRs is
>> doing that.
>> In our hosted system we have 1370 CAs, and each CA has it's own publication
>> point, although they all appear to be in the same rsync tree.
>
> so, this leads to some confusion, but does make the repository one
> monolithic item to kill/sync-from. It's convenient, right up until
> it's not :( I'm not sure when that point will arrive, but ...
>
I liked what you proposed in [1]
ca-1234ab.repository.ur-rir.net
ca-1235bb.repository.ur-rir.net
This would help to move a problematic CA out of the monolithic repo.
However, this would make a cache to create multiple rsync sessions to
retrieve objects and lowering its performance (according to Rob's
measurements with RIPE NCC repo). Isn't it?
[1] http://www.ietf.org/mail-archive/web/sidr/current/msg05835.html
/as
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
