All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts at tessares.net>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH net-next v3] mptcp: fix length of MP_PRIO suboption
Date: Fri, 29 Jan 2021 18:08:22 +0100	[thread overview]
Message-ID: <2db70998-7504-c244-9feb-0abe3055918e@tessares.net> (raw)
In-Reply-To: 07135f8a644672e1847788341e39f6dd25b1c32c.1611852408.git.dcaratti@redhat.com

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

Hi Davide, Mat,

On 28/01/2021 18:34, Davide Caratti wrote:
> With version 0 of the protocol it was legal to encode the 'Subflow Id' in
> the MP_PRIO suboption, to specify which subflow would change its 'Backup'
> flag. This has been removed from v1 specification: thus, according to RFC
> 8684 §3.3.8, the resulting 'Length' for MP_PRIO changed from 4 to 3 byte.
> 
> Current Linux generates / parses MP_PRIO according to the old spec, using
> 'Length' equal to 4, and hardcoding 1 as 'Subflow Id'; RFC compliance can
> improve if we change 'Length' in other to become 3, leaving a 'Nop' after
> the MP_PRIO suboption. In this way the kernel will emit and accept *only*
> MP_PRIO suboptions that are compliant to version 1 of the MPTCP protocol.

Thank you for this new version!

Just added in our tree, at the bottom, with Mat and my RvB tag.

- 91384be37ad9 mptcp: fix length of MP_PRIO suboption

Tests + export have been almost a success! Simult Flow selftest with a 
debug kernel was unstable but it is not new, see:

   https://github.com/multipath-tcp/mptcp_net-next/issues/137

So feel free to send this patch to netdev when you have the opportunity  ;-)
It doesn't conflict with other pending patches from Geliang that have 
been recently sent by Mat.

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

             reply	other threads:[~2021-01-29 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29 17:08 Matthieu Baerts [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-02-01 10:23 [MPTCP] Re: [PATCH net-next v3] mptcp: fix length of MP_PRIO suboption Davide Caratti
2021-01-28 23:37 Mat Martineau

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=2db70998-7504-c244-9feb-0abe3055918e@tessares.net \
    --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.