[Bloat] bloat in the industry

[Eggert, Lars]

Hi,

On Feb 12, 2013, at 7:33, Michael Richardson <mcr at 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