All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Paasch <cpaasch at apple.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [MPTCP][PATCH v3 mptcp-next 1/2] mptcp: send out dedicated ADD_ADDR packet
Date: Wed, 30 Sep 2020 18:04:56 -0700	[thread overview]
Message-ID: <20201001010456.GL19948@MacBook-Pro.local> (raw)
In-Reply-To: 27b358e8-cff0-0efa-c0c9-484ce8ad6d00@tessares.net

[-- Attachment #1: Type: text/plain, Size: 1992 bytes --]

On 09/30/20 - 11:31, Matthieu Baerts wrote:
> Hi Christoph, Paolo, Geliang,
> 
> On 29/09/2020 20:07, Christoph Paasch wrote:
> > On 09/29/20 - 11:30, Paolo Abeni wrote:
> > > On Mon, 2020-09-28 at 15:46 +0800, Geliang Tang wrote:
> 
> (...)
> 
> > > > -	/* If the first established packet does not contain MP_CAPABLE
> > > > + data
> > > > +	/* If the first established packet does not contain MP_CAPABLE
> > > > + data or ADD_ADDR
> > > >   	 * then fallback to TCP
> > > >   	 */
> > > > -	if (!mp_opt->mp_capable) {
> > > > +	if (!mp_opt->mp_capable && !mp_opt->add_addr) {
> > > >   		subflow->mp_capable = 0;
> > > >   		pr_fallback(msk);
> > > >   		__mptcp_do_fallback(msk);
> > > 
> > > I think the RFC is a bit unclear with this point, because in
> > > section 3.4.1. says:
> > > 
> > > """
> > > This [ADD_ADDR] option can be used at any time during a connection
> > > """
> > > 
> > > but also says that here we expect a mp_capable + data packet.
> > > 
> > > @Christoph, should we accept ADD_ADDR here or should we reject them?
> > 
> > I think we should accept them. There are 2 things that can happen:
> > 
> > * MP_CAPABLE + data comes later on. In that case we can use the received
> >    addr.
> >    Note, for this to happen I am assuming that the ADD_ADDR comes on an
> >    out-of-order packet and that the MP_CAPABLE will still come on the packet
> >    with relative sequence-number 1.
> 
> If the ADD_ADDR comes on an out-of-order packet and because it is a ACK
> without data, is it not dropped earlier by the TCP stack?
> I think we have this behaviour with mptcp.org version.

No, as far as I can see in mptcp.org we do parse the ADD_ADDR even if we
haven't yet received an MP_CAPABLE with data.

cfr., mptcp_handle_options, called from tcp_validate_incoming, which is
called even on ACKs without data.


Christoph

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

             reply	other threads:[~2020-10-01  1:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01  1:04 Christoph Paasch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-09-30  9:31 [MPTCP] Re: [MPTCP][PATCH v3 mptcp-next 1/2] mptcp: send out dedicated ADD_ADDR packet Matthieu Baerts
2020-09-29 18:07 Christoph Paasch
2020-09-29  9:30 Paolo Abeni

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=20201001010456.GL19948@MacBook-Pro.local \
    --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.