<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi Jim,<div><br></div><div>I'm glad you've got this letter going. I have started to write (mentally) this note several times, but two things always checked my momentum:</div><div><br></div><div>- Last summer, I sent notes asking the big speed test sites simply to add a latency test. (<a href="http://speedtest.net">speedtest.net</a>, <a href="http://testmy.net">testmy.net</a>, <a href="http://speedof.me">speedof.me</a>). All three responded that (basically) they would ask their developers about it, and you can see the (non) results. </div><div><br></div><div>- I'm afraid that it's not in their self-interest to add a latency test. Especially Ookla - I see their test package bundled as part of the offering for lots of ISPs. Ookla are hardly going to "enhance" their speed test in such a way that customer's customers can plainly see, "Congratulations on starting your service with us. You can see your speeds are pretty good, but you get an F- for bufferbloat."</div><div><br></div><div>The latter point is the reason that I'm so glad that Justin has added the latency test. <a href="http://DSLReports.com">DSLReports.com</a> doesn't have any sacred cows to protect, so they're free to call it as it is. And I also love that they do it with a letter grade: "Hey, dude. Your connection is bloated, and you get a D".</div><div><br></div><div>There is still a long row to hoe, but as more and more people get de-bloated, the test will help spread around the knowledge that "it doesn't have to be that way". </div><div><br></div><div>Rich</div><div><br></div><div><br><div><div><div>On May 15, 2015, at 12:16 PM, Jim Gettys <<a href="mailto:jg@freedesktop.org">jg@freedesktop.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_default" style="">Even before I knew about the wonderful DSLreports bufferbloat test, I had started working on a document to help people like that (e.g. Ookla) understand how to do bufferbloat testing. The document also grew a bit beyond that topic, by the time it was done....</div><div class="gmail_default" style=""><br></div><div class="gmail_default" style="">The document is at:</div><div class="gmail_default" style=""><br></div><div class="gmail_default" style=""><a href="https://docs.google.com/document/d/1z5NN4WRKQKK-RtxtKR__XIwkybvsKEmunek2Ezdw_90/edit?usp=sharing">https://docs.google.com/document/d/1z5NN4WRKQKK-RtxtKR__XIwkybvsKEmunek2Ezdw_90/edit?usp=sharing</a><br></div><div class="gmail_default" style=""><br></div><div class="gmail_default" style="">Comments welcome. <br></div><div class="gmail_default" style=""><br></div><div class="gmail_default" style="">It's intended long term home is the <a href="http://bufferbloat.net/">bufferbloat.net</a> wiki, but I've found Google doc's commenting feature really useful.</div><div class="gmail_default" style=""> - Jim</div><div class="gmail_default" style=""><br></div></div>
_______________________________________________<br>Bloat mailing list<br><a href="mailto:Bloat@lists.bufferbloat.net">Bloat@lists.bufferbloat.net</a><br>https://lists.bufferbloat.net/listinfo/bloat<br></blockquote></div><br></div></div></body></html>