Re: Problems with RIPE210

[Daniel Karrenberg <]

At 04:07 PM 6/28/00, Randy Bush wrote:

>> inetnum:     217.0.0.0 - 217.255.255.255
>> ...
>> min-alloc:   /20                                  <============

The reason I propose to put it in the inetnum is one of architectural
cleanness. This is clearly an attribute describing a property of
an address block. We have an object descibing an address block,
so the attribute should go there.

>it is not clear from your example how you expect me to compose the search
>which produces the table i derive manually today.  

A number of possibilitites here:

1) to get it for each /8

foreach $slasheight in (1..255) 
        whois -a -tinetnum $slasheight/8 | grep '^min-alloc:'

[other granularities left as an exercise]

2) to get all min-allocs of certain sizes

foreach $minalloc in (/16../24)
        whois -a -tinetnum -imin-alloc $minalloc

I would expect anyone can set a min-alloc atribute on the inetnum objects
they maintain, however small. One can of course check that the min-alloc
is not larger than the block itself but that is about it.
Theis means that with (2) you will have to filter out the objects 
that you wish to consider. This could be done by maintainer
or block size.

I think both of these, while not totally simple, are straightforward enough.

Daniel