Re: [multipathtcp] potential MPTCP proxy charter item

[Joe Touch <[e-mail]>]

Oh - a quick followup.

If you have an option that "poisons" the connection if not confirmed (as
would using long EDO inside the SYN), then you have to retry without
that option. That is *possible*, but there's another problem.

RFC793 defines options as optional. Making any option mandatory would
require updating RFC793. That sort of change is exactly why long EDO
(actually extending the option space, rather than declaring the
capability) is currently prohibited in EDO.

Joe


On 11/7/2016 7:56 AM, Joe Touch wrote:
>
> On 11/7/2016 7:42 AM, Mirja Kühlewind wrote:
>> Do you mean the MCP forwards the original SYN (and basically does nothing if the server supports MPTCP) or does the MCP terminate the TCP connection and start a new TCP connection with MP_CAPABLE towards the server?
>>
>> Mirja
> If you're OK with needing to terminate a failed option exchange, then it
> might be possible to use EDO in the SYN in its current form.
>
> TCPM decided to prohibit that in the general case, but I could ask them
> to allow that in very limited environments (but it could NEVER be
> default on).
>
> Note - the use cases I'm hearing appear to assume very strong knowledge
> about the other end of the connection and the path. In that case, you
> probably can skip most - if not all - of the 'negotiation' options and
> just start using them during the SYN too. However, if you say "no, we
> need to confirm", then you would not be able to use EDO inside the SYN.
>
> Joe