From: Othman, Ossama <ossama.othman at intel.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: force existing service to use MPTCP
Date: Fri, 04 Dec 2020 19:32:58 +0000 [thread overview]
Message-ID: <ee14d6511a79435ca04752f22524ee6f@intel.com> (raw)
In-Reply-To: d3a06454529b77757dc27b7157b3f55fee8f25b3.camel@redhat.com
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
Hi Paolo,
> Bottom line:
> - the above looks tecnically viable [at least for some services]. I'm
> looking for a more extended service/daemon list to investigate
> fourther. I think we could/should really consider package the above in
> mptcpd or the like.
That's fine. Mptcpd is licensed under BSD-3-Clause. Would we able to apply the same license to the proposed additions?
Thanks!
-Ossama
reply other threads:[~2020-12-04 19:32 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=ee14d6511a79435ca04752f22524ee6f@intel.com \
--to=mptcp@lists.linux.dev \
/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