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] [routing-wg] Last Call - creation of new out of region ROUTE(6) objects
- Previous message (by thread): [db-wg] Last Call - creation of new out of region ROUTE(6) objects
- Next message (by thread): [db-wg] Last Call - creation of new out of region ROUTE(6) objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Clement Cavadore
clement at cavadore.net
Thu Jan 11 09:59:42 CET 2018
Hello Denis, On Thu, 2018-01-11 at 00:03 +0000, Job Snijders wrote: > I don't think there is a good case to continue to allow the creation of > new ROUTE(6) objects in the RIPE DB for non RIPE address space. > > I'm seeing quite some abuse of this 'feature', where spammers/hijackers > register out-of-region prefixes to sneak them into people's prefix-list > filters. It would be good if that hole can be plugged. > > Separately, a study should be done on how to deal with the existing > non-RIPE-managed ROUTE(6) objects in the DB. Maybe some cleanup can be > done for at least for a subset of those objects. I fully agree with Job's position regarding the foreign route(6) objects. I think that we should also do a cleanup the existing objects too. Kind regards, -- Clément Cavadore
- Previous message (by thread): [db-wg] Last Call - creation of new out of region ROUTE(6) objects
- Next message (by thread): [db-wg] Last Call - creation of new out of region ROUTE(6) objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]