From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by huchra.bufferbloat.net (Postfix) with ESMTP id 8527B21F1EF for ; Sun, 8 Dec 2013 12:41:53 -0800 (PST) Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id B9918406062; Sun, 8 Dec 2013 12:41:52 -0800 (PST) X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: bloat@lists.bufferbloat.net From: Hal Murray Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Dec 2013 12:41:52 -0800 Message-Id: <20131208204152.B9918406062@ip-64-139-1-69.sjc.megapath.net> Cc: Hal Murray Subject: Re: [Bloat] curious..... 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: Sun, 08 Dec 2013 20:41:53 -0000 > Even at 1000 symmetric I still think it would be a good idea to isolate > really latency critical traffic from the rest, even if under normal > circumstances there should be no problem, I guess a "better safe than sorry" > approach. But, hey I do not do this for a living so I might be on the wrong > track here. The problem is who gets to decide what is latency critical and/or how to do it such that the bad-guys can't game the system. Has somebody made a list of various interesting cases, and where they break? -- These are my opinions. I hate spam.