This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] Looking for good way to find blocks allocated directly by ripe
- Previous message (by thread): [db-wg] Re: AW: [local-ir at ripe.net]Proposed change of "mnt-lower:" behaviour: procedure and timelines
- Next message (by thread): [db-wg] Looking for good way to find blocks allocated directly by ripe
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
william at elan.net
william at elan.net
Fri Sep 19 15:44:33 CEST 2003
Hi, I'd like to find what is the best way to determine if particular inetnum was allocated directly by RIPE, this would include all blocks allocated to LIRs, all blocks allocated to large organizations and blocks allocated as small PI blocks. Currently I have come with the following way to do it - first find all inetnum objects listed as "ALLOCATED PI" with network name starting as "EU-ZZ", this find all PI space; then discard all "ASSIGNED PA" blocks except those within range of previously found "ALLOCATED PI" blocks and also discard "ALLOCATED PI" and "LIR-PARTITIONED PA" blocks. >From reminder the netblocks totally within another inetnum are discarded as well as "superblocks" listed under RIPE name. I'd like to find if you think doing it this way would leave any blocks out or include too many larger block then direct RIPE allocations. Doing it the way I described above, already produced some data available at http://www.completewhois.com/bogons/data/allocated-cidr-ripe_main.txt and non-allocated space is at http://www.completewhois.com/bogons/data/bogons-cidr-ripe_main.txt I'd like to verify validity of this data and the process I used, especially considering that I see number of errors, for example there are several blocks > /24 listed as allocated (but I did not think RIPE did any direct allocations or assignemsns of size > /24), for example: 193.58.0.64/26 193.164.232.192/26 193.201.147.0/26 193.201.148.64/26 193.243.183.0/26 193.254.0.64/26 194.1.127.128/26 194.9.166.0/26 194.149.71.128/26 194.153.156.0/26 194.180.159.128/26 194.180.226.192/26 194.246.39.0/26 194.246.39.128/26 195.35.104.64/26 -- William Leibzon Elan Networks william at elan.net
- Previous message (by thread): [db-wg] Re: AW: [local-ir at ripe.net]Proposed change of "mnt-lower:" behaviour: procedure and timelines
- Next message (by thread): [db-wg] Looking for good way to find blocks allocated directly by ripe
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]