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.
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
Pages created by Denis Walker
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.
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.
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.
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?