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 ]
Nick Hilliard
nick at foobar.org
Tue Nov 29 19:30:34 CET 2022
denis walker wrote on 29/11/2022 13:00: > If we allow these objects to authorise hierarchical AS-SET objects with > 'source: RIPE' we have in effect turned non authoritative data back into > authoritative data. If we give the related AS-SET objects 'source: > RIPE-NONAUTH' we make it clear that these objects are also not > authoritative. Consumers of the data should make their own informed > decisions about the content of these AS-SET objects. if ASnnnnn has source: RIPE-NONAUTH, then the corresponding as-set would be ASnnnnn:FOOBAR, so this would also need to be RIPE-NONAUTH. I don't see an issue with RIPE-NONAUTH aut-nums being able to create scoped RIPE-NONAUTH as-sets. This also gives a clear route for garbage collection: if the aut-num becomes invalid, then the corresponding as-sets also become invalid. IIRC it's not possible to create new aut-num objects with source: RIPE-NONAUTH? Nick
- 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 ]