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
Should RIPE-NONAUTH Objects Be Returned By Default? Does it even matter? I expect that the bgpq[34] users are explicitly
On Jul 17, Edward Shryane <eshryane@ripe.net> wrote: (With my IXP operator hat on...) 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. listing the sources that they want to use.
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