On Jul 17, Edward Shryane <eshry...@ripe.net> wrote:
(With my IXP operator hat on...)
I now present some analysis of the RIPE-NONAUTH database for review. Perhaps we should not retire the RIPE-NONAUTH database completely as we don't know how it is being used, but we could take action to further reduce its size. Your feedback is appreciated.I agree that it is a good idea to remove the objects which are already represented in a another authoritative IRR. But I strongly suspect that the remaining records have an operational purpose (how many are for legacy ARIN resources?) and should be kept around at least for a while.
So I recommend that RIPE NCC starts with the uncontroversial cleanups and then we reassess the situation.
Does it even matter? I expect that the bgpq[34] users are explicitly listing the sources that they want to use.Should RIPE-NONAUTH Objects Be Returned By Default?
Should RIPE-NONAUTH objects with an exact match in another RIR database be deleted?
Yes: they are redundant.
Should unrouted RIPE-NONAUTH route(6) objects be deleted?
Yes, after a grace period, since they have no practical purpose. -- ciao, Marco
signature.asc
Description: PGP signature
----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/db-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
