[address-policy-wg] Maximum size for current IPv4 allocations
- Previous message (by thread): [address-policy-wg] Maximum size for current IPv4 allocations
- Next message (by thread): [address-policy-wg] Maximum size for current IPv4 allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Mon Aug 15 11:10:24 CEST 2022
In message <6449f927-d16e-9938-f2c2-bce8102c2c31 at tyrasuki.be>, Tyrasuki <me at tyrasuki.be> wrote: >As Bogdan mentioned, these seem to be a bunch of intra-RIR transfers. I'm sorry, but I'm not seeing that. What makes you think that this was other than a set of simple intra-company transfers (and NOT a set of inter-RIR transfers)? I just checked the biggest block (77.220.64.0/19) at the URL that people here gave me, and it appears that this came from a company called "Internet One SRL" which appears to be located in Romania. Last time I looked, Romania was still within the RIPE region, so I wonder how you concluded that this was an inter-RIR transfer. >I'm not sure if it has ever been explained why (if it has my apologies >for the obliviousness), but any transfer of v4 or v6 seems to >"re-create" the RIPE Database object, thus the very recent date. Worse, I can't get full history (from WHOIS) on the blocks. But I think this (WHOIS full history) problem/issue was discussed awhile back on the DB Working group mailing list, and I think the decision was reached to try to make available fully histories of blocks, even across inter-company transfers. But it seems like maybe that didn't quite get fully implemented yet. Regards, rfg
- Previous message (by thread): [address-policy-wg] Maximum size for current IPv4 allocations
- Next message (by thread): [address-policy-wg] Maximum size for current IPv4 allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]