Denis Walker

The RIPE NCC is pleased to announce a new Geolocation prototype service for storing geolocation data in the RIPE Database. This article outlines the methodology applied in this prototype.

This article provides you with a number of step by step examples on how to use the recently released prototype geolocation service in the RIPE Database.

In this article we suggest a technical solution to the issue of publicly displaying MD5 password hashes in the RIPE Database.

In this article we provide some analysis on the updates received by the RIPE Database during 2011 and in the first two months of 2012.

The RIPE NCC is proposing to deprecate DBConstat, a service to check consistency of data in the RIPE Database and produce statistics. It was written over ten years ago and has changed little over that period.

This is an automated process to replace the manual intervention frequently asked of the RIPE NCC to overcome the short comings of the authentication system with regard to proper management of resources by the registered resource holders.

Users often like to see the difference between two versions of an object. Some objects can be long and complex. It is not easy to look at two text versions and see what changed. We are proposing to implement a 'diff' function for the RIPE Database.

The RIPE NCC has changed the way data is imported for this service. This allows us to present a more complete Global Resource Service (GRS) for all Internet resources. This article outlines the GRS service including the recent changes. None of these changes have any impact on the standard RIPE Database query service.

Creating route objects just got a whole lot easier! Forget about hassle across organisations. Now you can submit the object with the passwords you have, and if it needs more, we will sort it out. The software will decide who else needs to authorise it and contact them. When they send in their passwords, we will match them up and create the object. Then we let everyone know the result – whether it’s a success or failure. Can it get any easier than this?

The RIPE Database operates as an open, public database for routing information. This information is not restricted to the RIPE NCC service region or to resources administered by the RIPE NCC.

Have you ever wanted to test an update to the RIPE Database, without actually changing anything in the database? Well now you can "dry-run" it - see what will happen without changing anything.

Availability of 16-bit AS Numbers is getting low. We have many in reserve that have been returned but they need 'cleaning'. You can help with this.

With RIPE NCC Access, our single sign-on service - you log in once and can access many RIPE NCC services. Now, with the new RIPE Database release, you can update your data in the RIPE Database using this single sign-on service. This is part of the RIPE NCC's work to make the RIPE Database easier to use.

The aim of the policy Abuse Contact Management in the RIPE Database (RIPE document ripe-563), was to make available an abuse contact for all resources maintained by the RIPE NCC. The RIPE NCC proposed an implementation plan that was accepted. During the deployment there has been some feedback on the practicalities of the implementation. At RIPE 67 the RIPE NCC agreed to think about this feedback and present some further options.

There are changes being made to the way out-of-region objects are managed and represented in the RIPE Database. The following information is important to all database users.