diff options
| author |   Matthieu Baerts <matthieu.baerts@tessares.net> | 2022-02-02 17:03:39 -0800 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2022-02-03 11:44:08 +0000 |
| commit | 8cca39e251718baec13a5999bf3d18c05af865be (patch) | |
| tree | db6fa9c3cd5d4cb98d49d712fce44eb64aea77d8 /net/smc | |
| parent | mptcp: reduce branching when writing MP_FAIL option (diff) | |
| download | linux-dev-8cca39e251718baec13a5999bf3d18c05af865be.tar.xz linux-dev-8cca39e251718baec13a5999bf3d18c05af865be.zip | |
mptcp: clarify when options can be used
RFC8684 doesn't seem to clearly specify which MPTCP options can be used
together.
Some options are mutually exclusive -- e.g. MP_CAPABLE and MP_JOIN --,
some can be used together -- e.g. DSS + MP_PRIO --, some can but we
prefer not to -- e.g. DSS + ADD_ADDR -- and some have to be used
together at some points -- e.g. MP_FAIL and DSS.
We need to clarify this as a base before allowing other modifications.
For example, does it make sense to send a RM_ADDR with an MPC or MPJ?
This remains open for possible future discussions.
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/smc')
0 files changed, 0 insertions, 0 deletions