From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 03A3B21F5A9; Fri, 12 Sep 2014 05:17:00 -0700 (PDT) Received: by mail-qc0-f175.google.com with SMTP id c9so674336qcz.6 for ; Fri, 12 Sep 2014 05:16:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=420nasvF1s8SPXPJpKnWlsnpfTlsb9h4cYbLM8uiwa4=; b=FAnYvWM7U7QOWbINVwhuqsGvC+G/kleHmYzmByoO20sx5OK7JKLkFckffytylyp4QC xWgV+lMjWey5v4AMqVye4/ltyc1n/Dtjse73yu1LBPqJD3WrnM23UUGu82J3EyL5wsRW 0oiXyelRa/7ykM4H65cAPh91MnP4ExjhK+lq45nf4hlplDeALq1g9uBD7aQGe0aslxoQ +Nu81hKcJXE33h1Yjp4RVr70kj5ctp+/zbqix56FR+6WZf8PW9bA7HdgKwY26pjSZo/J L/z3NLfzArzes8hwb1B7d9phIKKYJauI8x2SDUX7Psyyz03B5tgCACOdYlfvBBHC36yv MOsw== X-Received: by 10.140.30.227 with SMTP id d90mr1874761qgd.55.1410524217724; Fri, 12 Sep 2014 05:16:57 -0700 (PDT) Received: from richs-mbp-5818.home.lan (pool-71-241-220-44.ptldme.east.myfairpoint.net. [71.241.220.44]) by mx.google.com with ESMTPSA id s4sm2843094qay.36.2014.09.12.05.16.56 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Sep 2014 05:16:57 -0700 (PDT) Content-Type: multipart/signed; boundary="Apple-Mail=_3B261095-EA68-4384-9D96-320C5BB17269"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Rich Brown In-Reply-To: <20140912091730.2e762c93@redhat.com> Date: Fri, 12 Sep 2014 08:16:46 -0400 Message-Id: References: <20140912091730.2e762c93@redhat.com> To: Jesper Dangaard Brouer X-Mailer: Apple Mail (2.1878.6) Cc: Wes Felter , bloat , "cerowrt-devel@lists.bufferbloat.net" , =?utf-8?Q?Joel_Wir=C4=81mu_Pauling?= Subject: Re: [Bloat] Fixing bufferbloat: How about an open letter to the web benchmarkers? X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2014 12:17:29 -0000 --Apple-Mail=_3B261095-EA68-4384-9D96-320C5BB17269 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Sep 12, 2014, at 3:17 AM, Jesper Dangaard Brouer = wrote: > On Thu, 11 Sep 2014 20:13:19 -0400 > Rich Brown wrote: >=20 >> I'll sign too. (And I like the 98th percentile measure for each >> direction to give a single number that represents what's happening. = It >> could include ping loss rate, as well...) >=20 > I'll sign too. >=20 > The 98th percentile latency is of-cause nice, but we should remember = to > keep our request simple. I did try a simple request and got a lukewarm response. You can see the = gist of my correspondence with the test companies in = https://lists.bufferbloat.net/pipermail/cerowrt-devel/2014-September/00351= 7.html Rich =20 > "Dear speedtest.net/speedof.me please add a latency test, that = measures > latency during the upload and download test-runs." >=20 > That will be the first baby step, don't make it too complicated for > them, afterwards we can start explaining if we want min/max or 98th > percentile. >=20 > They already have a ping facility, which the only run _before_ = starting > the test run. Thus, they should be-able to easily adapt their = existing > "ping" code to measure during the test-runs... give then something = they > can easily do. >=20 > --=20 > Best regards, > Jesper Dangaard Brouer > MSc.CS, Sr. Network Kernel Developer at Red Hat > Author of http://www.iptv-analyzer.org > LinkedIn: http://www.linkedin.com/in/brouer --Apple-Mail=_3B261095-EA68-4384-9D96-320C5BB17269 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUEuQ0AAoJEH4agC/0z73/R4oH/RNCDSSWXj9uLRD7Xrgvy7Wx QXu605egzI7eVcsmeImfqcYQuzsjYHZx3MWHX5iXcFveW1fuS4fkTaCi7DPa6Xm3 hev1hPDJ8jMig+YfPX/EddUFZJji37CmC+97FO2V7ckzy8mLbXLW+k5B2cr1ODRw WCPhQgF7UOFG4NyFEkgE1vIvnZ/qEsbd+UB/f9aNXUJbnpdpDs5rj2ahVnnfKaq3 UU2/+LHndSGvHym9lcT4qlR/rSL9NjhIqImRRpiNOcwZAbSYvHDfvVvmZXdgX3iz LfDAu0RvhZ/4bSdJTM7K9Wafi+RgTXi2KVk/8oABcfjAbFRKXlP5UEiutAWcE7k= =wvCJ -----END PGP SIGNATURE----- --Apple-Mail=_3B261095-EA68-4384-9D96-320C5BB17269--