You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When GSO is used, we can now have packets with a size > 2¹⁶ (see commit 7c4e983) which is not compatible with MPTCP's DLL (Data-Level Length) field (see issue #450 and 9fce92f) limited to 2¹⁶.
Paolo suggested to increase MPTCP's DLL field by reusing (or moving?) the Checksum field.
We could have an extension of the MPTCPv1 protocol using one unused flag from the MPC to negotiate this option. If both ends support it, we can add up to 2 bytes to this field.
The text was updated successfully, but these errors were encountered:
When GSO is used, we can now have packets with a size > 2¹⁶ (see commit 7c4e983) which is not compatible with MPTCP's DLL (Data-Level Length) field (see issue #450 and 9fce92f) limited to 2¹⁶.
Paolo suggested to increase MPTCP's DLL field by reusing (or moving?) the Checksum field.
We could have an extension of the MPTCPv1 protocol using one unused flag from the MPC to negotiate this option. If both ends support it, we can add up to 2 bytes to this field.
The text was updated successfully, but these errors were encountered: