You are here: Home > Publications > RIPE Labs > Denis Walker

Denis Walker

15 Aug, 2011 11:20 AM
Geolocation Prototype for RIPE Database by Denis Walker — last modified 17 Oct, 2016 08:58 AM

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.

Review of Database Consistency Service (DBConstat) by Denis Walker — last modified 17 Oct, 2016 08:55 AM

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.

Reclaim Functionality for Resource Holders by Denis Walker — last modified 17 Oct, 2016 09:00 AM

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.

"diff" Functionality in the RIPE Database by Denis Walker — last modified 17 Oct, 2016 08:56 AM

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 Global Resource Service by Denis Walker — last modified 17 Oct, 2016 08:59 AM

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.

Simplified Route Creation in the RIPE Database by Denis Walker — last modified 11 Jul, 2017 02:13 PM

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?

Dry-Run Testing in the RIPE Database by Denis Walker — last modified 17 Oct, 2016 08:55 AM

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.

RIPE Database Joins Single Sign-On Club by Denis Walker — last modified 17 Oct, 2016 08:56 AM

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.

Suggestions for Improving Abuse Contact Management by Denis Walker — last modified 17 Oct, 2016 08:58 AM

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.