From: Hagen Paul Pfeifer <hagen@jauu.net>
To: christoph.paasch@uclouvain.be
Cc: netdev@vger.kernel.org, bonding-devel@lists.sourceforge.net,
linux-sctp@vger.kernel.org
Subject: Re: MultiPath TCP in the Linux Kernel
Date: Thu, 20 Jan 2011 15:38:25 +0000 [thread overview]
Message-ID: <7e28a5ddc16848dcd98c05351113304f@localhost> (raw)
In-Reply-To: <201101201509.34536.christoph.paasch@uclouvain.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
WARNING: multiple messages have this Message-ID (diff)
From: Hagen Paul Pfeifer <hagen@jauu.net>
To: <christoph.paasch@uclouvain.be>
Cc: <netdev@vger.kernel.org>, <bonding-devel@lists.sourceforge.net>,
<linux-sctp@vger.kernel.org>
Subject: Re: MultiPath TCP in the Linux Kernel
Date: Thu, 20 Jan 2011 16:38:25 +0100 [thread overview]
Message-ID: <7e28a5ddc16848dcd98c05351113304f@localhost> (raw)
In-Reply-To: <201101201509.34536.christoph.paasch@uclouvain.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
next prev parent reply other threads:[~2011-01-20 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 14:09 MultiPath TCP in the Linux Kernel Christoph Paasch
2011-01-20 14:09 ` Christoph Paasch
[not found] ` <AANLkTinkqCjQqRKDFnxTF4-uF27XyPzh0gY-vX3fnfSo@mail.gmail.com>
2011-01-20 15:11 ` Christoph Paasch
2011-01-20 15:11 ` Christoph Paasch
[not found] ` <AANLkTi=v7jJzfRoeQLGzwU29p2dVqJqd=Eap_8ntfxKP@mail.gmail.com>
2011-01-21 13:19 ` Christoph Paasch
2011-01-21 13:19 ` Christoph Paasch
2011-01-20 15:38 ` Hagen Paul Pfeifer [this message]
2011-01-20 15:38 ` Hagen Paul Pfeifer
2011-01-20 15:42 ` Eric Dumazet
2011-01-20 15:42 ` Eric Dumazet
2011-01-21 13:26 ` Christoph Paasch
2011-01-21 13:26 ` Christoph Paasch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7e28a5ddc16848dcd98c05351113304f@localhost \
--to=hagen@jauu.net \
--cc=bonding-devel@lists.sourceforge.net \
--cc=christoph.paasch@uclouvain.be \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.