From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-f43.google.com (mail-yw0-f43.google.com [209.85.213.43]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 46A6E201745 for ; Fri, 13 May 2011 16:59:18 -0700 (PDT) Received: by ywa6 with SMTP id 6so1485404ywa.16 for ; Fri, 13 May 2011 17:07:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=fScXt7q1uBHfEDQTUeXJxAxLftmjAEcF/KjQVMCh0fI=; b=SxzdUmsBaP2yuTnHHXZScUq0H2QGXAwexLNDdrRhfR8ppNQ9jQN5C6tPJWnSeiA6Lj KJZ/EoWY9Ga5F84UjtQB7hZk2JxbsmZhNVE3fDzMzGOjx05zYV/L0trO6nnNdmJToQTt Pwq64c3wMO8Dz9ve+IR8cTO0lDTvTYg2/AyZ0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hQzJ9jPTj3/kJSGgLl9YmmqW1widwDADqFalKTfQF3bJdVvob3LAkNi9rsTqfG/HXC eL6uW6AiWrmf8NYLX2FFt0+zZL08Wjtc7b9aFhLIxcwt3AkDkNccE/FVc+pXOKI23xx+ l7TKTpcuwAy8qmAuAyUrnlFqMudLAYWXmK88o= MIME-Version: 1.0 Received: by 10.100.50.27 with SMTP id x27mr362853anx.16.1305331664132; Fri, 13 May 2011 17:07:44 -0700 (PDT) Received: by 10.100.57.9 with HTTP; Fri, 13 May 2011 17:07:44 -0700 (PDT) Date: Fri, 13 May 2011 20:07:44 -0400 Message-ID: From: jeff sacksteder To: bloat@lists.bufferbloat.net Content-Type: text/plain; charset=ISO-8859-1 Subject: [Bloat] Strategy for consumers 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, 13 May 2011 23:59:18 -0000 I've recent moved to an area(Frontier Communications) with a serious bufferbloat problem on it's consumer DSL products. Maybe I'm not looking in the correct places, but has there been any discussion of contacting the NOC operators or network engineers at various ISPs to make whatever remediation is possible through configuration changes? It might also be useful to have a database of configuration changes on specific equipment to point to in the event that you are actually able to speak to a qualified network engineer.