From: "Eggert, Lars" <lars@netapp.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Dan York <york@isoc.org>,
"<bloat@lists.bufferbloat.net>" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] bloat in the industry
Date: Tue, 12 Feb 2013 16:30:06 +0000 [thread overview]
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E91F709263@SACEXCMBX01-PRD.hq.netapp.com> (raw)
In-Reply-To: <21027.1360683218@sandelman.ca>
Hi,
On Feb 12, 2013, at 7:33, Michael Richardson <mcr@sandelman.ca> wrote:
> What *I* need is a place, perhaps at isoc.org, where key contacts on the
> bufferbloat issue at each vendor can be kept, and I could refer sales
> person from vendor X to bufferbloat expert at vendor X.
> It needs to be vaguely wiki-ish and forum-ish (as much as I hate
> forums), so that even if we can't get vendor Z to fix their product, we
> can at least share information about what did work and what didn't work.
something else that (maybe in addition) could be useful would be to document the bufferbloat symptoms and causes in an RFC. Then you could refer your suppliers to said RFC and request them to state that their gear does *not* exhibit the documented issues.
In a second step, you'd want to be able to point to RFCs standardizing solutions to bufferbloat. But that may take longer to get done. Documenting the problem in an Informational RFC should be faster.
Lars
next prev parent reply other threads:[~2013-02-12 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 15:33 Michael Richardson
2013-02-12 16:30 ` Eggert, Lars [this message]
2013-02-12 20:01 ` Michael Richardson
2013-02-21 11:58 ` Matthew Ford
2013-02-21 12:47 ` MUSCARIELLO Luca OLNC/OLN
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=D4D47BCFFE5A004F95D707546AC0D7E91F709263@SACEXCMBX01-PRD.hq.netapp.com \
--to=lars@netapp.com \
--cc=bloat@lists.bufferbloat.net \
--cc=mcr@sandelman.ca \
--cc=york@isoc.org \
/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