MultiPath TCP in the Linux Kernel

Hi all,

The IETF is developing a new transport layer solution, MultiPath TCP, which 
allows to efficiently exploit several Internet paths between a pair of hosts, 
while presenting a single TCP connection to the application layer.

At the UCLouvain in Belgium we are developping the support for MultiPath TCP 
in the Linux Kernel. The implementation is a major extension to the Linux TCP-
stack.

For general information, access:
http://inl.info.ucl.ac.be/mptcp
https://scm.info.ucl.ac.be/trac/mptcp/

To access the git-repository:
git://scm.info.ucl.ac.be/mtcp.git
branches:
	mptcp_2.6.36 - based on Linux Kernel 2.6.36
	mtcp_no_subrcvqueue - based on Linux Kernel 2.6.28

For questions, feedback,... feel free to subscribe to the mptcp-dev Mailing-
List:
https://listes-2.sipr.ucl.ac.be/sympa/info/mptcp-dev


Regards,
Christoph

--
Christoph Paasch
PhD Student

IP Networking Lab --- http://inl.info.ucl.ac.be
MultiPath TCP in the Linux Kernel --- http://inl.info.ucl.ac.be/mptcp
Université Catholique de Louvain

www.rollerbulls.be
--

On Thu, 20 Jan 2011 15:09:34 +0100, Christoph Paasch wrote:

Hi all,

The IETF is developing a new transport layer solution, MultiPath TCP,

which 

allows to efficiently exploit several Internet paths between a pair of

hosts, 

while presenting a single TCP connection to the application layer.

At the UCLouvain in Belgium we are developping the support for MultiPath

TCP 

in the Linux Kernel. The implementation is a major extension to the

Linux

TCP-

stack.

Hello Christoph,



if you want that your work becomes part of the official network stack you

should align your effort on the official Linux way. This means you should

split your work and publish patches on this maillinglist.



Cheers, Hagen

Le jeudi 20 janvier 2011 à 16:38 +0100, Hagen Paul Pfeifer a écrit :

Hello Christoph,

if you want that your work becomes part of the official network stack you
should align your effort on the official Linux way. This means you should
split your work and publish patches on this maillinglist.

Hmm, they probably know that, and prefer to wait MTCP stuff is mature
before patch submission :)

On Thursday, January 20, 2011 wrote Eric Dumazet:

quoted

if you want that your work becomes part of the official network stack you
should align your effort on the official Linux way. This means you should
split your work and publish patches on this maillinglist.

Hmm, they probably know that, and prefer to wait MTCP stuff is mature
before patch submission :)

Exactly... :)

The protocol specification of MPTCP is not stable yet 
(http://datatracker.ietf.org/doc/draft-ietf-mptcp-multiaddressed/).

Also, all the features are not yet in our implementation (e.g., IPv6-support 
and dual IPv4/IPv6-support), and it is necessary to make our implementation 
less intrusive to the regular TCP/IP-stack.

However, as developper-resources are limited this will still take quite some 
time... ;)

Cheers,
Christoph


--
Christoph Paasch
PhD Student

IP Networking Lab --- http://inl.info.ucl.ac.be
MultiPath TCP in the Linux Kernel --- http://inl.info.ucl.ac.be/mptcp
Université Catholique de Louvain

www.rollerbulls.be
--