All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Jianguo Wu <wujianguo106@163.com>, Geliang Tang <geliangtang@gmail.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH] mptcp: create listening socket only if signal flag is set on
Date: Fri, 23 Apr 2021 16:02:50 +0200	[thread overview]
Message-ID: <f222b5b1-a2a9-5d10-ef22-5db67940daa3@tessares.net> (raw)
In-Reply-To: <4b4f4935-138d-a6fc-dfdc-3ef059a33c3e@163.com>

Hi Jianguo,

On 23/04/2021 10:38, Jianguo Wu wrote:
> On 2021/4/23 16:21, Matthieu Baerts wrote:
>> On 23/04/2021 09:41, Jianguo Wu wrote:
>>> I think this is better, we can't assume that all user-space tools works correctly.
>>
>> I was thinking a bit about that. With the proposed modifications, it
>> means that a server will have to send an ADD_ADDR if it wants to accept
>> subflows on another port. I guess there will be use-cases where we will
>> not want to send ADD_ADDR because we are in a controlled environment or
>> we don't want to announce a public ADD_ADDR+port on a specific network.
>>
> 
> Hi Matt, do you mean there will be use-cases where using ADD_ADDR+port as local address to initiate
> a outgoing subflow join, but not send ADD_ADDR?

That would definitively not be a common use-case but we will see if some
people are interested by that.

Anyhow, I think it is better to start by well covering requested
use-cases and avoid "strange" behaviours, e.g. not announcing the
address but doing bind.

Cheers,
Matt
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net

  reply	other threads:[~2021-04-23 14:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 10:30 [PATCH] mptcp: create listening socket only if signal flag is set on Jianguo Wu
2021-04-23  4:33 ` Geliang Tang
2021-04-23  6:38   ` Jianguo Wu
2021-04-23  7:17     ` Geliang Tang
2021-04-23  7:27       ` Geliang Tang
2021-04-23  7:41         ` Jianguo Wu
2021-04-23  7:47           ` Geliang Tang
2021-04-23  8:08             ` Jianguo Wu
2021-04-23  8:21           ` Matthieu Baerts
2021-04-23  8:38             ` Jianguo Wu
2021-04-23 14:02               ` Matthieu Baerts [this message]
2021-04-23  8:59             ` Geliang Tang
2021-04-23 14:04               ` Matthieu Baerts
2021-04-23  7:28       ` Jianguo Wu

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=f222b5b1-a2a9-5d10-ef22-5db67940daa3@tessares.net \
    --to=matthieu.baerts@tessares.net \
    --cc=geliangtang@gmail.com \
    --cc=mptcp@lists.linux.dev \
    --cc=wujianguo106@163.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.