From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by huchra.bufferbloat.net (Postfix) with ESMTP id 76CDC21F0AE for ; Tue, 12 Feb 2013 12:02:52 -0800 (PST) Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id DD36020177; Tue, 12 Feb 2013 15:09:10 -0500 (EST) Received: by sandelman.ca (Postfix, from userid 179) id 753916376A; Tue, 12 Feb 2013 15:01:48 -0500 (EST) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 63544636C5; Tue, 12 Feb 2013 15:01:48 -0500 (EST) From: Michael Richardson To: "Eggert, Lars" In-Reply-To: References: <21027.1360683218@sandelman.ca> X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22) X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Sender: mcr@sandelman.ca Cc: Dan York , "" Subject: Re: [Bloat] bloat in the industry 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, 12 Feb 2013 20:02:52 -0000 >>>>> "Eggert," == Eggert, Lars writes: >> 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. Eggert> something else that (maybe in addition) could be useful Eggert> would be to document the bufferbloat symptoms and causes in Eggert> an RFC. Then you could refer your suppliers to said RFC and Eggert> request them to state that their gear does *not* exhibit Eggert> the documented issues. I agree that this would help, it's the first step. The document needs to be authored with someone with some serious transport credentials. I'm not such a person. Transcribing Van Jacobson's IETF84 presentation would almost be enough... (https://plus.google.com/107942175615993706558/posts/F6G2qAD6fPN) -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [