[ledbat] "Oh Noes, the Internetz will Melt Down..."

Nicholas Weaver <nweaver@ICSI.Berkeley.EDU> Mon, 01 December 2008 15:57 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 9B4843A68D0; Mon, 1 Dec 2008 07:57:17 -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 362B23A68D0 for <ledbat@core3.amsl.com>; Mon, 1 Dec 2008 07:57:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 cl8hIl0OmMZd for <ledbat@core3.amsl.com>; Mon, 1 Dec 2008 07:57:15 -0800 (PST)
Received: from fruitcake.ICSI.Berkeley.EDU (fruitcake.ICSI.Berkeley.EDU [192.150.186.11]) by core3.amsl.com (Postfix) with ESMTP id 47A213A6868 for <ledbat@ietf.org>; Mon, 1 Dec 2008 07:57:15 -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 mB1Fur6H010481; Mon, 1 Dec 2008 07:57:03 -0800 (PST)
Message-Id: <34F38819-7926-4659-952B-3059B2B45C56@icsi.berkeley.edu>
From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
To: ledbat@ietf.org
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 01 Dec 2008 07:56:52 -0800
X-Mailer: Apple Mail (2.929.2)
Cc: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
Subject: [ledbat] "Oh Noes, the Internetz will Melt Down..."
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

The typical Fear Mongering "UDP Death Uhz Da Internetz":

http://www.theregister.co.uk/2008/12/01/richard_bennett_utorrent_udp/

However, the question is, does anyone have insight into the "uTP"  
congestion control protocol and what it is actually doing?  Is it  
"AIMD + delay based?" which was discussed at the IETF meeting, which  
still has the multi-flow unfairness issue (the ISP congestion problem  
stays the same, but isn't made worse or better), but addresses the  
buffer-congestion problem?

Or is it something else?

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