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 2596921F0F0; Tue, 11 Jun 2013 11:20:12 -0700 (PDT) Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2437620191; Tue, 11 Jun 2013 14:33:27 -0400 (EDT) Received: by sandelman.ca (Postfix, from userid 179) id 1505763A8C; Tue, 11 Jun 2013 14:19:15 -0400 (EDT) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id E0FCE639DF; Tue, 11 Jun 2013 14:19:15 -0400 (EDT) From: Michael Richardson To: Tristan Seligmann In-Reply-To: References: <51817A6F.1080006@superduper.net> <86AA48E0-B5CD-4A94-AF2B-D75178E8C660@gmail.com> <5181CD56.9050501@superduper.net> <71A0D0CD-9095-4AA5-93C3-FF55CC495788@gmail.com> <1368498364.1479.5.camel@ganymede.home> 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 Siemon , Jonathan Morton , codel@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net, bloat@lists.bufferbloat.net Subject: Re: [Cerowrt-devel] [Bloat] [Codel] Latest codel, fq_codel, and pie sim study from cablelabs now available X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jun 2013 18:20:12 -0000 >>>>> "Tristan" == Tristan Seligmann writes: >> It's pretty easy to configure the Transmission Bittorrent client to mark >> packets. >> Tristan> Unfortunately this only helps with outgoing traffic. Marking on inbound Tristan> traffic is at the mercy of the torrent peer and your ISP (in my case, my Tristan> ISP seems to overwrite the TOS/DS field indiscriminately, Tristan> not that you Ultimately, one wants PCP and/or RSVP and/or NSIS from the torrent client to the local router, as the torrent client knows the 5-tuple of the incoming packets. Local router would in utopian world, in a diffedge scenario be able to communicate that policy to ISP edge router, but at least, the local router can police that flow. -- ] 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 [