Hi Max,

I think your 'spot check' example highlights several aspects of the
ongoing discussion:

- some information in RIPE-NONAUTH can also be found $elsewhere
- RIPE-NONAUTH might be out-of-date compared to $elsewhere
- some information might only exists in RIPE-NONAUTH

All in all it seems there is some support to start pruning information
from the RIPE-NONAUTH dataset that can also be found elsewhere. In this
sense we move on from the "prune invalid information" strategy towards a
"prune redundant information" strategy.

Kind regards,

Job
-----
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/

Reply via email to