Re: [tcpm] WG status update
"Scheffenegger, Richard" <rs@netapp.com> Wed, 10 November 2010 12:50 UTC
Return-Path: <rs@netapp.com>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D7563A6407 for <tcpm@core3.amsl.com>; Wed, 10 Nov 2010 04:50:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.449
X-Spam-Level:
X-Spam-Status: No, score=-10.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 9nzZYzEeww7P for <tcpm@core3.amsl.com>; Wed, 10 Nov 2010 04:50:39 -0800 (PST)
Received: from mx4.netapp.com (mx4.netapp.com [217.70.210.8]) by core3.amsl.com (Postfix) with ESMTP id F332D3A677D for <tcpm@ietf.org>; Wed, 10 Nov 2010 04:50:38 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.59,177,1288594800"; d="scan'208";a="225588677"
Received: from smtp3.europe.netapp.com ([10.64.2.67]) by mx4-out.netapp.com with ESMTP; 10 Nov 2010 04:51:05 -0800
Received: from ldcrsexc2-prd.hq.netapp.com (webmail.europe.netapp.com [10.65.251.110]) by smtp3.europe.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id oAACp4GP008500; Wed, 10 Nov 2010 04:51:04 -0800 (PST)
Received: from LDCMVEXC1-PRD.hq.netapp.com ([10.65.251.108]) by ldcrsexc2-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 10 Nov 2010 12:51:04 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 10 Nov 2010 12:51:01 -0000
Message-ID: <5FDC413D5FA246468C200652D63E627A0B54DF91@LDCMVEXC1-PRD.hq.netapp.com>
In-Reply-To: <4CDA4FA9.4050006@alcatel-lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [tcpm] WG status update
Thread-Index: AcuArJQDlJswgExrQymw/Iie15u40wAKCH1w
References: <C304DB494AC0C04C87C6A6E2FF5603DB4821F155C3@NDJSSCC01.ndc.nasa.gov> <4CDA4FA9.4050006@alcatel-lucent.com>
From: "Scheffenegger, Richard" <rs@netapp.com>
To: Bruno Mongazon-Cazavet <bruno.mongazon-cazavet@alcatel-lucent.com>, "Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]" <wesley.m.eddy@nasa.gov>
X-OriginalArrivalTime: 10 Nov 2010 12:51:04.0874 (UTC) FILETIME=[EFBD48A0:01CB80D5]
Cc: tcpm@ietf.org
Subject: Re: [tcpm] WG status update
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Nov 2010 12:50:40 -0000
Hi Bruno, After a casual look, it appears to me that a lightweight implementation of MP-TCP can have the same benefits, but does not require the opaque exchange of IPv4 addresses... Your use case - that the old L3 address is already no longer available at the time of the rehash - may need to be looked at in MPTCP though (iirc, they do a graceful session setup first (thus can work with NAT mostly), and move data transport only after the successful establishment of the 2nd L3 connectivity, and only then tear down the original L3 connectivity). Perhaps the effort would be better placed on making sure that such light-weight MPTCP implementations remain feasible, instead of defining an alternate method that is addressing only this one aspect, but incompatible with MPTCP otherwise? Richard Scheffenegger > -----Original Message----- > From: Bruno Mongazon-Cazavet > [mailto:bruno.mongazon-cazavet@alcatel-lucent.com] > Sent: Mittwoch, 10. November 2010 08:54 > To: Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP] > Cc: tcpm@ietf.org > Subject: Re: [tcpm] WG status update > > > Le 10/11/2010 01:54, Eddy, Wesley M. (GRC-MS00)[ASRC > AEROSPACE CORP] a écrit : > > Hi, for those of you who aren't in Beijing, here's a > snapshot of the TCPM WG status. > > Hi, > > I have posted a 00 draft that might be of interest for your working > group. I don't see any mention in your snapshot. > http://www.ietf.org/id/draft-mongazon-tcpm-tcp-rehash-00.txt > > I will not be in Beijing to present it but i hope to be in > Prague to do so. > I would appreciate the working group can look at it and let > me know if > it could be of any interest and how i shall pursue my contribution. > > I have done a Linux kernel implementation of the draft and be > ready for > a demo in Prague. > > Best Regards, > Bruno. > _______________________________________________ > tcpm mailing list > tcpm@ietf.org > https://www.ietf.org/mailman/listinfo/tcpm >
- [tcpm] WG status update Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]
- Re: [tcpm] WG status update Mark Allman
- Re: [tcpm] WG status update Fernando Gont
- [tcpm] WG status update Eddy, Wesley M. (GRC-MS00)[Verizon]
- Re: [tcpm] WG status update Alexander Zimmermann
- [tcpm] WG status update Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]
- Re: [tcpm] WG status update Bruno Mongazon-Cazavet
- Re: [tcpm] WG status update Scheffenegger, Richard
- Re: [tcpm] WG status update Scheffenegger, Richard
- Re: [tcpm] WG status update Lars Eggert
- Re: [tcpm] WG status update Murari Sridharan
- Re: [tcpm] WG status update Bruno Mongazon-Cazavet
- Re: [tcpm] WG status update Lars Eggert
- Re: [tcpm] WG status update Bruno Mongazon-Cazavet
- Re: [tcpm] WG status update Lars Eggert
- Re: [tcpm] WG status update L.Wood
- [tcpm] MPTCP vs Rehash (was TCPM WG status update) Costin Raiciu
- Re: [tcpm] MPTCP vs Rehash (was TCPM WG status up… Bruno Mongazon-Cazavet
- Re: [tcpm] WG status update Lars Eggert
- Re: [tcpm] WG status update Joe Touch
- Re: [tcpm] WG status update Bruno Mongazon-Cazavet