On Fri, 30 Sept 2022 at 09:59, Tim Bruijnzeels <[email protected]> wrote: > I disagree that having out-of-region objects in the RIPE NCC RPKI repository > creates a mess. The comparison with IRR is wrong for a number of reasons.
I completely agree, the comparison with IRR is wrong and makes no sense at all. We are talking about RPKI, not IRR2. The objections raised are relevant if we would spin up a new IRR database, but that is not what we are doing here. If we overly restrict RIPE services, then new external services need to cover for this, just like RADB and friends are covering for the lack of ARIN features today (or in the past) in the IRR world. A lot of people spinning up their own http/rsync infrastructure is a nightmare. Just think of all the connections and reliability issues of CAs in validator outputs we have today. And I don't think the number of organizations operating across multiple RIR regions (or more specifically: working with resources from multiple RIR regions) is that low. Lukas -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/routing-wg
