Dear colleagues,
Earlier today we deployed a minor release of the RIPE Database software. The release contained a correction of an invalid data structure returned in the JSON format. The issue is described in detail here:
https://github.com/RIPE-NCC/whois/issues/114
The beta REST API was decommissioned with the deployment of 1.71. As the issue above was affecting users that had not yet migrated to the new API we decided to go ahead with the minor release. However, we were just informed that there are users that rely on this specific structure for their operations so we have reverted the minor release.
The current RIPE Database version in production is now back to 1.71
We’ve also made sure that the old beta API is available for any users that can’t migrate because of the issue mentioned above. Please contact me directly and I will provide you with the details on how you can connect to the old beta API.
We are sorry for any inconvenience this might have caused you and if you have any questions or concerns then please let me know.
Kind regards,
Johan Åhlén
Assistant Manager Database
RIPE NCC
Dear colleagues,
We are pleased to announce RIPE Database release 1.71. You can find details about the new features, changes and how you might be affected, and important dates in the release notes:
https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.71
The new release contains the "import-via" and "export-via" attributes that were discussed in the Database and Routing Working Groups at RIPE 67, the initial implementation of which was made by Job Snijders. After further discussions on the mailing lists, the working group chairs decided that this feature should be incorporated in the RIPE Database. You can find out more about these attributes here:
http://www.ietf.org/id/draft-snijders-rpsl-via-02.txt
With this release we would also like to introduce our new Release Candidate environment. The Release Candidate environment is distinct from the TEST Database, and aims to provide an environment as close as possible to "production" where you can test that your software will work with upcoming RIPE Database releases. You can find out more about the Release Candidate environment in the release notes linked above.
We look forward to hearing any questions or comments you might have!
Kind regards,
Johan Åhlén
Assistant Manager Database
RIPE NCC