From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by huchra.bufferbloat.net (Postfix) with ESMTP id 3E304200619 for ; Tue, 8 Jan 2013 11:03:30 -0800 (PST) Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 9E18980003B; Tue, 8 Jan 2013 11:03:29 -0800 (PST) X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: bloat@lists.bufferbloat.net From: Hal Murray Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Jan 2013 11:03:29 -0800 Message-Id: <20130108190329.9E18980003B@ip-64-139-1-69.sjc.megapath.net> Cc: Hal Murray Subject: Re: [Bloat] bufferbloat paper 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: Tue, 08 Jan 2013 19:03:30 -0000 > Aside from their dataset having absolutely no reflection on the reality of > the 99.999% of home users running at speeds two or three or *more* orders of > magnitude below that speed, it seems like a nice paper. Did any of their 90 homes contained laptops connected over WiFi? > Here is a plot (also at http://web.mit.edu/keithw/www/verizondown.png) from > a computer tethered to a Samsung Galaxy Nexus running Android 4.0.4 on > Verizon LTE service, taken just now in Cambridge, Mass. Neat. Thanks. Any ideas on what happened at 120 seconds? Is that a pattern I should recognize? Is there an event that triggers it? Is it something as simple as a single lost packet? -- These are my opinions. I hate spam.