Re: [multipathtcp] Implementers meeting in Hiroshima

Sébastien Barré <sebastien.barre@uclouvain.be> Wed, 04 November 2009 15:35 UTC

Return-Path: <sebastien.barre@uclouvain.be>
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 833DA3A67FD for <multipathtcp@core3.amsl.com>; Wed, 4 Nov 2009 07:35:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 sbnSanP3uici for <multipathtcp@core3.amsl.com>; Wed, 4 Nov 2009 07:35:33 -0800 (PST)
Received: from smtp4.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) by core3.amsl.com (Postfix) with ESMTP id 3F4B33A6358 for <multipathtcp@ietf.org>; Wed, 4 Nov 2009 07:35:33 -0800 (PST)
Received: from [130.104.228.69] (marguerite.dhcp.info.ucl.ac.be [130.104.228.69]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: sbarre@smtp4.sgsi.ucl.ac.be) by smtp4.sgsi.ucl.ac.be (Postfix) with ESMTPSA id A383CF25F1; Wed, 4 Nov 2009 16:35:45 +0100 (CET)
Message-ID: <4AF19F45.70705@uclouvain.be>
Date: Wed, 04 Nov 2009 16:35:33 +0100
From: Sébastien Barré <sebastien.barre@uclouvain.be>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: "multipathtcp@ietf.org Mailing List" <multipathtcp@ietf.org>
References: <C38FBEBA-158B-4618-BCE9-E83C89B1A93D@cs.ucl.ac.uk>
In-Reply-To: <C38FBEBA-158B-4618-BCE9-E83C89B1A93D@cs.ucl.ac.uk>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.95.2 at smtp-4.sipr-dc.ucl.ac.be
X-Virus-Status: Clean
Received-SPF: Pass (sender authenticated); receiver=; client-ip=130.104.228.69; helo=
Received-SPF: Pass (sender authenticated); receiver=; client-ip=130.104.228.69; envelope-from=<sebastien.barre@uclouvain.be>
X-Sgsi-Spamcheck: SASL authenticated,
X-SGSI-MailScanner-ID: A383CF25F1.00000
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: sebastien.barre@uclouvain.be
X-SGSI-Spam-Status: No
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: Wed, 04 Nov 2009 15:35:34 -0000

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