This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request
- Previous message (by thread): [db-wg] New on RIPE Labs: How We're Implementing the GDPR - the RIPE Database
- Next message (by thread): [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at ntt.net
Mon Feb 12 13:04:12 CET 2018
On Tue, Dec 05, 2017 at 12:04:59PM +0100, Tim Bruijnzeels wrote: > > On 5 Dec 2017, at 11:07, Job Snijders <job at ntt.net> wrote: > > > > ps. I'd leave the 'clean up out-of-region AUT-NUMs' for a separate > > discussion on how to handle that data. Combining datamodel changes > > and governance of existing data in the same topic might distract. > > This can be a separate effort. However, what I did not mention earlier > is that we probably should disallow the creation of new out-of-region > AUT-NUM objects if they are no longer required to authorise ROUTE(6) > objects. Yes, I support disallowing the creation of NEW out-of-region AUT-NUM and ROUTE objects. I keep seeing route objects covering non-RIPE IP space popping up in the RIPE IRR for nefarious purposes. An ideal outcome is that the RIPE IRR contains only RIPE NCC managed resources. A first step towards that goal is to stop accepting new "RIPE-NONAUTH" objects. Kind regards, Job
- Previous message (by thread): [db-wg] New on RIPE Labs: How We're Implementing the GDPR - the RIPE Database
- Next message (by thread): [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]