From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by huchra.bufferbloat.net (Postfix) with ESMTP id 5F1D521F0AE for ; Mon, 10 Jun 2013 06:19:01 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2EAFB20178; Mon, 10 Jun 2013 09:32:11 -0400 (EDT) Received: by sandelman.ca (Postfix, from userid 179) id 7AE0563A8C; Mon, 10 Jun 2013 09:18:05 -0400 (EDT) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 6D10D63A7C; Mon, 10 Jun 2013 09:18:05 -0400 (EDT) From: Michael Richardson To: bloat 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: Ian Subject: [Bloat] experimental TCP theatre/LARP --- June 7 talk at oclug 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: Mon, 10 Jun 2013 13:19:01 -0000 I did my talk on June 7. It was an attempt to implement TCP as theatre. It did not go as well as I would have liked, VJ's fountain analogy is much more powerful, but significantly less portable. We implemented the Toffee Consumption Protocol, which involved moving candies from one table to another, using shot-glasses to represent segments of data, and playing cards to represent sequence numbers. Slides are at: http://www.sandelman.ca/SSW/talks/toffee-control-protocol-2013/bloatgame.html I should have included more supporting material from Nichols paper. I was concerned that the transmitter would operate too fast, and that I would be unable to slow the packets down enough. In fact the transmitter didn't have enough power, and the packets did go to fast, and we got no interesting congestion. A key thing is that packets take longer (visually, have to stretch out!) when going through a constriction. It might have been possible to implement that had we used multiple people to carry a single packet. So for instance, using canoe paddles or sticks or tent poles for packets rather than candy. -- ] 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 [