<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font size="+1"><tt>Dear Piotr<br>
<br>
The new versions of both the Update and Query Reference Manuals
in PDF format were available on the <a class="moz-txt-link-abbreviated" href="http://www.ripe.net">www.ripe.net</a> website
yesterday. The html version of the new Query Reference Manual is
now also available. They both include details of the new SSO
auth option.<br>
<br>
Regards<br>
Denis Walker<br>
Business Analyst<br>
RIPE NCC Database Team<br>
<br>
<br>
</tt></font>
<div class="moz-cite-prefix">On 25/03/2014 08:26, Piotr Strzyzewski
wrote:<br>
</div>
<blockquote cite="mid:20140325072629.GA19555@hydra.ck.polsl.pl"
type="cite">
<pre wrap="">On Mon, Mar 24, 2014 at 02:27:39PM +0100, Denis Walker wrote:
Dear Denis
</pre>
<blockquote type="cite">
<pre wrap="">The RIPE Database release 1.72 has now been fully deployed to production.
</pre>
</blockquote>
<pre wrap="">
Could you please specify, when the new version of RIPE Database Update
Reference Manual will be available online?
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">
And this is good example of what I was trying to avoid when we were
discussing being over cautious with changing something just a week ago.
Piotr
</pre>
</blockquote>
<br>
</body>
</html>