<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Hi Chris,</div><p class="airmail_on">On 8 December 2015 at 16:35:29, Chris Amin (<a href="mailto:camin@ripe.net">camin@ripe.net</a>) wrote:</p> <div><blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span><div><div></div><div>On 08/12/2015 16:16, Nico CARTRON wrote:<span class="Apple-converted-space"> </span><br>> On 8 December 2015 at 16:07:02, Stephane Bortzmeyer (bortzmeyer@nic.fr<span class="Apple-converted-space"> </span><br>> <mailto:bortzmeyer@nic.fr>) wrote:<span class="Apple-converted-space"> </span><br>>> http://root-servers.org/news/events-of-20151130.txt<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> Thanks Stéphane for your reactivity, as usual :)<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> “Such test traffic may not be indicative of what happens to normal<span class="Apple-converted-space"> </span><br>> traffic or user experience”.<span class="Apple-converted-space"> </span><br>><span class="Apple-converted-space"> </span><br>> Not entirely sure what this means behind, or is it just them trying to<span class="Apple-converted-space"> </span><br>> minimise the impact?<span class="Apple-converted-space"> </span><br><br>It could be a bit of expectation management on their part. I agree with<span class="Apple-converted-space"> </span><br>the statement that DNSMON and other similar tools do not provide direct<span class="Apple-converted-space"> </span><br>insight into end user experience, but that is also not their goal.<span class="Apple-converted-space"> </span><br>DNSMON at least is deliberately designed to measure from stable vantage<span class="Apple-converted-space"> </span><br>points (RIPE Atlas anchors, formerly TTM boxes), and makes no attempt to<span class="Apple-converted-space"> </span><br>simulate how recursive resolvers and end user operating systems may<span class="Apple-converted-space"> </span><br>behave. In fact, it avoids such attempts, even to the point that it<span class="Apple-converted-space"> </span><br>never retries a failed query, which most clients would do. I would argue<span class="Apple-converted-space"> </span><br>that this is a feature of the system, providing as it does a nice clear<span class="Apple-converted-space"> </span><br>signal that functions as a good metric for traffic between recursive<span class="Apple-converted-space"> </span><br>resolvers and the authoritative servers.<span class="Apple-converted-space"> </span><br><br>For reference, this is what DNSMON "saw" during the reported time<span class="Apple-converted-space"> </span><br>period, which seems to correspond to the times in the report:<span class="Apple-converted-space"> </span><br><br>[…]</div></div></span></blockquote></div><p>Fully agreed, but I still don’t see why they are downplaying the event like this.</p><p>Tools such as DNSMON are useful, and of course need to be taken with a grain of salt and not blindly believed “as it”.</p><p>A lot of users/eyeballs have noticed problems, so pretending this did not happen is not really… constructive.</p><p>(OK, they did not pretend this did not happen, but downplaying is kind of the same to me).</p><p><br></p><p>Cheers,</p><p>-- </p><p>Nico</p><div></div></body></html>