<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hello Peter,<div><br></div><div>Please find my reply inline:</div><div><br><div><div><div>On 03 Jun 2014, at 08:46, Peter Koch <<a href="mailto:pk@DENIC.DE">pk@DENIC.DE</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><blockquote type="cite">Old and new DNSMON will be available in parallel until end of June 2014.<br>Configuration updates for existing zones will only be applied to the new DNSMON.<br>Data collection in the old DNSMON service will be terminated by 1 July 2014.<br></blockquote><br>Given the increasingly painful dependency on the old TTM system, and taking<br>into account the warning time given to us customers, this transition deadline appears<br>reasonable to me: "no objection�.<br></blockquote><div><br></div>Thank you.</div><div><br><blockquote type="cite"><br><blockquote type="cite">Data visualisation of (historic) measurement data provided by the old DNSMON will be available until the end of 2014.<br>Raw data from the old DNSMON measurements will be kept available for a longer period. We are investigating ways to keep the old data available indefinitely.<br></blockquote><br>As I said at the microphone in Warsaw, I think it would be a plus not only to<br>maintain the old data, but also some way to visualize it, so some trends over<br>the years can be looked up (literally, not only dug in the raw data) in comparison.<br>That does not imply running an unmaintained or unmaintainable system indefinitely,<br>neither does it postpone the shutdown date for said system. Getting the viz back<br>in some "reasonable" time would be great.<br></blockquote><div><br></div><div>I fully agree. As suggested in Warsaw, we will keep running the old visualisations until RIPE 69 in London and will present the WG with real usage numbers and a few suggestions on how to move forward for a discussion and decision by the community. </div><br><blockquote type="cite"><br>The other point I want to submit "in writing" is that I am not convinced by the<br>reasoning that led to giving up the two hour delay. The fact that "measurements<br>are public" or "anybody could set up their own measurements" neglects the very<br>value added by the (new) visualisation: not only is there an instant feedback<br>channel, but that channel is _the_ well reputed source. In 1980s' words:<br>the revolutionary army not only has a transmitter, but it has direct write<br>access to the 20:00 main news.<br>Doesn't give me sleepless nights, but I question the unilateral decision<br>based on that fatalistic reasoning.</blockquote><br></div><div>Yes and we are fully committed to implement what is proposed by the WG. Regardless of old TTM decommissioning timeline, we can always introduce a delay in the new DNSMON results. As a matter of fact, Robert has prepared an email explaining possible scenarios to kick off that discussion, we are just waiting to hear from the WG on the status of the timeline in order to be able to commit to implement any possible change to the new DNSMON.</div><div><br></div><div>All the best,</div><div>Kaveh.</div></div></div><div><br></div><div><br></div><div>�</div><div>Kaveh Ranjbar,</div><div>Chief Information Officer, RIPE NCC</div></body></html>