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

Reinaldo Penno <rpenno@juniper.net> Tue, 25 November 2008 21:23 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 C026D28C1AD; Tue, 25 Nov 2008 13:23:45 -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 8B7B728C1AD for <ledbat@core3.amsl.com>; Tue, 25 Nov 2008 13:23:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.25
X-Spam-Level:
X-Spam-Status: No, score=-6.25 tagged_above=-999 required=5 tests=[AWL=0.349, 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 q7IzsLLeo7Q8 for <ledbat@core3.amsl.com>; Tue, 25 Nov 2008 13:23:43 -0800 (PST)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by core3.amsl.com (Postfix) with ESMTP id DD92128C150 for <ledbat@ietf.org>; Tue, 25 Nov 2008 13:23:39 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKSSxs0EI31uHzjEkirlDvPiH8cieM+cKz@postini.com; Tue, 25 Nov 2008 13:23:41 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.311.2; Tue, 25 Nov 2008 13:20:29 -0800
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 25 Nov 2008 13:20:28 -0800
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 25 Nov 2008 13:20:28 -0800
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with Microsoft SMTPSVC(5.0.2195.6713); Tue, 25 Nov 2008 16:20:26 -0500
Received: from 172.23.1.75 ([172.23.1.75]) by proton.jnpr.net ([10.10.2.37]) with Microsoft Exchange Server HTTP-DAV ; Tue, 25 Nov 2008 21:20:25 +0000
User-Agent: Microsoft-Entourage/12.14.0.081024
Date: Tue, 25 Nov 2008 13:20:13 -0800
From: Reinaldo Penno <rpenno@juniper.net>
To: Michael Welzl <michael.welzl@uibk.ac.at>, ledbat@ietf.org
Message-ID: <C551AC0D.16CB7%rpenno@juniper.net>
Thread-Topic: [ledbat] list of reasons for needing multiple TCP connections
Thread-Index: AclPQ5p87fnHt507kU2Cfc7HIuSJww==
In-Reply-To: <1227515154.3731.48.camel@pc105-c703.uibk.ac.at>
MIME-Version: 1.0
X-OriginalArrivalTime: 25 Nov 2008 21:20:26.0299 (UTC) FILETIME=[A26968B0:01C94F43]
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ledbat-bounces@ietf.org
Errors-To: ledbat-bounces@ietf.org

I will be updating the draft on recommendations based on all the great
references sent and surely a new section on multiple TCP connections and
performance will be added.

Thanks,

Reinaldo


On 11/24/08 12:25 AM, "Michael Welzl" <michael.welzl@uibk.ac.at> wrote:

> Hi,
> 
> On Thu, 2008-11-20 at 14:54 -0800, Caitlin Bestler wrote:
>> Joe Touch wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>> 
>>> Hi, Robb,
>>> 
>>> Appreciating the following, this isn't intended as an application
>>> protocol, so we can't assume it would apply only to P2P. I.e., we need a
>>> solution that can be used for any application, and there are several
>>> applications that DO use multiple connections to increase bandwidth in
>>> the typical case.
>>> 
>> 
>> As a point of reference, part of the justification for doing iSCSI
>> over multiple TCP connections within a session was because "It
>> might be impossible to achieve the full bandwidth capability
>> of the underlying physical transport by using a single TCP
>> connection."
>> 
>> [http://storageconference.org/2003/papers/19-Meth-Design.pdf
>> section 2.2]
>> 
> 
> I'd like to add GridFTP to this, as another example. cf.:
> http://www.globus.org/toolkit/docs/3.2/gridftp/
> 
> which points to:
> http://www.globus.org/alliance/publications/papers/dataMgmt.pdf
> where it says, on page 7:
> 
> "Parallel data transfer: On wide-area links, using multiple TCP streams
> in parallel (even between the same source and destination) can improve
> aggregate bandwidth over using a single TCP stream [10]. GridFTP
> supports parallel data transfer through FTP command extensions and data
> channel extensions."
> 
> Cheers,
> Michael
> 
> 
> _______________________________________________
> ledbat mailing list
> ledbat@ietf.org
> https://www.ietf.org/mailman/listinfo/ledbat

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