The RIPE NCC is working on a toolbox, called RIPEstat, that will make it easier to access the various datasets maintained by the RIPE NCC. This toolbox will be developed in close cooperation with the community. There will be public demo sessions as described in this article.
The RIPE NCC has a lot of data about Internet numbers: IPv4 addresses, IPv6 addresses, autonomous system numbers, number resource registry information in the RIPE database, routing registry information in the RIPE database, measured routing data in the Routing Information Service (RIS) database, TTM results within the Test Traffic Measurement network as well as numerous data sets that we collect from external sources. We are preparing a summary article on all our data sets which will appear on RIPE Labs shortly.
Finding and Combining the Right Tools can be Difficult
The RIPE NCC also offers a variety of tools to access all that
data and make sense of it. Each tool by itself serves a useful
purpose. However, many of you tell us that it is difficult to find the
right tool to answer a specific question and that it becomes really
cumbersome when one wants to combine the results of several tools or to
feed the results of one tool into another. Wouldn't it be nice to have
a well organised toolbox to access all this data?
We have started to build the RIPEstat toolbox that will remove these difficulties and make our tools and data more useful and accessible to you. Based on experience with our current tools and REX, the Resource Explainer prototype, we have developed a first simple and rough version of this toolbox. Instead of building a whole system and then present it to you only when finished, we will build RIPEstat bit-by-bit in an incremental way. Every 4 weeks we will demonstrate new functionality for you to explore and comment on. Based on those comments and our observations of how you use RIPEstat we will design new functionality and adjust development priorities.
Public Demo Sessions
We are offering a public demo session every 4 weeks using webex videoconferencing. The first session will take place this coming Tuesday, 25 January 2011 from 1130-1200 Amsterdam time (1030-1100 UTC) . The URL for the meeting is:
It is possible to dial in by telephone, but that will be a second
class experience, because you will not be able to follow the live
screens of the demonstrations.
If you have not used webex before, we recommend you try out if you have all the software required by going to https://ripencc.webex.com/ripencc/systemdiagnosis.php and check it out. There are also clients for handheld devices. We hope to see you on Tuesday. For those who miss the live events, we will post a summary on RIPE Labs shortly after the event. We hope to see a lot of feedback on RIPE Labs and discussion on the MAT WG mailing list.
The schedule for the subsequent public demo sessions is as follows:
Tuesday, 22 February 2011
Tuesday, 22 March 2011
Tuesday, 19 April 2011
Tuesday, 17 May 2011
Tuesday, 14 June 2011
Tuesday, 12 July 2011
Tuesday, 9 August 2011
Tuesday, 6 September 2011
Tuesday, 4 October 2011
Tuesday, 1 November 2011 (NB: During RIPE63)
Tuesday, 29 November 2011
Tuesday, 27 December2011 (tentative...)
Comments are disabled on articles published more than a year ago. If you'd like to inform us of any issues, please reach out to us via the contact form here.
It is nice to hear that Test Traffic Measurement traces would be available in a more suitable form and the right tools will be there in the form of toolbox. We are from IIT Kharagpur working on Traffic Measurements and Modeling and we would be glad to contribute to it. RIPE has way to go. <br />Best wishes.<br />Sumit
This is excellent! <br />QUOTE Instead of building a whole system and then present it to you only when finished, we will build RIPEstat bit-by-bit in an incremental way.UNQUOTE<br /><br />I am a statistician and long-time user of applications software and data retrieval tools. I've worked with developers in designing quantitative toolkits too. But I've never seen this approach, stated explicitly from the very beginning of the project. What a wonderful idea! <br /><br />Just make sure that you don't let the users slow down your project schedule. Be aware that we'll want everything, and everyone will want something slightly different, just for their particular needs! But you will get input that should enable you to save time. You'll avoid development of features that are not in fact helpful or of only minor importance to most users. Sometimes the only way to determine that is from user acceptance testing. Because even the users don't necessarily realize what they need or want until after they try it out, go on a test drive! <br /><br />I would like to contribute to this project very much, and echo the sentiments of Sumit of IIT Kharagpur's comment above!<br />Best of luck to RIPE!
Roger Mbiama Assogo •
Security RIPE NCC Access account connect for the process REMOTE_SERVER at any time. root-servers routing update informations. Services that you are subscribed to: Data repository IS Alarms RIPE Labs