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] proposal: disallow creation of new non-hierarchically named AS-SET objects
- Previous message (by thread): [db-wg] proposal: disallow creation of new non-hierarchically named AS-SET objects
- Next message (by thread): [db-wg] proposal: disallow creation of new non-hierarchically named AS-SET objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Yang Yu
yang.yu.list at gmail.com
Wed Nov 16 11:06:57 CET 2022
I support this proposal. >It seems Amazon has no recourse to get the AS-AMAZON object removed from >the RIPE database; because the existence of that object in the RIPE >database does not violate any policies (as far as I know). Also ran into this issue and would like to see policy support to handle this kind of abuse. On Mon, Nov 14, 2022 at 3:08 PM denis walker via db-wg <db-wg at ripe.net> wrote: > Interesting timing. I was about to make the same suggestion but for a > different reason...accountability. Currently ANYONE can create a set > object in the RIPE Database. You can be completely anonymous, not a > member or LIR, hold no resources. All you need to do is create a ROLE, > MNTNER and set object. Anyone with an email can make a RIPE account and start creating objects in RIPE database. In other registries there are usually some safeguards on user / mntner object creation. Limiting database updates to only accounts associated with LIR sounds reasonable. Yang
- Previous message (by thread): [db-wg] proposal: disallow creation of new non-hierarchically named AS-SET objects
- Next message (by thread): [db-wg] proposal: disallow creation of new non-hierarchically named AS-SET objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]