On Tue, Jun 03, 2025 at 07:52:48AM +0200, Gert Doering wrote:
Hi,
> On Mon, Jun 02, 2025 at 11:35:24PM +0200, Piotr Strzyzewski wrote:
> > > > It is not. I actually tested it using a random /24 in the TEST database.
> > > > First, I created a /24 inetnum object with the ALLOCATED PA status, and
> > > > then 255 inetnum objects with the SUB-ALLOCATED PA status - ranging from
> > > > 192.0.2.0 - 192.0.2.254 down to 192.0.2.0 - 192.0.2.0. As a side note,
> > > > the last one doesn't make much sense, since it's not possible to create
> > > > any smaller inetnum object with ASSIGNED PA status.
> > >
> > > That is not surprising - but I was talking "depth", not "breadth".
> >
> > Same here. I was talking "depth" as well.
> >
> > > So the maximum depth of nesting in a /24 is 8, then you hit /32, and
> >
> > My observation is that it was 1 allocation having 255 sub-allocations
> > nested one in another. Like 192.0.2.0 - 192.0.2.0 nested in 192.0.2.0 -
> > 192.0.2.1 nested in 192.0.2.0 - 192.0.2.2 nested ... in 192.0.2.0 -
> > 192.0.2.254 (last, most outer sub-allocation) nested in 192.0.2.0 -
> > 192.0.2.255 (allocation). So the maximum depth of nesting in a /24 is
> > 255.
>
> No :-)
Yes ;-)
> 192.0.2.0/24
> 192.0.2.0/25
> 192.0.2.0/26
> ...
> 192.0.2.0/32
>
> ... this is what I called "nesting in depth", and the limit is 8.
Fine with me. But this is not what I was trying to explain. The inetnum
object is not limited to bit boundaries.
> Filling each level (192.0.2.0/32, 192.0.2.1/32, 192.0.2.2/32, ... .255/32)
> is what I called "width" - and of course, you can add hundreds of object
> that way, without mentioning "SUB-ALLOCATED" at all (just tag the /32s
> as "ASSIGNED").
Sure, but that's not what I did. These weren't /32s.
Since I probably wasn't very clear, which led to the misunderstanding,
let me explain one last time using a small diagram what I've done:
192.0.2.0 - 192.0.2.255 (/24 ALLOCATION)
|-> 192.0.2.0 - 192.0.2.254 (255 addresses; SUB-ALLOCATION)
|-> 192.0.2.0 - 192.0.2.253 (254 addresses; SUB-ALLOCATION)
...
|-> 192.0.2.0 - 192.0.2.1 (2 addresses; SUB-ALLOCATION)
|-> 192.0.2.0 - 192.0.2.0 (the only /32 in my example; SUB-ALLOCATION)
In this scenario, there are 255 levels. Hope that's clearer now.
Best,
Piotr
--
Piotr Strzyżewski
-----
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/
