LONGEST ALLOC PREFIX, under rir control, would address the discussions of automatic generation of prefix length filters. I had thoght about that. In the RIPE database context this is more properly addressed by an atttribute of the corresponding inetnum object, e.g something like: inetnum: 217.0.0.0 - 217.255.255.255 netname: EU-ZZ-217 descr: RIPE NCC descr: European Regional Registry country: EU admin-c: NN32-RIPE tech-c: CREW-RIPE tech-c: OPS4-RIPE status: ALLOCATED UNSPECIFIED mnt-by: RIPE-NCC-HM-MNT mnt-lower: RIPE-NCC-HM-MNT min-alloc: /20 <============ changed: hostmaster@ripe.net 20000602 changed: hostmaster@ripe.net 20000615 source: RIPE
it is not clear from your example how you expect me to compose the search which produces the table i derive manually today. do i use mnt-lower recurse down a tree from a known root? if so, it needs a left and right pointer, not just a single one. do i form a query for all ??-ZZ-*? randy, confused again in seattle