IETF Logo Mail Archive

Re: [multipathtcp] Draft Multipath TCP (MPTCP) BOF description

Pasi Sarolahti <pasi.sarolahti@nokia.com> Mon, 11 May 2009 08:23 UTC

Return-Path: <Pasi.Sarolahti@nokia.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 50F533A6B79 for <multipathtcp@core3.amsl.com>; Mon, 11 May 2009 01:23:23 -0700 (PDT)
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=[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 l74BKLCp2sv8 for <multipathtcp@core3.amsl.com>; Mon, 11 May 2009 01:23:22 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 3B3E23A68C5 for <multipathtcp@ietf.org>; Mon, 11 May 2009 01:23:22 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n4B8OBKi006723; Mon, 11 May 2009 11:24:44 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 11 May 2009 11:24:33 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 11 May 2009 11:24:32 +0300
Received: from [172.21.30.100] ([172.21.30.100]) by vaebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 11 May 2009 11:24:28 +0300
In-Reply-To: <4A051E47.7090400@fandm.edu>
References: <4A031B0F.4030606@employees.org> <4A031E1E.5050900@it.uc3m.es><20090507211619.GA35382@cisco.com><5E59C0C6-4A97-4253-954D-05139E1F684C@muada.com><4A03635F.4010107@it.uc3m.es> <4A02FC62.8080503@it.uc3m.es><4A031B0F.4030606@employees.org> <4A031E1E.5050900@it.uc3m.es><20090507211619.GA35382@cisco.com><5E59C0C6-4A97-4253-954D-05139E1F684C@muada.com><20090507230452.GC35382@cisco.com><C52F3179-6C29-4865-8623-84F4685CC6D6@mpi-sws.org><CF91F6E8-6ADB-4BE7-A2C0-526983319FB6@muada.com><1241789497.4055.8.camel@nhuynhth-laptop> <EEAB7ADD-056C-4C04-AC18-E2D2C00D025D@muada.com> <001e01c9cfff$bde8f1e0$103947ab@cisco.com> <97963A5D-FD5D-4D08-99F6-12455BB90FE4@muada.com> <001f01c9d005$0c583110$103947ab@cisco.com> <E9DE886C-6289-4603-A00B-D4178BBF012A@muada.com> <000001c9d028$aea92640$103947ab@cisco.com> <4A051E47.7090400@fandm.edu>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <2AEF47F0-83EC-4BD9-84B8-C700F663C495@nokia.com>
Content-Transfer-Encoding: 7bit
From: Pasi Sarolahti <pasi.sarolahti@nokia.com>
Date: Mon, 11 May 2009 11:24:22 +0300
To: "janardhan.iyengar@fandm.edu" <janardhan.iyengar@fandm.edu>
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 11 May 2009 08:24:28.0237 (UTC) FILETIME=[E6A12FD0:01C9D211]
X-Nokia-AV: Clean
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] Draft Multipath TCP (MPTCP) BOF description
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: Mon, 11 May 2009 08:23:23 -0000

On May 9, 2009, at 9:10, ext Janardhan Iyengar wrote:

> A couple of thoughts on the draft/BoF:
>
> 1/ "Two-ended" multipath, where both endpoints are aware:  There  
> are several architectural and design considerations that will be  
> common to TCP, SCTP, DCCP, SST etc., and as I see it, there is no  
> reason why this discussion should not include all transports.

This might be a sensible idea: there is an expired draft on multipath/ 
mobile DCCP (draft-kohler-dccp-mobility-02) that is a bit similar to  
the multipath TCP variant with implicit address management.

- Pasi

v2.23.0 | Report a Bug | By Email