From: Mat Martineau <mathew.j.martineau at linux.intel.com>
To: mptcp at lists.01.org
Subject: Re: [MPTCP] MPTCP Upstreaming wiki
Date: Mon, 23 Apr 2018 14:53:55 -0700 [thread overview]
Message-ID: <alpine.OSX.2.21.1804231446530.4969@mjmartin-mac01.sea.intel.com> (raw)
In-Reply-To: f4ba293a-8cd4-8996-4400-579de2e46532@oracle.com
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
On Mon, 23 Apr 2018, Rao Shoaib wrote:
>
>
> On 04/20/2018 05:17 PM, Mat Martineau wrote:
>>
>> Hello -
>>
>> I've set up a wiki for our project:
>>
>> https://github.com/multipath-tcp/mptcp_net-next/wiki
>>
>> To start with I've added some information that was otherwise buried in our
>> mailing list archives. This includes a summary of what the community has
>> shared so far, meeting information, and pointers to relevant resources.
>>
> Hi Mat,
>
> Why is the following a requirement for the initial implementation
>
> "Move away from meta-sockets, treating each subflow more like a regular TCP
> connection. The overall MPTCP connection is coordinated by an upper layer
> socket that is distinct from tcp_sock."
>
> This can be done later.
Hi Rao,
The idea is to make the MPTCP changes less invasive to TCP by isolating
the socket-level changes in separate MPTCP-specific socket code. I think
"less invasive to TCP" is an important goal from the start.
--
Mat Martineau
Intel OTC
next reply other threads:[~2018-04-23 21:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 21:53 Mat Martineau [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-25 16:20 [MPTCP] MPTCP Upstreaming wiki Rao Shoaib
2018-04-24 21:51 Mat Martineau
2018-04-23 20:11 Rao Shoaib
2018-04-23 7:25 Matthieu Baerts
2018-04-21 0:17 Mat Martineau
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=alpine.OSX.2.21.1804231446530.4969@mjmartin-mac01.sea.intel.com \
--to=unknown@example.com \
/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.