Hi Randy This is a good question. The whole purpose of the "status:" attribute is to describe and document real world networks from an administrative point of view. Also to 'impose' some structure on the networks with a set of rules. There are some gaps in those rules, like allowing an infinite number of levels in a legacy network or with sub-allocations. This doesn't make sense from either a real world or an administrative perspective. My suggestion is that we fill those gaps.
cheers denis On Fri, 2 May 2025 at 17:58, Randy Bush <[email protected]> wrote: > > > Is it reasonable to limit the number of levels of SUB-ALLOCATED PA to > > 4? That is the most we have now in the RIPE Database. Or do you have > > another number in mind...maybe even 1? > > > > Should there be a limit on the number of levels in a LEGACY hierarchy? > > Currently it is infinite. > > is there a technical or business reason for this? otherwise it appears > to be bikeshedding. if so, magenta please. > > randy ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/db-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
