Dear Working Group, We found two minor issues while 1.89 was in the Release Candidate Environment. #1 Abuse contact information was sometimes returned incorrectly for ASNs #2 The “Zonemaster” configuration was incorrect We had a fix ready for the first issue and therefore we deployed release 1.89.1 to production on 22 May as planned. The fix for the second issue was deployed on 23 May. Note that “Zonemaster” is not enabled yet in production. Although this was tested in the Release Candidate environment, and we don’t expect issues, we plan to enable “Zonemaster” in production manually, knowing that we have the option to revert without the need for a new release in case unforeseen issues are still found. We will send an announcement about this change to this working group before we do. Kind regards Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group

On 4 May 2017, at 14:55, Tim Bruijnzeels via db-wg <db-wg@ripe.net> wrote:

From: Tim Bruijnzeels <tim@ripe.net> Subject: Whois release 1.89 deployed to the Release Candidate Environment Date: 4 May 2017 at 14:55:51 GMT+2 To: db-wg@ripe.net

Dear working group,

We just deployed release 1.89 to the Release Candidate (RC) environment. If no issues are raised we plan to deploy this version to production on 22 May 2017.

This release contains a number of small improvements:

- Include information on who changed an object in update responses if SSO or PGPKEY is used for authentication - Replaced dnscheck with Zonemaster for improved domain object (and nameserver) validation - Fixed NRTM client bugs #279 and #294

The complete list of other minor issues solved by this release can be found here: https://github.com/RIPE-NCC/whois/blob/master/changes.txt

Kind regards

Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group