Dear working group, This has now been deployed to production. Somewhat related to this work. As documented here: https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-datab... The "created:" date on objects reflects when the object was created in the database, but we do not have accurate data on this from before 21 December 2001. However we can back date objects on demand. And after discussing with the chairs we agreed that we will make an effort to use the date found in the "netname:" attribute for inetnums, or the date in the oldest "changed:" attribute (with a sanity check that it's not before April 1992), in those cases where did not find a date. Kind regards, Tim Bruijnzeels

On 22 Dec 2015, at 12:35, Tim Bruijnzeels <tim@ripe.net> wrote:

Dear working group,

We have just deployed release 1.85 to the Release Candidate environment.

This release completes the deprecation of the "changed:" attribute: https://labs.ripe.net/Members/tim/deprecating-the-changed-attribute-in-the-r...

With this release we will:

= Filter out "changed:" from all RIPE Database objects = Actively remove "changed:" from all RIPE Database objects = Reject updates that contain "changed:"

We encourage all users of the database to test their tools. If no issues are found we plan to deploy this release to production on Monday 1 February 2016.

Note that this release includes all changes from the previous release, 1.84.1. But, we only plan to upgrade the RIPE Database hardware, and deploy the 1.84.1 release, in the first half of January. Because this upgrade will involve a brief outage for updates to the Database, we will communicate a more detailed plan with time lines closer to the date.

Kind regards,

Tim Bruijnzeels

Assistant Manager Software Engineering RIPE NCC Database Group