You are here: Home > Manage IPs and ASNs > RIPE Database > Release Notes > RIPE Database Release 1.79

RIPE Database Release 1.79

These are the release notes for RIPE Database version 1.79, 1.79.1 and 1.79.2.

Date of Deployment

Release Candidate (RC) environment:

  • Deployment and updating objects: 30 March 2015
  • Enabling "last-modified:" and "created:" in output: 2 April 2015
  • 1.79 was never deployed to production
  • 1.79.1 was deployed to RC on 22 April 2015.

Production environment:

  • 1.79.1 was deployed on 28 April 2015
  • Deployment and updating objects: 28 April 2015
  • Enabling "last-modified:" and "created:" in output: 4 May 2015 
  • 1.79.2 was deployed on 7 May 2015.
Release 1.79 was not deployed to production but release 1.79.1 and 1.79.2 were deployed to production.

Documentation has been prepared for this release.

Release 1.79 introduces two new attributes "created:" and "last-modified:", and changes attribute "referral-by" from mandatory to optional. The Web interface of the RIPE Database Software has a new look & feel.

New or Improved Features

  • Release 1.79 of the RIPE Database software introduces the new attributes "created:" and "last-modified:". These two attributes will be the replacement of the "changed:" attribute which will be deprecated in one of the following releases. You can find more information in the related RIPE Labs article. After deployment, we will run an update script to add these attributes to all objects in the database. This can take up to 48 hours. In order to ensure that the Database output is consistent for all objects, we have also added a "switch mode" mechanism to enable the new attributes in output.
  • Release 1.79 also changes attribute "referral-by" from mandatory to optional. This attribute is part of a mntner object for historical reasons and will be deprecated.
  • The RIPE NCC is currently working on a project to redesign the www.ripe.net website, and in the process provide a fresh, clean and consistent look and feel to all of our online services. These changes will be deployed across our services in the week of 13 April, and include updates to the web interface of the RIPE Database. However, please note that this deployment will not include any of the core whois 1.79 changes that are only planned to be deployed to production on 28 April.

Fixed Issues

The following issue has been fixed:

  • Issue #275: Some key-cert objects with multiple owners cannot be deleted

You can find more details about the issues in this release on GitHub.    

Release 1.79.1

We have found two issues with the 1.79 Release Candidate:

  • Deletion of objects would not work until the new attributes are enabled
  • The publication of sponsoring org for legacy resources by the RIPE NCC (policy 2014-06) was not allowed by business rules

Release 1.79.2

Fixed an issue where submitting an unmodified object would result in an update of the “last-modified:” attribute, where this should be treated as a Noop.