From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-12-ewr.dyndns.com (mxout-165-ewr.mailhop.org [216.146.33.165]) by lists.bufferbloat.net (Postfix) with ESMTP id D7F042E02E9 for ; Sat, 5 Feb 2011 11:49:02 -0800 (PST) Received: from scan-12-ewr.mailhop.org (scan-12-ewr.local [10.0.141.230]) by mail-12-ewr.dyndns.com (Postfix) with ESMTP id EFB91932BD6 for ; Sat, 5 Feb 2011 19:49:01 +0000 (UTC) X-Spam-Score: 0.0 () X-Mail-Handler: MailHop by DynDNS X-Originating-IP: 24.71.223.10 Received: from idcmail-mo1so.shaw.ca (idcmail-mo1so.shaw.ca [24.71.223.10]) by mail-12-ewr.dyndns.com (Postfix) with ESMTP id 46F83932AC5 for ; Sat, 5 Feb 2011 19:49:01 +0000 (UTC) Received: from pd2ml1so-ssvc.prod.shaw.ca ([10.0.141.139]) by pd3mo1so-svcs.prod.shaw.ca with ESMTP; 05 Feb 2011 12:49:01 -0700 X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=6EkEX6JM2LCztCEhkE317K9SpBSN4cB8nbuuHVfFIzI= c=1 sm=1 a=VTUP8yi54EUA:10 a=BLceEmwcHowA:10 a=wPDyFdB5xvgA:10 a=xqWC_Br6kY4A:10 a=EvaGpPYFoCfc2jwbaD6Azw==:17 a=b7SLfKwVAAAA:8 a=kurRqvosAAAA:8 a=3dZX8JWgAAAA:8 a=_ET-mynFqgEhYBBD3xwA:9 a=f0YPkmzrnXVTmUtsXk8A:7 a=MEobavrYI34l0jsScTBZGNe-Yx8A:4 a=Fw8iwiUKpeAA:10 a=Ls3g0dwzjE0A:10 a=TphoKWqS9HQA:10 a=kYWxGs7lXrSgJ3Zm:21 a=0hQcajwXxuqKK3lR:21 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Received: from unknown (HELO amd.pacdat.net) ([96.48.77.169]) by pd2ml1so-dmz.prod.shaw.ca with ESMTP; 05 Feb 2011 12:49:00 -0700 Received: from localhost ([::1]) by amd.pacdat.net with esmtp (Exim 4.69) (envelope-from ) id 1Plo7v-0007Kv-5h; Sat, 05 Feb 2011 11:49:00 -0800 From: richard To: esr@thyrsus.com In-Reply-To: <20110205132305.GA29396@thyrsus.com> References: <20110205132305.GA29396@thyrsus.com> Content-Type: text/plain Date: Sat, 05 Feb 2011 11:48:58 -0800 Message-Id: <1296935338.12017.60.camel@amd.pacdat.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) Content-Transfer-Encoding: 7bit X-Spam_score: -2.9 X-Spam_score_int: -28 X-Spam_bar: -- Cc: bloat@lists.bufferbloat.net Subject: Re: [Bloat] First draft of complete "Bufferbloat And You" enclosed. 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: Sat, 05 Feb 2011 19:49:03 -0000 Having been one of the commercial internet pioneers here in Canada, I've spent a lot of time dealing with the end users. I like to write, and one of the things I try to do is explain computer problems to my dumb relatives, customers, friends etc. I like your vehicle analogy but I think today's network-using public can relate better to a real-world situation in the internet so I've put together my own article on the problem. I'd already started the article last week and finally got to finish it today. http://digital-rag.com/article.php/Buffer-Bloat-Packet-Loss It could have some more technical terms (latency for example) added to it but I limited it to the concept of window and ACK for now. It takes the content of a recent ad from a local ISP and talks about what is actually going on "under the hood" richard On Sat, 2011-02-05 at 08:23 -0500, Eric Raymond wrote: > I consider this draft coverage-complete for the basic introduction I was > aiming at. Suggestions from dtaht5 and jg have been incorporated where > appropriate. Critique and correct, but try not to make it longer. I'm a > bit unhappy about the length and may actually try to cut it. > > You will note that the description of network failure modes is > somewhat broader than in jg's talk. So is the section on why QoS > fails to address the problem. This is me putting on my > system-architect head and doing original analysis; if you think I have > misunderstood the premises or reasoned about them incorrectly, tell > me. > > Please fix typos and outright grammatical errors. If you think you have spotted > a higher-level usage problem or awkwardness, check with me before changing it. > What you think is technically erroneous may be expressive voice. > > Explanation: Style is the contrast between expectation and surprise. > Poets writing metric poetry learn to introduce small breaks in > scansion in order to induce tension-and-release cycles at a higher > level that will hold the reader's interest. The corresponding prose > trick is to bend usage rules or change the register of the writing > slightly away from what the reader unconsciously expects. If you try > to "fix" these you will probably be stepping on an intended effect. > So check first. > > (I will also observe that unless you are already an unusually skilled > writer, you should *not* try to replicate this technique; the risk of > sounding affected or just teeth-jarringly bad is high. As Penn & > Teller puts it, "These stunts are being performed by trained, > *professional* idiots.") > > Future directions: unless somebody stops me, I'm going to reorganize > what wiki docs there are around this thing. The basic idea is to make this > the page new visitors naturally land on *first*, with embedded > hotlinks to the more specialized stuff. > > Explanation: Outlines and bulleted lists of stuff are deadly. They're > great for reference, but they scream "too much; don't read" to people > first trying to wrap their heads around a topic. Narrative > introductions with hotlinks are both less threatening and more > effective. The main reason they're not used more is that most people > find them quite hard to write. I don't. > > If I decide I need to cut the length, I'll push some subsections down > to linked subpages. > > I haven't learned Textile yet. I'll probably get to that this weekend. > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat -- Richard C. Pitt Pacific Data Capture rcpitt@pacdat.net 604-644-9265 http://digital-rag.com www.pacdat.net PGP Fingerprint: FCEF 167D 151B 64C4 3333 57F0 4F18 AF98 9F59 DD73