[db-wg] 57.224.0.0/11

 Colleagues
Just to be clear the "created:" attribute relates to an 'object' not to a 'resource'. So in this case the creation date has not been changed. This is a new object and the "created:" attribute reflects the date this object was created. The main issue with historical data in the RIPE Database is that no history is available for deleted objects.
NWI-10, which is in the process of being implemented, will add a "country:" attribute to all ORGANISATION objects referenced by resource objects and will be maintained by the RIPE NCC.
cheersdenis
co-chair DB-WG
    On Tuesday, 22 September 2020, 13:57:01 CEST, Ronald F. Guilmette via db-wg <db-wg at ripe.net> wrote:  
 
 In message <CAK5YLgeGEP3obAZNArvVVvzHE3upR2dbyfZQ1gMwX-HLyydHyg at mail.gmail.com>, 
Aftab Siddiqui <aftab.siddiqui at gmail.com> wrote:

>Just for my understanding, do you need a policy for the NCC to offer
>"whowas[1]" service?

I guess that my answer would be "no".

As a general matter, and barring any complications, such as are present in
the case of 57.224.0.0/11, historical RIPE WHOIS records are and have
been available, and I have even written my own little tool to fish them
all out with respect to any given IPv4 CIDR... at least those that have
not undergone a death & rebirth.

In short, I am generally a satisfied customer already with respect to RIPE
WHOIS historical records, and I am very glad that these are easily available.

It is only in these rather rare and unusual circumstances, such as what
pertains to the history of the 57.224.0.0/11 block, when the data I see is
not quite what I was expecting.

But I don't think it would be a worthwhile expenditure of NCC staff time to
work on something just to insure that rfg is not occasionally flummoxed.  If
they have an excess of free time then I can quite certainly dream up a number
of much more valuable pursuits for them, in particular, insuring that every
number resource record in the data base has a corresponding org: and that
every organisation: record has a country:

The latter issue still causes me much difficulty on a regular basis.


Regards,
rfg
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/db-wg/attachments/20200922/0ebf57f0/attachment.html>