In message <[email protected]>, Garry Glendown <[email protected]> wrote:
>Could we please stop these "conspiracy theory" discussion? In essence, >the initial question inferred that RIPE is still handing out IPV4 >outside of current policies, which I'm pretty sure they don't. I'm sorry to learn that my modest attempts at wry humor have fallen so flat over on the Left Side of the Pond. Of course, NCC has not been giving out /15 blocks. (According to what I was reading just yesterday, NCC doesn't even have any such to give!) But if you look at the data base record that I posted, that is clearly the implication that would be derived from a straightforward reading of the plain text of the record in question: inetnum: 62.222.0.0 - 62.223.255.255 ... created: 2019-08-20T11:55:01Z Quite obviously, this is a data base problem. But before I hop onto the DB working group mailing list and start pointing out this self-evident problem/issue, I felt obliged to check here first, just in case, just to make absolutely and 1000% sure that this was not just some sort of fluke, or the result of some obscure special loophole in the current allocation policies (e.g. for "special hardship" or something like that) which would have authorized NCC to award a /15 just this past August. Now I am sure, because everyone has been so kind and generous to point out to me that no, this space was all already well and truly allocated, well before this past August. So I can now proceed with confidence and note this strange "created:" anomaly... which naturally might lead to entirely incorrect inferences... on the DB WG mailing list. Thank you all for your good humor and generosity and your help in clarifying for me the actual nature of the problem/issue here. Regards, rfg
