Re: [multipathtcp] Implementers meeting in Hiroshima

Michio Honda <micchie@sfc.wide.ad.jp> Fri, 06 November 2009 08:11 UTC

Return-Path: <micchie@sfc.wide.ad.jp>
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 108103A6B8A for <multipathtcp@core3.amsl.com>; Fri, 6 Nov 2009 00:11:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.905
X-Spam-Level:
X-Spam-Status: No, score=0.905 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, RELAY_IS_203=0.994]
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 9-qWMRQNzYsa for <multipathtcp@core3.amsl.com>; Fri, 6 Nov 2009 00:11:14 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [203.178.142.146]) by core3.amsl.com (Postfix) with ESMTP id 7D8AD3A6A1F for <multipathtcp@ietf.org>; Fri, 6 Nov 2009 00:11:14 -0800 (PST)
Received: from net72-dhcp1556.sfc.keio.ac.jp (net72-dhcp1556.sfc.keio.ac.jp [133.27.78.30]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id D2A194C09A for <multipathtcp@ietf.org>; Fri, 6 Nov 2009 17:11:32 +0900 (JST)
From: Michio Honda <micchie@sfc.wide.ad.jp>
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: multipart/alternative; boundary="Apple-Mail-1-15018486"
Date: Fri, 06 Nov 2009 17:11:32 +0900
In-Reply-To: <51eafbcb0911040813k4995d938v2add8d49dd12199a@mail.gmail.com>
To: "multipathtcp@ietf.org Mailing List" <multipathtcp@ietf.org>
References: <C38FBEBA-158B-4618-BCE9-E83C89B1A93D@cs.ucl.ac.uk> <4AF19F45.70705@uclouvain.be> <51eafbcb0911040813k4995d938v2add8d49dd12199a@mail.gmail.com>
Message-Id: <1AEC9376-EBED-4D12-8F3B-EBA90D948F99@sfc.wide.ad.jp>
X-Mailer: Apple Mail (2.1076)
Subject: Re: [multipathtcp] Implementers meeting in Hiroshima
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: Fri, 06 Nov 2009 08:11:16 -0000

Hi,

Wednesday afternoon is also fine for me.

Best regards
-Michio

On Nov 5, 2009, at 1:13 , Daniel Migault wrote:

> I would be interested to attempt this meeting since we are working  
> on IPsec and multihoming issues. --i.e. interactions with IKEv2.
>
> Wednesday afternoon after dnsop would be nice for me.
>
> Regards,
>
> Daniel
> 2009/11/4 Sébastien Barré <sebastien.barre@uclouvain.be>
> Hi,
>
> Regarding the second implementation, I will setup a trac platform  
> for that project, so that people can easily contribute, and I will  
> make a first release so that people can easily install for playing.
> I will send another mail as soon as the trac repository is set up,  
> probably by the end of next week. The code is currently using the  
> git scm software, and the git tree will be connected to the trac  
> platform. Unfortunately I will not be able to attend that meeting,  
> but Costin knows well about this implementation.
>
> regards,
>
> Sébastien.
>
> Costin Raiciu a écrit :
>
> Hi,
>
> We plan to have an mptcp implementers meeting in Hiroshima, with the  
> purpose to coordinate efforts and share knowledge on implementing  
> mptcp. A few people have expressed interest in helping implementing  
> MPTCP. If you still want to help, this is a good time to start.  
> Please reply stating preferences for days and times. Anything except  
> monday afternoon works for me.
>
> I am currently aware of three implementations of mptcp in:
> - userland (based on an older Linux kernel, ported to userland) - by  
> me. It implements a subset of the spec, and works on v4.
> - kernel 2.6, by Sebastien Barre, that works over ipv6 and uses  
> shim6 as a way to provide multiple paths. Soon this is will changed  
> to support v4 and address exchange through options, as defined in  
> the protocol draft.
> - kernel 2.6 by Michio Honda. As far as I know this is incomplete,  
> and doesn't run at all.
>
> Any others?
>
> The second implementation (kernel 2.6) has been coded using the  
> userland experience, so it is more polished, and could be used as a  
> good starting point for a reference implementation.
>
> I will come back with date and time proposals once enough people  
> reply.
>
> Thanks,
> Costin
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp
>
> -- 
> Sébastien Barré
> Researcher,
> CSE department, UCLouvain, Belgium
> http://inl.info.ucl.ac.be/sbarre
>
>
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp
>
>
>
> -- 
> Daniel Migault
> Orange Labs -- Security
> +33 6 70 72 69 58
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp