<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font size="+1"><tt>Dear Colleagues<br>
<br>
</tt></font>The RIPE Database release 1.72 has now been fully
deployed to production.<br>
<br>
We would like to point out that, with this release, Webupdates and
Syncupdates can only be accessed with HTTPS and not with HTTP. This
is to conform to the requirements of using RIPE ACCESS now as an
authentication method for updating the RIPE Database. Any update
using HTTP will be automatically redirected to HTTPS.<br>
<br>
Regards<br>
Denis Walker<br>
Business Analyst<br>
RIPE NCC Database Team<br>
<div class="moz-forward-container"><br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Subject:
</th>
<td>RIPE Database Release 1.72 - including SSO Integration</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Date: </th>
<td>Thu, 06 Mar 2014 17:15:16 +0100</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">From: </th>
<td>Denis Walker <a class="moz-txt-link-rfc2396E" href="mailto:denis@ripe.net"><denis@ripe.net></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Organization:
</th>
<td>RIPE NCC</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">To: </th>
<td>Database WG <a class="moz-txt-link-rfc2396E" href="mailto:db-wg@ripe.net"><db-wg@ripe.net></a>, NCC Services WG
<a class="moz-txt-link-rfc2396E" href="mailto:ncc-services-wg@ripe.net"><ncc-services-wg@ripe.net></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>Dear colleagues,
We are pleased to announce RIPE Database release 1.72. For more
information about the features, changes and how this release might
affect your operations, please see these release notes:
<a class="moz-txt-link-freetext" href="https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.72">https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.72</a>
A major feature introduced in this release is the integration of RIPE
Database services with RIPE NCC Access. This gives maintainers the
option to use their RIPE NCC Access account for authorising updates to
the RIPE Database. The first applications that utilise this feature are
Webupdates and Syncupdates from a web form. Linking a RIPE NCC Access
account to an organisation is a requirement for certifying PI address
space. No change has been made to existing authorisation options.
This release also fixes a number of issues, so please read the release
notes. By fixing certain issues with the JSON output from the REST API,
the structure of that output has changed slightly. This should not
affect any users as it was broken in the first place. To ensure this is
the case, please test your implementation in the Release Candidate
environment.
More information about the Release Candidate environment is described in
this document:
<a class="moz-txt-link-freetext" href="https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-environment">https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-environment</a>
We look forward to hearing any questions or comments you might have.
Regards,
Denis Walker
Business Analyst
RIPE NCC Database Team
</pre>
<br>
</div>
<br>
</body>
</html>