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
Wed Nov 30 18:59:13 CET 2022

Niall O'Reilly via db-wg wrote on 30/11/2022 16:15:
> If we indeed don't need a policy, I think it would be cleaner
> to make this a new NWI, as adding to an NWI after implementation
> work has begun seems, IMESHO, likely to cause confusion.

agreed.  In terms of breakage, we're carrying a 25yo basket of eggs. Any 
shift in position will is likely to cause a crack here or there.  It's 
unlikely that any shift in position will cause more breakage than 
introducing RIPE-NONAUTH in the first place.

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 ]