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/db-wg@ripe.net/

[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 ]

Niall O'Reilly niall.oreilly at ucd.ie
Wed Nov 23 00:30:19 CET 2022

On 22 Nov 2022, at 19:11, Nick Hilliard via db-wg wrote:

> Careful with this, e.g. AS-NULL. There are some situations where 
> referencing an empty set can be useful in RPSL.

I'm not sure whether Nick meant this as a single exception,
or rather as an example of a category of useful empty sets.

I can well imagine that most "operationally empty objects"
(as Denis put it) are either useless or troublesome.

As Nick says, "Careful with this."

Niall

• 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 ]