From: Florian Westphal <fw@strlen.de>
To: Paul Moore <paul@paul-moore.com>
Cc: Mat Martineau <mathew.j.martineau@linux.intel.com>,
Stephen Smalley <stephen.smalley.work@gmail.com>,
selinux@vger.kernel.org, mptcp@lists.01.org,
linux-security-module@vger.kernel.org
Subject: Re: [MPTCP] Re: [RFC PATCH] selinux: handle MPTCP consistently with TCP
Date: Fri, 4 Dec 2020 00:54:15 +0100 [thread overview]
Message-ID: <20201203235415.GD5710@breakpoint.cc> (raw)
In-Reply-To: <CAHC9VhTVc07P_MhWm7YRF6LXdMRQOcDEKe7SB+fpJJizdKOvEg@mail.gmail.com>
Paul Moore <paul@paul-moore.com> wrote:
> I'm not very well versed in MPTCP, but this *seems* okay to me, minus
> the else-crud chunk. Just to confirm my understanding, while MPTCP
> allows one TCP connection/stream to be subdivided and distributed
> across multiple interfaces, it does not allow multiple TCP streams to
> be multiplexed on a single connection, yes?
Its the latter. The application sees a TCP interface (socket), but
data may be carried over multiple individual tcp streams on the wire.
next prev parent reply other threads:[~2020-12-03 23:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 10:31 [RFC PATCH] selinux: handle MPTCP consistently with TCP Paolo Abeni
2020-12-02 11:17 ` [MPTCP] " Paolo Abeni
2020-12-03 17:24 ` [MPTCP] " Mat Martineau
2020-12-03 23:30 ` Paul Moore
2020-12-03 23:54 ` Florian Westphal [this message]
2020-12-04 2:24 ` Paul Moore
2020-12-04 10:04 ` Paolo Abeni
2020-12-04 23:22 ` Paul Moore
2020-12-08 15:35 ` Paolo Abeni
2020-12-08 23:35 ` Paul Moore
2020-12-09 10:02 ` Paolo Abeni
2020-12-10 2:43 ` Paul Moore
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=20201203235415.GD5710@breakpoint.cc \
--to=fw@strlen.de \
--cc=linux-security-module@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=mptcp@lists.01.org \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).