[db-wg] proposal: disallow creation of new non-hierarchically named AS-SET objects

> Job Snijders wrote on Monday, November 14, 2022 6:41 PM:
> I think the solution is to - GOING FORWARD - disallow creation of new
> AS-SET objects which follow the 'short' naming style.

Forcing people to something they could already make use of? Wouldn't 
mind ... for sure it's minimizing the accidental collision of set
names (esp. in other RRs).

> The RIPE database engine blocking creation of short-named AS-SETs
> might help nudge the industry towards making hierarchical naming
> the norm.

If others follow. But even if all "important" ones follow - and as
Cynthia wrote - as long as RADB and other "open" major RRs are around
- the abuse of *evil* person registering the aut-num and a bad as-set
would be still possible.

So not a final solution, just improving the situation. 

Markus