From: jeff sacksteder <jsacksteder@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] Strategy for consumers
Date: Fri, 13 May 2011 20:07:44 -0400 [thread overview]
Message-ID: <BANLkTikjXUmv1tg95ouerc3NqYzU3359Gw@mail.gmail.com> (raw)
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.
next reply other threads:[~2011-05-13 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 0:07 jeff sacksteder [this message]
2011-05-14 14:05 ` Jim Gettys
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTikjXUmv1tg95ouerc3NqYzU3359Gw@mail.gmail.com \
--to=jsacksteder@gmail.com \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox