<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 17/01/2012 16:21, Nick Hilliard wrote: <blockquote cite="mid:4F15A010.90501@inex.ie" type="cite"> <pre wrap="">Hi Alex, </pre> <pre wrap=""> Problem is, we don't yet have a replacement command-line tool for dealing with quick-n-easy LIR resource usage summarisation. This has meant that the people who depended on this tool were left hanging for the last 8 years, because the code slowly rotted as interfaces subtly changed over time. This is not a criticism of changing the DB interface or anything, btw - progress needs to happen. In terms of being platform specific, it was limited to any platform which could run perl - perhaps with minor modifications. There are lots of complaints that people make about perl, (some legitimate) but platform portability is not one of them. OTOH, webasused can be very slow. E.g. I submitted a request for a LIR at 15:28 GMT today, and got a reply at 15:39. This makes it unusable for a typical workflow process (e.g. run asused, check output against internal records, submit a couple of updates, run asused again, check again, repeat until satisfied). The web version is also unauthenticated which means that it's open to third parties submitting requests for arbitrary LIRs. And it doesn't support ipv6, which means that it's still difficult to do resource reconciliation for v6 assignments. I'll admit that not everyone likes command line tools, but for those of us who continue to us asused, it's a real pity that it wasn't maintained and further developed to support ipv6. </pre> </blockquote> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">  Nick, Alex et al<o:p></o:p> <o:p> </o:p> At the Board meeting on the 8th December the board gave Axel an action "to reinstate/redevelop the stand-alone version of the RIPE NCC ASused tool"<o:p></o:p> <o:p> </o:p> I doubt that this action would be satisfied merely by the provision of an API into the webasused tool.<o:p></o:p> <o:p> </o:p> Alex, you may like to check this with Axel. It is possible that it was misunderstood by him, but it is very clearly minuted.<o:p></o:p> <o:p> </o:p> And I'd agree with Nick that lack of platform portability is one of the few brickbats that cannot be aimed at perl.<o:p></o:p> <o:p> </o:p> Nigel<o:p></o:p> <meta name="ProgId" content="Word.Document"> <meta name="Generator" content="Microsoft Word 14"> <meta name="Originator" content="Microsoft Word 14"> <link rel="File-List" href="file:///C:%5CDOCUME%7E1%5CNIGEL%7E1.TIT%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"> <link rel="themeData" href="file:///C:%5CDOCUME%7E1%5CNIGEL%7E1.TIT%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"> <link rel="colorSchemeMapping" href="file:///C:%5CDOCUME%7E1%5CNIGEL%7E1.TIT%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"> <style>  </style> </body> </html>