From: Mat Martineau <mathew.j.martineau at linux.intel.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Design ideas for MPTCP metadata queuing
Date: Fri, 03 Aug 2018 10:43:45 -0700 [thread overview]
Message-ID: <alpine.OSX.2.21.1808031036550.13723@bjaszczy-mobl.amr.corp.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
Hello -
We've been discussing ideas for handling MPTCP metadata (DSS mappings,
ADD_ADDR, REMOVE_ADDR, etc) with a manageable amount of impact on the TCP
stack and networking subsystem.
I've written up some design proposals on our wiki:
https://github.com/multipath-tcp/mptcp_net-next/wiki/Design
(see the "Metadata queuing" section).
I'd appreciate any comments and feedback.
Thanks,
--
Mat Martineau
Intel OTC
reply other threads:[~2018-08-03 17:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1808031036550.13723@bjaszczy-mobl.amr.corp.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.