[182974] in North American Network Operators' Group
Re: Did *bufferbloat* cause the 2010 flashcrash?
daemon@ATHENA.MIT.EDU (Sean Donelan)
Thu Aug 6 13:30:35 2015
X-Original-To: nanog@nanog.org
Date: Thu, 6 Aug 2015 13:28:19 -0400 (EDT)
From: Sean Donelan <sean@donelan.com>
To: nanog list <nanog@nanog.org>
In-Reply-To: <CAL9jLaapgN7TRtTf4A3hs7vuJyXzwA+f6-O+gAND9Fc6bY47Nw@mail.gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Thu, 6 Aug 2015, Christopher Morrow wrote:
> bufferbloat is the boogieman... of late. I think that's foolish :(
> I think this comment from jtk is really on point though! 'why only
> then?' that sure seems convenient, eh?
Failures almost never have a single cause.
Transport networks are never perfect, i.e. delays, dropped packets, data
corruption, etc. They may be contributing factors, or a combination of
rare events. The hard question that SEC and the industry has been
wrestling with is "Why?" not so much "How?"
The apparent condititions didn't change, but the system reacted
differently during those seconds. Why? What was different?
