From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) (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 14D4621F392 for ; Fri, 15 May 2015 09:17:03 -0700 (PDT) Received: by wguv19 with SMTP id v19so56444560wgu.1 for ; Fri, 15 May 2015 09:16:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=DXJr5c29YGOf3GtH7V7D361fFoceivH3gWBldWCeR5c=; b=WZLIcL69KzvXHH74F4YliDVhOOnsDN/aHa16/pY4vn6Wu8kBky2nzuurlv/dTcLsmY GIlzAiEqEX/2tVf23ROVBZvjIibLEiO0zgre2ZzE0wTqoAsY7/42M41YKjER3B+xOm1L 2nUoNUSiW1zN0fQ+FuotF1LuaSehEIplj/bUZ/XxtBBVE97DISECG2t4psUyLyUlRZhe yxnEUBH9AOcs+9XtzRWx6kNOPf4+2OsJHhS3CwzzJIhr6X88ac1xd1EvzG+FolAWR6mJ fK77Sb+D68UL3B09JMWfJjzxxvBtzWL/NU14OKkOOwiNuK1rpfAWfwNtNxuTakEdVfij L48Q== MIME-Version: 1.0 X-Received: by 10.180.187.232 with SMTP id fv8mr26955243wic.28.1431706616617; Fri, 15 May 2015 09:16:56 -0700 (PDT) Sender: gettysjim@gmail.com Received: by 10.194.118.166 with HTTP; Fri, 15 May 2015 09:16:56 -0700 (PDT) Date: Fri, 15 May 2015 12:16:56 -0400 X-Google-Sender-Auth: 4rNdNZAhXGndYGwRolp-D9rIpro Message-ID: From: Jim Gettys To: bloat Content-Type: multipart/alternative; boundary=001a11c384a24e603d0516212c93 Subject: [Bloat] General Bufferbloat Testing Document. 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, 15 May 2015 16:17:46 -0000 --001a11c384a24e603d0516212c93 Content-Type: text/plain; charset=UTF-8 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.... The document is at: https://docs.google.com/document/d/1z5NN4WRKQKK-RtxtKR__XIwkybvsKEmunek2Ezdw_90/edit?usp=sharing Comments welcome. It's intended long term home is the bufferbloat.net wiki, but I've found Google doc's commenting feature really useful. - Jim --001a11c384a24e603d0516212c93 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Even before I knew abou= t the wonderful DSLreports bufferbloat test, I had started working on a doc= ument to help people like that (e.g. Ookla) understand how to do bufferbloa= t testing.=C2=A0 The document also grew a bit beyond that topic, by the tim= e it was done....

The document is at:


Comments welco= me.=C2=A0

It's intended long term home is the bufferbloat.net wiki, but I've found Googl= e doc's commenting feature really useful.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Jim

--001a11c384a24e603d0516212c93--