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.
Likes on articles
About the author
From 2001 to 2015 I was a developer and then the business analyst for the RIPE Database with the RIPE NCC. During this time I have been involved in every aspect of it's design and development of the software, web services and infrastructure, it's philosophy, legal, political and policy aspects, documentation, testing and future planning and specifying of new features
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 th…
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…
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 passw…
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.
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 Data…
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.
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.