<html><head></head><body><div class="ydpecedb056yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div dir="ltr" data-setdir="false">Colleagues</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">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.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">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.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">cheers</div><div dir="ltr" data-setdir="false">denis</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">co-chair DB-WG</div><div><br></div>
</div><div id="ydp2383c1ceyahoo_quoted_0939797018" class="ydp2383c1ceyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Tuesday, 22 September 2020, 13:57:01 CEST, Ronald F. Guilmette via db-wg <db-wg@ripe.net> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">In message <<a shape="rect" href="mailto:CAK5YLgeGEP3obAZNArvVVvzHE3upR2dbyfZQ1gMwX-HLyydHyg@mail.gmail.com" rel="nofollow" target="_blank">CAK5YLgeGEP3obAZNArvVVvzHE3upR2dbyfZQ1gMwX-HLyydHyg@mail.gmail.com</a>>, <br clear="none">Aftab Siddiqui <<a shape="rect" href="mailto:aftab.siddiqui@gmail.com" rel="nofollow" target="_blank">aftab.siddiqui@gmail.com</a>> wrote:<br clear="none"><br clear="none">>Just for my understanding, do you need a policy for the NCC to offer<br clear="none">>"whowas[1]" service?<br clear="none"><br clear="none">I guess that my answer would be "no".<br clear="none"><br clear="none">As a general matter, and barring any complications, such as are present in<br clear="none">the case of 57.224.0.0/11, historical RIPE WHOIS records are and have<br clear="none">been available, and I have even written my own little tool to fish them<br clear="none">all out with respect to any given IPv4 CIDR... at least those that have<br clear="none">not undergone a death & rebirth.<br clear="none"><br clear="none">In short, I am generally a satisfied customer already with respect to RIPE<br clear="none">WHOIS historical records, and I am very glad that these are easily available.<br clear="none"><br clear="none">It is only in these rather rare and unusual circumstances, such as what<br clear="none">pertains to the history of the 57.224.0.0/11 block, when the data I see is<br clear="none">not quite what I was expecting.<br clear="none"><br clear="none">But I don't think it would be a worthwhile expenditure of NCC staff time to<br clear="none">work on something just to insure that rfg is not occasionally flummoxed. If<br clear="none">they have an excess of free time then I can quite certainly dream up a number<br clear="none">of much more valuable pursuits for them, in particular, insuring that every<br clear="none">number resource record in the data base has a corresponding org: and that<br clear="none">every organisation: record has a country:<br clear="none"><br clear="none">The latter issue still causes me much difficulty on a regular basis.<div class="ydp2383c1ceyqt2845995050" id="ydp2383c1ceyqtfd00318"><br clear="none"><br clear="none"><br clear="none">Regards,</div><br clear="none">rfg<div class="ydp2383c1ceyqt2845995050" id="ydp2383c1ceyqtfd05913"><br clear="none"></div></div></div>
</div>
</div></body></html>