Re: [ledbat] list of reasons for needing multiple TCP connections

Nicholas Weaver <nweaver@ICSI.Berkeley.EDU> Tue, 02 December 2008 03:11 UTC

Return-Path: <ledbat-bounces@ietf.org>
X-Original-To: tana-archive@ietf.org
Delivered-To: ietfarch-tana-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA51D3A6BC5; Mon, 1 Dec 2008 19:11:23 -0800 (PST)
X-Original-To: ledbat@core3.amsl.com
Delivered-To: ledbat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A91DD3A6BC5 for <ledbat@core3.amsl.com>; Mon, 1 Dec 2008 19:11:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.562
X-Spam-Level:
X-Spam-Status: No, score=-6.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0j9W5LNp+tHE for <ledbat@core3.amsl.com>; Mon, 1 Dec 2008 19:11:21 -0800 (PST)
Received: from fruitcake.ICSI.Berkeley.EDU (fruitcake.ICSI.Berkeley.EDU [192.150.186.11]) by core3.amsl.com (Postfix) with ESMTP id D4B763A6BB7 for <ledbat@ietf.org>; Mon, 1 Dec 2008 19:11:21 -0800 (PST)
Received: from [IPv6:::1] (fruitcake [192.150.186.11]) by fruitcake.ICSI.Berkeley.EDU (8.12.11.20060614/8.12.11) with ESMTP id mB23A1Jm014735; Mon, 1 Dec 2008 19:11:11 -0800 (PST)
Message-Id: <8ADD85A3-CA3F-485E-B9E1-4440AFA713AA@icsi.berkeley.edu>
From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
To: Richard Bennett <richard@bennett.com>
In-Reply-To: <4934A642.7010005@bennett.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 01 Dec 2008 19:10:01 -0800
References: <4925BDEE.6090101@isi.edu> <8c99930d0811201206yb0ef259v28c361438cb14773@mail.gmail.com> <DC2CEB0C-4C70-42CD-8ADE-AFF4E45B1915@shlang.com> <C3E8A5B2-16BE-47FD-9DD9-5AFCBA6BEBED@nokia.com> <492F27F3.3020309@bennett.com> <3efc39a60812011438s71066079s4b467eab43d7a998@mail.gmail.com> <49346C79.8090308@bennett.com> <3efc39a60812011527s361af2ben9a333f5f92bfa1cc@mail.gmail.com> <493474B4.40607@bennett.com> <3efc39a60812011846q61469f5cle3bc5747e507300d@mail.gmail.com> <4934A642.7010005@bennett.com>
X-Mailer: Apple Mail (2.929.2)
Cc: "ledbat@ietf.org" <ledbat@ietf.org>, Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
Subject: Re: [ledbat] list of reasons for needing multiple TCP connections
X-BeenThere: ledbat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list of the LEDBAT WG <ledbat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ledbat>, <mailto:ledbat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ledbat>
List-Post: <mailto:ledbat@ietf.org>
List-Help: <mailto:ledbat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ledbat>, <mailto:ledbat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ledbat-bounces@ietf.org
Errors-To: ledbat-bounces@ietf.org

On Dec 1, 2008, at 7:06 PM, Richard Bennett wrote:

> Actually, this article in DSL Reports started the recent discussion  
> about BitTorrent over UDP:
>
> http://www.dslreports.com/shownews/New-UDP-uTorrent-Takes-Aim-At-Throttling-99366
>
> The title is: "New UDP uTorrent Takes Aim At Throttling". The  
> author, Karl Bode, is aware that UDP is one of the methods that P2P  
> programmers have discussed over the years for avoiding traffic  
> shaping. There's nothing particularly obscene about attempting to  
> work through the implications of trade-offs; this is what engineers  
> do.
>
> Several people have objected to the implication that the sole  
> purpose of making UDP the default transport was management evasion,  
> and I'll correct that notion in a follow-up piece. That being said,  
> there are still important issues to explore in relation to the  
> Internet infrastructure, for "whoever designs it."

We've had confirmation that the udp protocol being on-by-default in  
uTorrent is the same AIMD + delay-based that was presented at the IETF.

AIMD + delay-based means it can't make the ISP's congestion problem  
worse (it may make it better but thats an open question), but it  
definatly makes the access-link congestion better.

So rather than "getting around" traffic management (which doesn't work  
anyway), this is specifically about reducing the network impact,  
especially on the local access point.

_______________________________________________
ledbat mailing list
ledbat@ietf.org
https://www.ietf.org/mailman/listinfo/ledbat