Re: [multipathtcp] High-level design decisions /architecture
Scott Brim <scott.brim@gmail.com> Thu, 05 November 2009 04:05 UTC
Return-Path: <scott.brim@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 E28B43A684A for <multipathtcp@core3.amsl.com>; Wed, 4 Nov 2009 20:05:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level:
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599]
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 yGpgatYgsRww for <multipathtcp@core3.amsl.com>; Wed, 4 Nov 2009 20:05:35 -0800 (PST)
Received: from mail-gx0-f228.google.com (mail-gx0-f228.google.com [209.85.217.228]) by core3.amsl.com (Postfix) with ESMTP id 1B42C3A67E6 for <multipathtcp@ietf.org>; Wed, 4 Nov 2009 20:05:35 -0800 (PST)
Received: by gxk28 with SMTP id 28so1617170gxk.9 for <multipathtcp@ietf.org>; Wed, 04 Nov 2009 20:05:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=y4nDHA6g4J7ethkdMOkjJjk2uCcniZN2K3VC2SW5zP4=; b=IJmCTC7N8TGHpIWjxao12BhA0GQ92uqGAD33a8wlVWjycqtoOyWfM6AwJ5/EIUPYgg 7uQgTxlnJdFYJQZ6qxte/+QMjSnZWaBBQab05gG0DFSH1GAISnP7YGtrBStZD1K1YSNY IrMdONyKtNIZsWIw0ZvIBLSapDsgzFD8EEE14=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=a/F5unmelOE3ZMMBN3FbSlYB2gnSVujxIrIhoQ6i+AIN7TtTHMz8j8Uy+7X49zBHIO 8260Zei4Z5A/+vL4+rwvVEYQpLHgIL9UNbBPhTLFsCPQBoZFGYi5DbwLzkVnpnZAiQV8 +RN4aiy43r7RIFgqX07Vx8B9u06KbP8d9+bxw=
Received: by 10.150.24.2 with SMTP id 2mr4235377ybx.172.1257393952190; Wed, 04 Nov 2009 20:05:52 -0800 (PST)
Received: from 12-187-221-19.att-inc.com (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id 9sm630047ywe.26.2009.11.04.20.05.48 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 04 Nov 2009 20:05:50 -0800 (PST)
Message-ID: <4AF24F1B.1010506@gmail.com>
Date: Wed, 04 Nov 2009 20:05:47 -0800
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
References: <20091104.195734.88191535.nishida@sfc.wide.ad.jp> <3B0898A2-0F7E-4128-B789-AC54A5D64B56@cs.ucl.ac.uk> <93D4E6CB-455F-4A4E-B8B3-2A0BDC2E2903@nokia.com> <20091105.051958.02289937.nishida@sfc.wide.ad.jp>
In-Reply-To: <20091105.051958.02289937.nishida@sfc.wide.ad.jp>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: 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: Thu, 05 Nov 2009 04:05:36 -0000
Yoshifumi Nishida allegedly wrote on 11/04/2009 12:19 PM: > > With per-subflow receive windows, you can use receive window tuning, > > too. > > Well, that's an idea. Yes, I agree. > I tend to agree that this can be a open issue now. But, I still have a naive question... > > Compared to having a tweaky algorithm at receiver side, doing simple > negotiation during SYN exchange would be that difficult? (and probably we will > also need to use 1 bit in Add Address option to specify primary path or etc, > but it's still simple.) > If we think about a small gudget like iphone, I guess simple receiving > algorithm might be preferable. The problem with putting this in signaling is that you lose richness of what you can do. You need to have a few standard meanings for the bits (or bit values) available to you, and so on. Also, the particular effect sought here is throttling traffic, which is exactly what receive windows are good for. If there is a need for anything else, maybe signaling would be more appropriate. Scott
- [multipathtcp] High-level design decisions /archi… philip.eardley
- Re: [multipathtcp] High-level design decisions /a… marcelo bagnulo braun
- Re: [multipathtcp] High-level design decisions /a… William Herrin
- Re: [multipathtcp] High-level design decisions /a… marcelo bagnulo braun
- Re: [multipathtcp] High-level design decisions /a… William Herrin
- Re: [multipathtcp] High-level design decisions /a… Joe Touch
- Re: [multipathtcp] High-level design decisions /a… Joe Touch
- Re: [multipathtcp] High-level design decisions /a… Mark Handley
- Re: [multipathtcp] High-level design decisions /a… Joe Touch
- Re: [multipathtcp] High-level design decisions /a… Lars Eggert
- Re: [multipathtcp] High-level design decisions /a… Yoshifumi Nishida
- [multipathtcp] This shim6 part of the answer (was… marcelo bagnulo braun
- [multipathtcp] The MPTCP part (was Re: High-level… marcelo bagnulo braun
- Re: [multipathtcp] High-level design decisions /a… marcelo bagnulo braun
- Re: [multipathtcp] High-level design decisions /a… Scott Brim
- Re: [multipathtcp] High-level design decisions /a… Scott Brim
- Re: [multipathtcp] High-level design decisions /a… Scott Brim
- Re: [multipathtcp] High-level design decisions /a… Joe Touch
- Re: [multipathtcp] High-level design decisions /a… Joe Touch
- Re: [multipathtcp] High-level design decisions /a… Joe Touch
- Re: [multipathtcp] High-level design decisions /a… Costin Raiciu
- Re: [multipathtcp] High-level design decisions /a… Joe Touch
- Re: [multipathtcp] High-level design decisions /a… Mark Handley
- Re: [multipathtcp] High-level design decisions /a… Costin Raiciu
- Re: [multipathtcp] High-level design decisions /a… Costin Raiciu
- Re: [multipathtcp] High-level design decisions /a… Ford, Alan
- Re: [multipathtcp] High-level design decisions /a… Ford, Alan
- Re: [multipathtcp] High-level design decisions /a… Ford, Alan
- Re: [multipathtcp] High-level design decisions /a… Scott Brim
- Re: [multipathtcp] High-level design decisions /a… marcelo bagnulo braun
- Re: [multipathtcp] High-level design decisions /a… William Herrin
- Re: [multipathtcp] High-level design decisions /a… Joe Touch
- Re: [multipathtcp] High-level design decisions /a… Joe Touch
- Re: [multipathtcp] High-level design decisions /a… Yoshifumi Nishida
- Re: [multipathtcp] High-level design decisions /a… Joe Touch
- Re: [multipathtcp] High-level design decisions /a… Joe Touch
- Re: [multipathtcp] High-level design decisions /a… Joe Touch
- Re: [multipathtcp] High-level design decisions /a… Mark Handley
- Re: [multipathtcp] High-level design decisions /a… Ford, Alan
- Re: [multipathtcp] High-level design decisions /a… Ford, Alan
- Re: [multipathtcp] High-level design decisions /a… Yoshifumi Nishida
- Re: [multipathtcp] High-level design decisions /a… Costin Raiciu
- Re: [multipathtcp] High-level design decisions /a… philip.eardley
- Re: [multipathtcp] High-level design decisions /a… Lars Eggert
- Re: [multipathtcp] High-level design decisions /a… William Herrin
- Re: [multipathtcp] High-level design decisions /a… Yoshifumi Nishida
- Re: [multipathtcp] High-level design decisions /a… Scott Brim
- Re: [multipathtcp] High-level design decisions /a… Costin Raiciu
- Re: [multipathtcp] High-level design decisions /a… Yoshifumi Nishida
- Re: [multipathtcp] High-level design decisions /a… Joe Touch
- Re: [multipathtcp] High-level design decisions /a… William Herrin
- Re: [multipathtcp] High-level design decisions /a… Joe Touch
- Re: [multipathtcp] High-level design decisions /a… William Herrin
- Re: [multipathtcp] High-level design decisions /a… Joe Touch
- Re: [multipathtcp] High-level design decisions /a… William Herrin
- Re: [multipathtcp] High-level design decisions /a… Joe Touch