Re: [multipathtcp] High-level design decisions /architecture

Mark Handley <M.Handley@cs.ucl.ac.uk> Tue, 03 November 2009 16:43 UTC

Return-Path: <mark.j.handley@gmail.com>
X-Original-To: multipathtcp@core3.amsl.com
Delivered-To: multipathtcp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9C7D28C0EF for <multipathtcp@core3.amsl.com>; Tue, 3 Nov 2009 08:43:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.76
X-Spam-Level:
X-Spam-Status: No, score=-1.76 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 cY+7X8A3adap for <multipathtcp@core3.amsl.com>; Tue, 3 Nov 2009 08:43:47 -0800 (PST)
Received: from mail-bw0-f223.google.com (mail-bw0-f223.google.com [209.85.218.223]) by core3.amsl.com (Postfix) with ESMTP id C943A28C0E0 for <multipathtcp@ietf.org>; Tue, 3 Nov 2009 08:43:46 -0800 (PST)
Received: by bwz23 with SMTP id 23so7817042bwz.29 for <multipathtcp@ietf.org>; Tue, 03 Nov 2009 08:44:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type; bh=l/0uwATGO6ivLJ85y/27OHF7ZJi629ii+HqefviIPo8=; b=jqBOPW0lrQodhxEbRYWNYHZZf/LbxOeyaRx1NnMXGiWe5pfnq/XB6j2eYzwUmVUCIP y0skamwZzF+r2g5WFfEZ56ElF2u3Kpv6m2/zANQmciICvHXRwbPJv/xjuz0PoUxEpefK ucUkbzG2NBLszuROfnmVf4AX4hVBHh2OSqwFk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=tpJ5JCe9ySlTDmWCokBBB2n12HSNvK6NlqtPaGqzhMV/ffq8X93AYLTbvz96nOCNeU t4QZDZSTR5zY4ojuTMaG2h+t7oqLl3vK+b7MszAVRR/ZTSJ4Zjx+ns9s+VopNxpMtqyZ NHXAlL/vrm4OJod8Qnut2oYLgH3+awHsrYo7s=
MIME-Version: 1.0
Sender: mark.j.handley@gmail.com
Received: by 10.223.29.193 with SMTP id r1mr35389fac.29.1257266643261; Tue, 03 Nov 2009 08:44:03 -0800 (PST)
In-Reply-To: <4AF05A0F.6040705@isi.edu>
References: <4A916DBC72536E419A0BD955EDECEDEC06363A62@E03MVB1-UKBR.domain1.systemhost.net> <3c3e3fca0911021328h2ef65493v9f0290f384f7b800@mail.gmail.com> <4AEF6114.6070106@it.uc3m.es> <3c3e3fca0911021538y3ebd3f3fx6a03e7bc5b03f246@mail.gmail.com> <84a612dd0911021640s3820b7b1w3602b63f3d568527@mail.gmail.com> <4AEF7FB3.4020604@isi.edu> <98B687E1-CB11-47E2-84A6-2F7F7ECAFB95@nokia.com> <4AF05758.4080309@isi.edu> <6E3D84BC-F010-4035-A053-76D99901294F@cs.ucl.ac.uk> <4AF05A0F.6040705@isi.edu>
From: Mark Handley <M.Handley@cs.ucl.ac.uk>
Date: Tue, 03 Nov 2009 16:43:43 +0000
X-Google-Sender-Auth: cb9b31cfc5b9114c
Message-ID: <84a612dd0911030843u22f0aa19u6384886afa2342d8@mail.gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] High-level design decisions /architecture
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multipathtcp>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Nov 2009 16:43:47 -0000

2009/11/3 Joe Touch <touch@isi.edu>:
> Costin Raiciu wrote:
>> Hi Joe,
>>
>> The proposed congestion controller gives the aggregate multipath
>> connection the throughput a TCP would get on the best (fastest) of the
>> paths available (to the multipath connection). It does so only by
>> looking at loss rates and rtts on the different paths. It does not need
>> to know whether there is a shared bottleneck or not.
>
> If it doesn't, then you will create the potential for a single multipath
> group to fight with itself, which seems less than productive.

Well, so long as the total window increase per RTT of all the subflows
in a connection is no more than a single vanilla TCP would get, then
you don't fight with yourself any more than one TCP would ("fighting"
in this context is pretty much equivalent to how much unacked traffic
per RTT a flow can inject - the ack-clocked traffic already had its
space last RTT, so isn't "fighting" for extra space).

This is exactly how the proposed congestion control algorithm works
through a common bottleneck.

 - Mark