<html><head></head><body><div class="ydp79cdabf4yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div dir="ltr" data-setdir="false">Hi Ronald</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">The RIPE NCC mirrors the other 4 RIR databases and the mirrored data is updated daily. If you add '--resource' to your query of the RIPE Database you will get the correct response from the RIR database (mirror) that holds the resource.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">for example:</div><div dir="ltr" data-setdir="false">whois -h whois.ripe.net -r --resource 51.79.0.0/16</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><div><ul class="ydp8d938bf1showripemanaged" style="margin: 0px; padding: 0px; list-style: none; color: rgb(51, 51, 51); font-family: Menlo, Monaco, Consolas, Courier New, monospace; white-space: pre-wrap;"><li>inetnum: <a href="https://apps.db.ripe.net/db-web-ui/lookup?source=arin-grs&key=51.79.0.0%20-%2051.79.255.255&type=inetnum" style="background-image: initial; background-size: initial; background-repeat: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: initial; color: rgb(42, 100, 150);" rel="nofollow" target="_blank">51.79.0.0 - 51.79.255.255</a></li><li>org: <a href="https://apps.db.ripe.net/db-web-ui/lookup?source=arin-grs&key=HO-2&type=organisation" style="background-image: initial; background-size: initial; background-repeat: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: initial; color: rgb(42, 100, 150);" rel="nofollow" target="_blank" class="">HO-2</a></li><div>netname: HO-2<br></div><li>status: <span>ALLOCATION</span></li><li>source: <span>ARIN-GRS</span></li><li>remarks: <span>****************************</span></li><li>remarks: <span>* THIS OBJECT IS MODIFIED</span></li><li>remarks: <span>* Please note that all data that is generally regarded as personal</span></li><li>remarks: <span>* data has been removed from this object.</span></li><li>remarks: <span>* To view the original object, please query the ARIN Database at:</span></li><li>remarks: <span>* http://www.arin.net/</span></li><li>remarks: <span>****************************</span></li></ul></div><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 dir="ltr" data-setdir="false"><br></div><div><br></div>
</div><div id="ydpca118228yahoo_quoted_2140005267" class="ydpca118228yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Wednesday, 30 September 2020, 10:27:37 CEST, Ronald F. Guilmette via db-wg <db-wg@ripe.net> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">I have been writing a modest little software tool recently that seeks to<br></div><div dir="ltr">ferret out the identity of the "top level" registrant organization for<br></div><div dir="ltr">any given assigned IPv4 address. In this context by "top level" I mean<br></div><div dir="ltr">the entity that obtained the relevant IP address assignment directly,<br></div><div dir="ltr">either from one of the five regional Internet registries or else from<br></div><div dir="ltr">some subserviant national Internet registry.<br></div><div dir="ltr"><br></div><div dir="ltr">This softare tool always starts by querying whois.iana.org in order to<br></div><div dir="ltr">obtain a first-order referral to one of the WHOIS servers belonging to<br></div><div dir="ltr">of the five regional Internet registries... usually and often the correct<br></div><div dir="ltr">one that actually holds the desired information.<br></div><div dir="ltr"><br></div><div dir="ltr">Due to various inter-region transfers that have taken place over time<br></div><div dir="ltr">however, the first-order referral given by whois.iana.org is often simply<br></div><div dir="ltr">wrong, and it is really some other WHOIS server of some other one of<br></div><div dir="ltr">the five regional Internet registries that actually contains the<br></div><div dir="ltr">information sought.<br></div><div dir="ltr"><br></div><div dir="ltr">Conveniently, in the case of the ARIN WHOIS server and the APNIC WHOIS<br></div><div dir="ltr">server, even in those cases where these respective WHOIS servers do not<br></div><div dir="ltr">contain the data sought, e.g. due to some inter-region transfer, these<br></div><div dir="ltr">WHOIS servers are at least helpful enough to provide in their responses<br></div><div dir="ltr">explict referrals to the proper regional Internet registry WHOIS server<br></div><div dir="ltr">where the desired data can in fact be obtained.<br></div><div dir="ltr"><br></div><div dir="ltr">I would like to request that NCC staff administering the RIPE WHOIS data<br></div><div dir="ltr">base likewise incoroprate some such helpful explicit referral text into<br></div><div dir="ltr">the WHOIS responses for all number resources where whois.iana.org believes<br></div><div dir="ltr">that the resources are under the administration of RIPE, but where in fact<br></div><div dir="ltr">the number resources in question have been transferred to some different<br></div><div dir="ltr">region.<br></div><div dir="ltr"><br></div><div dir="ltr">During the early testing of my small software tool I have already encountered<br></div><div dir="ltr">a number of such cases. In each of these cases I had to sort out the problem<br></div><div dir="ltr">by hand -- I had to ferret out the correct RIR WHOIS server by other means,<br></div><div dir="ltr">the responses from whois.ripe.net being of no help whatsoever in this regard,<br></div><div dir="ltr">and I then had to program in some "manual overide" work-arounds in my code<br></div><div dir="ltr">in order to deal with these cases:<br></div><div dir="ltr"><br></div><div dir="ltr">51.79.0.0/16<br></div><div dir="ltr">51.81.0.0/16<br></div><div dir="ltr">51.161.0.0/16<br></div><div dir="ltr">51.162.0.0/17<br></div><div dir="ltr">51.222.0.0/16<br></div><div dir="ltr">151.101.0.0/16<br></div><div dir="ltr">151.139.0.0/16<br></div><div dir="ltr">151.164.0.0/16<br></div><div dir="ltr">151.190.0.0/16<br></div><div dir="ltr">185.105.7.0/24<br></div><div dir="ltr">185.150.189.0/24<br></div><div dir="ltr">185.150.190.0/23<br></div><div dir="ltr">185.171.208.0/22<br></div><div dir="ltr">194.204.192.0/18<br></div><div dir="ltr"><br></div><div dir="ltr">I have some faith and hope that the community, the members, and the staff<br></div><div dir="ltr">of the RIPE region will wish to be at least as helpful with repect to<br></div><div dir="ltr">this WHOIS referral issue as their North American and Asia/Pacific<br></div><div dir="ltr">counterparts.<br></div><div dir="ltr"><br></div><div dir="ltr">Given the expected increases in inter-regional transfers it seems that the<br></div><div dir="ltr">time is... well... ripe, to address this small but consequential issue<br></div><div dir="ltr">within the data base.<br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">Regards,<br></div><div dir="ltr">rfg<br></div><div dir="ltr"><br></div></div>
</div>
</div></body></html>