<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi Tore,</div><div><br></div><div>I wanted to research all the details and wait for some developments to unfold before replying to the list. </div><div><br></div><div>As Mirjam just posted, Daniel published a RIPE Labs article describing a way for members to look at registration history in RIPEstat:</div><div><a href="https://labs.ripe.net/Members/dfk/registration-history-for-members-a-demo">https://labs.ripe.net/Members/dfk/registration-history-for-members-a-demo</a></div><div><br></div><div>An important point Daniel makes in the article is "We would like to demonstrate what we can make available if there is consensus among the membership that we should." </div><div><br></div><div>The way the information in RIPEstat is presented, is that a member can only do a query on a single prefix at a time, with restrictions in place to prevent excessive resource usage. One of the implementation suggestions you do in your email, is to *publicly* present historic data in *aggregate form*, for example by publishing historic versions of alloclist.txt. </div><div><br></div><div>This goes quite a bit further than what we are demoing in RIPEstat at the moment. We will definitely need more discussion on this topic to make sure there is consensus on what exactly we should offer. </div><div><br></div><div>Cheers,</div><div><br></div><div>Alex</div><div><br></div><div><div>On 5 Sep 2012, at 09:44, Tore Anderson <<a href="mailto:tore.anderson@redpill-linpro.com">tore.anderson@redpill-linpro.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">* Alex Band<br><br><blockquote type="cite">Could you give us some context how you would want to use this data,<br>and what you currently are not capable of doing using for example the<br>RIPE Database?<br></blockquote><br>Hi,<br><br>Take a look at proposal 2012-05 in apwg. One of its goals is to ensure<br>that the origin and recipient of allocation transfers are public<br>information. I agree with this goal, and will likely find it very<br>interesting to follow transfers happening in the coming months.<br><br>Much of this information is already easily available on the FTP,<br>however. The name and reg-id of the holding LIR are available in<br>alloclist.txt, while the prefix and date of allocation is available in<br>both alloclist.txt and delegated-ripencc-extended-latest. The only thing<br>I cannot easily find, is the historic information of which LIR held an<br>allocation previously. (If I have simply missed it, please point me to<br>it and stop reading.)<br><br>It occurs to me that by adding a LIR/reg-id column in<br>delegated-ripencc-extended-latest, and/or to publish historic versions<br>of alloclist.txt, the information sought by 2012-05 (and as an added<br>bonus, information about the origin of returned resources) would be<br>easily obtainable from the FTP. To avoid any privacy issues, the<br>LIR/reg-id column in the delegated file could be left empty for assigned<br>resources - I believe that would mean that no previously unpublished<br>information would need to be made public. Is this doable, you think?<br><br>Best regards,<br>-- <br>Tore Anderson<br>Redpill Linpro AS - <a href="http://www.redpill-linpro.com">http://www.redpill-linpro.com</a><br><br><br></blockquote></div><br></body></html>