Daniel Karrenberg

Registration History for Members - A Demo

Daniel Karrenberg
Contributors: Vesna Manojlovic
4

RIPE NCC members can browse RIPE database objects with history in RIPEstat for a couple of weeks as a demonstration. Please check it out and let us know what you think.


In recent mailing list discussions there have been several calls for historic information about address space registrations. Also it is becoming more and more important for members to evaluate the history of addresses they are asked to route or pass traffic for. We would like to demonstrate what we can make available if there is consensus among the membership that we should. Therefore the RIPEstat database object browser will offer history to all users who are logged in as members via RIPE NCC Access from now until the end of the RIPE meeting. The object browser is part of the standard set of widgets shown for each RIPEstat query. You can also access it directly . Normally the browser shows the validity period of the most recent version of the object only:

Figure 1: Object browser for non RIPE NCC members

If you are logged in as a RIPE NCC member this will be replaced by a context menu that allows you to select the specific version of the object you want to see:

Figure 2: Object browser for logged-in RIPE NCC members

In the image below you can see various time intervals you can choose from. Depending on how often the object has changed in the past, you will see more or less time intervals in the drop down menu.

Figure 3: Object browser showing time intervals of the object between changes

If you select a historic version of the object, all the related objects will change as expected and when you navigate to a related object, RIPEstat will use a version that matches the time period you selected as closely as possible:

Figure 4: Object browser with other related objects

Raw data and RIPEstat API access is also available. In combination with other routing history and other historic data, this gives a comprehensive picture of how a particular resource has been used over the years and by whom. Please note that the same restrictions on the number of objects apply (see below).

Restrictions

In order to prevent downloading the entire database via this interface and in order to safeguard against excessive resource usage, the number of queries for historic objects is limited to 1000/user/day. The browser widget makes two queries each time it is used. So you can use or reload this widget 500 times per day. See below the warning that will be displayed. History is only available to users that belong to a RIPE NCC member. Personal details are not shown for historic objects because of privacy concerns.

Figure 5: Limitation on the number of objects you can see

Let us know what you think!

Let us know how we can make this feature more useful for you. Should we offer this on a permanent basis? Any concerns about privacy? Any concerns about commercial confidentiality? Any ideas for other usage limitations? Should we also offer history in the address hierarchy browser and how should that be presented? Let us hear it! Please leave a comment under the article.

4

You may also like

View more

About the author

Daniel Karrenberg Based in Western Europe, NL&DE mostly

>>>>>>>>>>>> https://www.ripe.net/about-us/press-centre/publications/speakers/daniel-karrenberg <<<<<<<<<<<< Ample information about his past sins can be found using your favourite search engine. Following are a few additional keywords you might use, arranged by decade: 1980s: GUUG EUUG EUnet unido mcvax cwi RARE iepg RIPE; 1990s: RIPE+NCC rir iana postel terena ebone centr k.root-servers.net; 2000s: dnsmon nsd ris internet+society rssac; 2010s: ripe+labs ripestat ripe+atlas

Comments 4