<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <tt>Dear colleagues, </tt>RIPE Database software release 1.73.1 has now been deployed into production.<tt> The RIPE NCC has modified all AUT-NUM objects to add the mandatory "status:" attribute. We have also modified all legacy INETNUM objects and set the "status:" to 'LEGACY'. Regards Denis Walker Business Analyst RIPE NCC Database Team </tt> <div class="moz-cite-prefix">On 19/05/2014 16:32, Johan Åhlén wrote: </div> <blockquote cite="mid:7876BA61-B705-4F9F-91A0-09AEC707B775@ripe.net" type="cite"> <pre wrap="">Dear colleagues, Based on feedback from users testing RIPE Database release 1.73 in the Release Candidate (RC) environment, the RIPE NCC Database Group have made some software improvements that we’ve decided to incorporate into the next deployment. We will not deploy version 1.73 to production. Instead, we will deploy the improved version, 1.73.1, to the RC environment today, 19 May, and to production on 27 May 2014. The main concern with RIPE Database release 1.73 was related to user-automated assignment generation in the RIPE Database for legacy address space. With release 1.73, if a legacy object was updated with an incorrect "status:" attribute value, then the update would fail. With version 1.73.1, the database software will accept the update, regardless of any value supplied by the user, but will show a warning if the “status:” attribute value is incorrect. For more information about this release and how it might affect your operations, please see the release notes: <a class="moz-txt-link-freetext" href="https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.73.1">https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.73.1</a> We look forward to any questions or comments you might have. Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC </pre> </blockquote> </body> </html>